What is a customer journey map useful for?

A customer journey map describes the steps someone takes when dealing with your business, including interactions, feelings and difficulties. HBS Online identifies these as core components. Give your first map a practical purpose: investigate where a customer needs help completing a particular task.

Imagine a small cleaning company. In this hypothetical example, a homeowner wants to arrange a first visit before guests arrive. Map that task from looking for help through receiving the service and checking the result.

Define the terms before drawing boxes

Customer touchpoints are specific interactions with a business, such as a website visit, telephone call or email. A persona is a profile representing a customer group and its needs. These definitions follow the components described by HBS Online.

For the cleaning example, write reading the service description as one interaction and asking whether supplies are included as another. Avoid a vague box labelled website. Put an action in every box so someone can check whether it happened.

Use the map to examine your promise as well. If you advertise an easy booking, walk through what the customer must actually do. For help wording that promise, keep the value proposition guide beside your notes.

Which journey should you map first?

Choose one customer group, one situation and one desired outcome. Atlassian recommends this narrow scope. Write the boundary at the top of the page before inviting anyone to contribute.

For our hypothetical company, choose a first-time homeowner booking a one-off clean. Leave recurring customers and commercial contracts on a separate list. Decide whether your current question concerns booking alone or the complete first service.

Write a useful project brief

Try this: examine how a new customer confirms what is included, receives a price and books a suitable visit. Then add your business question: where do people need another explanation before they can decide?

• Customer goal: prepare the home before guests arrive.
• Starting point: the customer begins looking for a service.
• Finishing point: the first visit is completed and checked.
• Open question: which expectations need clarification before booking?

Keep desired outcomes separate from your current observations. A proposed instant confirmation belongs in an improvement column until you actually provide it. Write down what customers experience today, including awkward workarounds.

How do you find out what customers actually experience?

Review recent enquiries and speak to customers about a specific experience. Interviews, surveys, analytics and support records are research inputs recommended by HBS Online. Choose the records you already have before commissioning new research.

Ask about the last real occasion

I suggest beginning with a few completed bookings and a few enquiries that stopped. Use this as an initial investigation, without presenting it as a representative survey. Ask permission to take notes and keep identifying details out of the shared map.

1. What prompted you to look for help?
2. What did you check before contacting us?
3. Which details did you need before choosing?
4. What happened immediately after you enquired?
5. Was anything different from what you expected?

Ask what happened next whenever an answer skips a step. If someone says booking was confusing, ask which part they were trying to complete. Record their explanation before proposing your own solution.

Label what you know and what you suspect

Give every observation a simple evidence label: customer reported, record observed, or assumption to check. If a person stopped replying, record that fact. Leave their reason unknown unless you have evidence for it.

For feelings, use ordinary words such as uncertain, reassured or frustrated. Add who described the feeling. When it is your interpretation, write that explicitly and ask the customer whether it fits.

Invite whoever answers enquiries to review the sequence with you. Ask them to show the handover between answering a question and confirming a visit. Put unexplained gaps on an investigation list rather than settling them by a vote.

What should your customer journey map template contain?

Start with a table showing the step, customer question, interaction, evidence and possible action. The example below is hypothetical throughout. Its problems are suggestions to investigate, not findings from a real cleaning business.

Adapt the stages to the task

Use these customer journey stages as working labels, then replace them with the language your customers use. Add an emotion column and a reference to the underlying record. Keep proposed changes in a separate column from current events.

A buyer journey map might finish at the purchasing decision. For this exercise, include preparation and the first service as well. Draw a return arrow if a customer revisits a quote or asks another question before confirming.

If the booking step needs attention, use the appointment booking guide for the implementation work. Keep the map focused on what the customer needs to understand at that step.

How do you choose a change and judge the result?

Choose one problem with supporting evidence and a manageable fix. Discuss how often it appears in your records, how it affects the customer's task and who can address it. Atlassian also recommends checking the scale of identified problems with quantitative data. Its analysis step explains this prioritisation.

Write the change as an assignment

For the hypothetical cleaning company, test clearer confirmation wording. Assign the booking coordinator to distinguish a requested slot from an accepted booking. Specify the information each message must include and how unresolved availability should be handled.

If your investigation points to preparation messages, consult the appointment reminder guide after deciding what information customers need. First approve the message and its timing, then choose how to deliver it.

Choose a measure before starting

For this test, count confirmed bookings that need an additional clarification about the visit time. Divide that count by all eligible confirmed bookings reviewed. Define eligible before the test and use the same definition afterwards.

• Record the clarification question, not just the total.
• Check whether staff used the revised message.
• Track booking errors alongside the main measure.
• Note other changes, including offers or staffing.

Treat a small comparison as a reason to investigate further, rather than proof that one message caused a business result. Discuss contradictory examples with the team. Keep, revise or stop the change based on the complete record.

For this exercise, use customer journey analytics to mean checking numbers against the steps in your map. Keep your broader experiments in a separate log; the small business growth marketing guide is a related next read.

How can a small team finish its first map this week?

Use a shared spreadsheet or a paper worksheet for the first version. I would choose Excel or Google Sheets for a table and a physical whiteboard for a discussion. Avoid spending the first session comparing journey mapping tools.

If your team already works in Confluence, consider the template referenced in Atlassian's mapping exercise. Judge your chosen format by whether colleagues can find the evidence and update a step, rather than by presentation polish.

1. Monday: agree on the customer, task and boundary.
2. Tuesday: review records and hold short customer conversations.
3. Wednesday: draft the sequence and mark unresolved questions.
4. Thursday: check the map with a customer and choose a change.
5. Friday: assign the work and schedule the review.

Keep one person responsible for the working document. At the review, ask what new evidence would make the team change its interpretation. Turn that question into the next small research task.

When gathering further feedback, connect it to a specific experience. If the enquiry starts on social media, the social media audit guide can help structure your next review. Bring the relevant findings back to the same customer task.