Concourse → Journeys
Mapping the route from question to answer
Journey mapping is how we turn "people cannot find things" into specific, fixable problems. Here is the method and an example worked through.
The method
1. Collect real questions
From help inboxes, phone notes and short interviews: the actual words people use when they ask for something.
2. Group by task
Questions cluster into a small number of tasks. Those tasks, not departments, become the backbone of the portal.
3. Walk the current route
We try each task on the existing setup and record every click, dead end, login and email.
4. Design the shorter route
The new journey names each stop, the content needed there and the person responsible for it.
worked example
"How do I book annual leave?"
Current route
- Open intranet home page
- Guess "HR Hub"
- Scroll a page of news
- Open "Policies", find a 2019 leave policy
- Email HR to ask for the form
- Wait two days
Designed route
- Home page task list: "Holiday and leave"
- One page: current policy summary, form, who approves, how long it takes
- Submit form; receipt with reference
- Manager approval notification
Decisions needed: who owns the leave page, how the form is routed, and where the authoritative policy lives.
When journeys reveal process problems
Sometimes the map shows that the portal is not the problem: the request has no owner, or two teams think the other one handles it. We report that plainly. A clearer page can still help, but the real fix is an agreement between people, and we would rather you knew before paying for a build.