What is a customer journey map?

It is a map built from one user's point of view that shows what value users get, how they get it, how they feel, how they behave, and what they think at each moment of an experience. It turns a vague sense that an experience is bad into specific, locatable problems.

Do I need a persona before making a journey map?

Yes. A journey map is always built from one persona's path, so you choose who you are mapping before you start.

Customer Journey Map Template (With a Filled-In Example)

A customer journey map template helps you see a product the way your user actually experiences it — moment by moment, over time. Most free templates give you an empty timeline and leave you guessing what to put in it. This one comes with a complete, filled-in example so you can see what a useful map looks like.

A journey map is built from one user’s point of view. By analysing each moment of an experience, you can see what value users get, how they get it, how they feel, how they behave, and what they think at every step.

Why it works: a journey map turns a vague “the experience is bad” into specific, locatable problems. It shows you exactly where the painful moments are — and where the opportunities to fix them sit.

What goes in a journey map

Read the map in horizontal rows, one column per moment:

Experience steps — name each moment from the user’s point of view, with what’s happening, plus their thoughts and emotions.
Positive and negative points — what works and what hurts at each moment.
Insights and opportunities — where there’s something interesting, or a clear chance to improve.
Touchpoints — the channels where each moment happens (website, call center, app, etc.).

How to use the template

Pick a persona first. A journey map is always one persona’s path. Choose who you’re mapping before you start.
Name the journey. Write the scenario you’re describing (e.g., “checking whether a client has paid”).
Define the moments. Give each step a short title, then describe it from the user’s point of view — and capture their thoughts and feelings, in their words.
Mark positives and negatives for each moment.
Pull out insights and opportunities — the openings worth designing for.
Note the touchpoints so you know where each problem lives.

A useful tip: one scenario reflects one user’s point of view, so you may need more than one journey map to understand the different sides of your idea.

A filled-in example: Maya’s journey

This map follows the same user as our persona example — Maya, a long-term freelancer — as she tries to find out whether a client has paid her.

Moment 1 — Wants to check her payments She doesn’t know whether her client has paid, and she needs to. Thinking: “How annoying — I have to open the website, I have to call… I don’t get it.” Emotion: anxious. Negatives: worried about whether payments arrived; has to make an effort just to find out.

Moment 2 — First attempt to solve it She opens the bank’s website and can’t find the option she’s looking for. Thinking: “So frustrating — I can’t find out whether they’ve paid me. I’ll have to call customer service.” Emotion: angry. Negatives: can’t find what she needs; forced to ask the call center. Touchpoint: bank website.

Moment 3 — Connects to the call center She calls customer service. They ask her a series of questions and send a code to her phone to verify her identity. Thinking: “So many questions! Just finding out whether I got paid is this hard…” Emotion: worried. Negatives: wait time too long; too many questions. Opportunity: an easy-access channel for simple questions. Touchpoint: call center.

Moment 4 — A frustrating answer After all the questions, they confirm she hasn’t been paid yet — and offer her a new service she didn’t ask for. Thinking: “What a hassle! All that wasted time — and now they’re trying to sell me more!” Emotion: frustration. Negatives: feels her time was wasted; fed up with the bank. Opportunity: send a notification whenever money is deposited. Touchpoint: call center.

Read across the bottom row and the design work writes itself: the single highest-leverage fix is a deposit notification, which removes the entire reason she started this painful journey.

What to use before and after

Before: you need a persona — the journey is always built from a persona’s point of view.
After: turn the opportunities into ideas with a “How Might We” reframing, then test the strongest one.

To see how a journey like this becomes part of a portfolio story, read the UX case study guide and browse real examples.

A journey map shows you found the real problem — the thing a strong case study is built on. When you write yours up, Folioverse helps you turn the thinking into a case study recruiters trust. Try it free.