
Journey Mapping
Part of Customer journey mapping
Mapping a journey from the customer's perspective
Reconstruct a customer journey from the person's goal, actions and questions, including the work before and after your recorded touchpoints.
To map from the customer’s perspective, write down the goal they were pursuing and reconstruct the steps as they experienced them. Begin before your first recorded interaction and follow the task to an outcome they can recognise, including an unsuccessful or uncertain outcome.
Use their accounts and observable actions to set the sequence. Add internal activity only where it explains something they encounter.
Start with the customer’s trigger
Consider an illustrative appointment-booking journey. A booking system may record the first step when someone opens a form. The person’s task may begin earlier, when they read a referral, work out which service to use and look for an available appointment. A possible goal is: “Book the right appointment and know what to bring.”
These details are prompts for research, not findings from an appointment service. Ask about a recent instance rather than an idealised route.
What prompted the task? What did the person expect to happen first? Where did they go for information?
What made them believe they had booked successfully? Include people whose attempts ended early if the map is meant to reveal barriers to booking.
Key Actions in a Customer’s Appointment Booking Process
- Identify need from referral or adviceStart of task based on real-world trigger
- Find correct service and check eligibilityIncludes searching for ABN, GST details or location-based criteria
- Navigate to booking platformUse government portal such as Service NSW or VicGov
- Complete form and submitMay involve entering personal details, superannuation info, or contact data
- Verify confirmation and next stepsCheck email, SMS or portal for booking outcome
Reconstruct events without smoothing them out
Place each account on a timeline before combining accounts. Record the customer’s action, the channel or touchpoint, the information they needed and the result.
Add their words or reactions only when they were captured and can appropriately be used. A pause seen during an observed session is an observation; uncertainty about eligibility remains an interpretation unless the person expressed it.
Customers may double back, ask someone else for help or wait between steps. Keep those loops. A neat row of company touchpoints can conceal the customer’s work between them, such as finding a reference number or calling to check whether an online request arrived.
Where routes differ materially, show separate paths. Someone booking for themselves may face different steps from someone assisting another person. Do not combine their experiences into an invented ‘typical customer’ without checking what the routes share.
Customer Appointment Booking Journey: Key Steps and Touchpoints
- Read referral or notification
- Initial trigger for action
- Research service options and eligibility
- Determine which appointment to book
- Check online booking system
- Access via website or app
- Attempt to select appointment time
- May require multiple attempts
- Wait to confirm booking success
- Uncertainty about confirmation receipt
- Receive confirmation (or not)
- Outcome may be unclear or missing
Test whose perspective the map represents
Read each stage as a customer action or question. “Scheduling team assigns queue” is internal work. “I wait for an appointment time” describes the corresponding experience.
Keep the internal step in a note if it may explain the wait, but do not let it replace the customer-facing stage. Check the draft against the original accounts. Can you trace each important step and difficulty to evidence?
Have you recorded a completed booking as success even though the customer did not receive a usable confirmation? Mark unknown outcomes as unknown. If customers and staff describe the same stage differently, retain the disagreement until it is investigated.
A customer-perspective map can show work and uncertainty the organisation otherwise misses. Its conclusions remain bounded by the people and situations researched; use it to identify what to check next, not to claim that every customer follows the same path.
Customer vs. Organisation Perspective: Booking Confirmation Stage
- Customer Experience
- I waited for a confirmation but didn’t know if it went through
- Organisation Record
- Scheduling team assigns queue


