Service Map / Journey Map (template)
Use this to map the service from the user's perspective. A “step” is a decision point or moment where the user needs visibility/control. A “task” is an individual action.
Tip: start with ~6–12 steps. Too many usually means you're mixing steps and tasks.
Journey overview
- Service:
- User group:
- Start:
- Done:
- Channels in scope:
Journey table
| Step | User goal at this step | User tasks | Channel(s) | What the user needs (info/evidence) | Pain points / confusion | Where they seek help | Notes (handoffs, risks) |
|---|---|---|---|---|---|---|---|
| 1 | |||||||
| 2 | |||||||
| 3 | |||||||
| 4 | |||||||
| 5 |
Cross-cutting notes
- Top 3 drop-off points:
- Top 3 causes of contact:
- Known accessibility issues:
- Known policy/operational constraints: