Templates & tools
A customer journey map template that demands evidence.
Most journey maps are beautiful and useless: built in a two-hour workshop from what the team believes customers feel, printed, framed, and never consulted again. The map looks finished, so nobody tests it — and the store keeps losing customers at stages the map paints as smooth. This template adds the one column that changes everything: Evidence. Every friction you write down has to point at data that proves it exists.
The full template is on this page, free to use — seven columns and example rows covering a complete retail journey, from discovery to the return visit. If you want the print-ready version for your mapping workshop, we'll email you the PDF. Fill it with data, not opinion, and the map stops being a poster and starts being a backlog.
The template — 7 columns, one row per journey stage
The map — example rows for a retail journey
Example rows for a physical retail journey. Replace every cell with your own data — and if the Evidence cell stays empty, treat the friction as a hypothesis, not a fact.
| Stage | Customer goal | Touchpoint | Customer feeling | Friction / gap | Owner | Evidence |
|---|---|---|---|---|---|---|
| Discovery | Find a store that has the product | Google, social, marketplace listings | Curious | Store hours and stock wrong online | Marketing | Google Business Profile reviews, website analytics |
| Arrival | Get oriented and feel welcome | Storefront, entrance, first greeting | Hopeful | No greeting in the first minute; layout unclear | Store manager | Door counts vs. greeting observations |
| Browsing | Compare options and shortlist | Shelves, displays, signage, price tags | Evaluating | Prices missing; sizes not on the floor | Visual merchandising | Shelf audits, out-of-stock log |
| Sales interaction | Get a trustworthy recommendation from someone who understood the need | The conversation with the salesperson on the floor | Anywhere from confident to pressured — the widest emotional swing of the whole journey | Needs-discovery skipped; features recited instead of a recommendation; objections dropped instead of answered; no closing attempt | Sales lead / trainer | Usually none — the biggest evidence gap in the entire map (see below) |
| Checkout | Pay fast and feel sure about the choice | POS, queue, payment terminal | Impatient | Queue over 5 minutes at peak; surprise charges | Operations | Queue-time samples, line abandonment counts |
| Post-purchase | Get value from the product; resolve issues fast | Product use, support channel, exchanges | Testing the decision | Exchange policy explained differently by each employee | CX / support | Support tickets, exchange logs, survey verbatims |
| Return visit | Repeat a purchase that went well | Promotions, CRM, new season | Loyal — or quietly gone | No reason to come back beyond discounts | CRM / marketing | Repeat-purchase rate, cohort retention |
Get the print-ready PDF
The same template, formatted for print and workshop use — delivered to your inbox.
How to use this template
- Map with data, not opinion: before the workshop, gather what you already have — reviews, survey verbatims, conversion by stage, queue times — and bring it into the room.
- Run it as a workshop with the people who serve customers: salespeople and cashiers know where the journey breaks long before any dashboard does. Managers alone will map the org chart.
- Build one map per persona and per store format: the journey of a gift buyer in a mall store is not the journey of a contractor in a depot. One generic map hides both.
- Treat the Evidence column as mandatory: every friction needs a source that proves it exists. A row with an empty Evidence cell is a hypothesis to test, not a problem to fix.
- Review the map every quarter: re-check the evidence, retire fixed frictions, add new ones. A journey map with a date older than six months is describing a store that no longer exists.
The mistakes that turn journey maps into wall art
Making it once and framing it. A journey map made for a kickoff and never revisited is decoration — the journey changes with every season, price move and staff change, and the map has to change with it. Put a review date on the map the day you finish it.
Mapping your internal process instead of the customer's perspective. If the stages read like your departments — marketing, sales, logistics — you mapped the company, not the journey. Every stage name should describe what the customer is trying to do, not which team touches them.
Filling the feeling column by guesswork. 'The customer feels welcome' written by the people responsible for making them feel welcome is not a finding — it is a hope. That is exactly why this template has an Evidence column: no source, no feeling.
The map is a hypothesis. The interaction is the fact.
Look at the Evidence column of any journey map ever made: the stage with the least evidence is always the sales interaction — the one stage that decides whether the visit becomes a sale. Reviews cover discovery, tickets cover post-purchase, queue counts cover checkout; the conversation on the floor stays a guess. Cognifyze captures exactly that stage, with consent and without identifying any individual shopper, and fills the Evidence cell of your most decisive row with real data.
In measured deployments, making the interaction visible moved same-store conversion from 51.5% to 79.5% (+28pp, p<0.001), with 383% ROI and payback in 1.4 months.
Fill the evidence gap in your journey map — book an executive diagnostic.
Related tools and guides
Journey mapping — frequently asked questions
What is a customer journey map?
A structured view of every stage a customer moves through with your business — what they are trying to do, where they touch you, how it feels, and where it breaks. Done well, it is a prioritized list of frictions with evidence; done badly, it is a poster.
How many stages should a retail journey map have?
Five to eight covers most physical retail: this template uses seven, from discovery to the return visit. Fewer than five hides frictions inside merged stages; more than ten turns the workshop into an inventory nobody maintains.
Who should be in the mapping workshop?
The people who face customers — salespeople, cashiers, support — plus whoever owns each stage and someone with the data. A workshop of managers only produces the official version of the journey, which is precisely the version you do not need.
What goes in the Evidence column?
Any source that proves the friction exists: review excerpts, survey verbatims, conversion or queue-time numbers, out-of-stock logs, support tickets. If a row has no evidence, keep the friction on the map but mark it as a hypothesis — and design a way to test it.
How often should the map be updated?
Quarterly is a healthy default for retail: fast enough to track season and assortment changes, slow enough to see whether fixes moved the evidence. Re-validate every row's evidence, retire what was fixed, and re-rank what remains.