Journey Mapping
Part of Customer journey mapping
Distinguishing a journey map from an internal process diagram
See what each diagram shows, choose the right view for a customer question and connect the two without confusing internal completion with customer success.
A journey map follows a person trying to achieve a goal. It shows what they do and experience over time.
An internal process diagram follows the work an organisation performs. It includes decisions, queues and system steps.
Choose the view that answers your question. When a customer problem may have an operational cause, compare the two views at the points where internal work becomes visible.
Check what sets the order of the diagram
A journey map is ordered by the customer’s path: noticing a problem, looking for help, submitting a request and learning the result. Useful rows include actions, touchpoints, questions, waits and outcomes. The path may cross departments without naming every internal task.
A process diagram is ordered by how work is carried out: a request enters a queue, a rule is checked, a specialist approves a change and a system sends a message. Useful details include responsibility, decision conditions and rework. Those details can explain a journey stage, but they do not by themselves show whether the customer understood what happened or achieved the goal.
Consider a hypothetical invoice correction. A process diagram may end when finance marks the correction complete.
A customer journey may continue until the person receives an accurate invoice and can use it. The endpoints answer different questions. An internal completion marker alone cannot establish that the customer’s task is finished.
Journey Map vs Internal Process Diagram: Key Differences
- Order of Diagram
- Customer’s path (e.g. noticing a problem, seeking help, receiving result)
- Order of Diagram
- Internal work flow (e.g. request enters queue, rule checked, specialist approves)
- Key Rows/Details
- Actions, touchpoints, questions, waits, outcomes
- Key Rows/Details
- Responsibility, decision conditions, rework, system steps
- Endpoint Meaning
- Customer achieves goal (e.g. receives accurate invoice)
- Endpoint Meaning
- Internal task complete (e.g. finance marks correction as done)
Use the question to choose the view
| Question | Start with |
|---|---|
| Where does the customer become uncertain or give up? | A current-state journey map grounded in customer evidence. |
| Which team receives a request after submission? | An internal process diagram or service blueprint. |
| Why does the customer have to chase an update? | The journey to locate the wait, then the process to investigate its cause. |
| What might a proposed service change feel like? | A future-state journey map, labelled as a proposal to check. |
The views can share a timeline without being collapsed into one dense chart. A service blueprint can connect customer touchpoints with the people, systems, data and rules behind them.
How to Use the Right View for Customer Questions
- Where does the customer become uncertain or give up?Start with a current-state journey map grounded in customer evidence
- Which team receives a request after submission?Use an internal process diagram or service blueprint
- Why does the customer have to chase an update?First use the journey to locate the wait, then the process to investigate cause
- What might a proposed service change feel like?Use a future-state journey map, labelled as a proposal to check
Convert an internal map carefully
If you only have a process diagram, do not relabel its boxes as customer stages. First define the customer goal and ask where the task begins and ends for that person.
Then reconstruct their actions, questions and visible outcomes from research. Use the process diagram to identify internal steps that might explain a wait or message. Mark those explanations as unverified until checked.
In the illustrative invoice example, “finance approves adjustment” may correspond to “I wait to know whether the charge will change”. The customer may also search for the original invoice or contact support before finance sees a case. Those moments need customer evidence; the process diagram cannot supply them automatically.
Keep the two views linked where work becomes visible to the customer. If they disagree, investigate the difference through customer research or operational records. This gives the team an account of the experience and a way to examine the process shaping it.
Reconstructing a Customer Journey from an Internal Process Diagram
- Step 1Define the customer goal and identify where the task begins and ends for them
- Step 2Reconstruct customer actions, questions, and visible outcomes using research
- Step 3Use the process diagram to identify internal steps that may explain waits or messages
- Step 4Mark explanations as unverified until confirmed through customer research or operational records
- Step 5Keep both views linked where work becomes visible to the customer; investigate discrepancies
