A customer journey map template for Excel. Built to actually get used.

What the template covers. Seven rows, one journey.

A customer journey map in Excel earns its keep when it is built around seven rows, repeated under each stage column: stage name, customer goal, touchpoint, action taken, emotion, pain point and owner. That last row is the one most templates leave out, and it is the reason most journey maps end up as a nicely formatted document nobody acts on. A pain point with no named owner gets nodded at in a review meeting and then forgotten the moment everyone goes back to their actual workload.

Nielsen Norman Group's guidance on journey mapping, one of the more widely cited references for the format, recommends organising a map by stage across the top and by these layers of detail down the side, precisely because it lets a reader scan a single layer, every stage's pain points, say, in one pass rather than reading the map stage by stage like a story. Excel is a genuinely good fit for this structure: columns for stages, rows for layers, each cell a short, specific entry rather than a paragraph.

Keep the stage count to between four and six. Three stages tends to compress too much detail into one cell; eight or more means the sheet stops fitting on a single screen, and a map nobody can see in one view gets referred to less often. For most B2B and SaaS journeys, awareness, consideration, onboarding, active use and renewal covers the real decision points without padding.

How to use it. One segment, one real journey, no averaging.

Pick one customer segment before opening Excel. A map built to represent "all our customers" ends up vague in every cell, because the enterprise buyer's onboarding pain point and the solo founder's onboarding pain point are rarely the same thing, and averaging them produces an entry too general to act on. Name the segment at the top of the sheet and hold to it.

Fill the goal and touchpoint rows from what you already know, then fill emotion and pain point from evidence, not assumption. Pull three or four recent support tickets, a handful of churn or onboarding call transcripts, or five minutes with the account manager who owns that segment. A pain point row filled from a real transcript reads completely differently to one guessed in a workshop: "frustrated that the pricing page does not show currency" is something you can brief a fix against; "confused" is not.

Colour the pain point row using Excel's conditional formatting, a simple three-colour scale for severity, so anyone opening the sheet can see the two or three stages that need attention first without reading every cell. This is one of the few places Excel genuinely beats a slide deck for journey mapping: it is quick to filter, sort and recolour as new evidence comes in, where a deck has to be rebuilt by hand each time.

Fill the owner row last, and do not leave a single cell blank. If no one obviously owns a pain point, that gap is itself a finding worth raising, not a reason to skip the row.

A worked example. A founder-led SaaS team's onboarding stage.

I built this exact structure with a founder-led SaaS team whose only journey map lived in a slide deck from a workshop eighteen months earlier, never opened since, updated once after a rebrand changed the logo and nothing else. Nobody disagreed the deck was out of date; nobody had found a reason to open it, since updating it meant rebuilding slides rather than editing a few cells.

We rebuilt the onboarding stage first, because the team's own hunch was that it was losing customers there without clear evidence why. Pulling emotion and pain point from the last twenty support tickets tagged "onboarding" took under an hour and surfaced something the deck had never captured: customers repeatedly described feeling lost between finishing setup and seeing the product actually produce a result, a gap of two to three days with no clear next step and no message from the team during it. The deck's onboarding stage had said "customer completes setup, customer sees value", one box covering what was actually two distinct emotional states separated by a silent gap.

The fix was not a new feature. It was a single automated check-in email sent 48 hours after setup, written by the founder, pointing the customer at the one action most correlated with activation. The owner row named the head of customer success, who reviewed and updated that one cell monthly against fresh ticket data rather than letting it sit. Three months on, the team could point to a specific drop in onboarding-stage churn rather than a feeling that onboarding "seemed better now".

McKinsey's research on customer journeys, published in its work on end-to-end experience redesign, found that organisations which manage experiences by complete journey rather than by individual touchpoint see customer satisfaction improve by 20 to 30 percent while reducing the cost of service by 15 to 20 percent. The Excel template above is the practical, no-budget version of that same discipline: one sheet, one segment, one honest look at where the journey actually breaks.

Our guide to running a journey mapping workshop covers how to gather this evidence as a team exercise if you want several people filling the sheet together rather than building it alone; the structure above works identically either way.

Getting started. Build the first stage this week.

1. Pick one segment and one journey. Resist the urge to map everyone at once.
2. Set up the seven rows under 4-6 stage columns. Stage, goal, touchpoint, action, emotion, pain point, owner.
3. Fill emotion and pain point from real evidence. Tickets, transcripts or a short conversation with the team closest to the customer, not a guess in a meeting room.
4. Name an owner for every pain point. An unowned row is a finding to raise, not a gap to leave.
5. Review it every quarter, and after any pricing or onboarding change. A sheet left untouched for a year is no more trustworthy than the slide deck it replaced.

Whether this stays a simple Excel sheet or eventually becomes part of a wider customer journey mapping engagement usually comes down to one thing: how many teams need to see and edit it live. For a single owner updating it quarterly, the template above is genuinely enough.