What This Template Is For
A customer journey map is a visual representation of every interaction a customer has with your product. The Nielsen Norman Group provides foundational research on journey mapping methodology, from the moment they first become aware of you through long-term advocacy. It captures what customers do, think, and feel at each stage, revealing pain points and opportunities that quantitative data alone cannot surface.
This template provides a structured framework for mapping the six core stages of the customer journey: Awareness, Consideration, Purchase, Onboarding, Adoption, and Advocacy. Each stage includes spaces for touchpoints, customer emotions, pain points, opportunities for improvement, and metrics to track. The approach draws from service design thinking principles. A fully filled-out example for a SaaS product is included to guide your own mapping process.
When to Use This Template
- Product discovery and research: Map the current journey before redesigning flows or building new features. The Product Discovery Handbook covers research methods that feed directly into journey mapping.
- Onboarding optimization: Identify where new users drop off and why.
- Cross-functional alignment: Create a shared understanding of the customer experience across product, marketing, sales, and support.
- Customer experience audits: Systematically evaluate every touchpoint for friction and opportunity.
- New product planning: Map the intended journey before building, to design experiences intentionally rather than accidentally.
- Churn investigation: Trace the journey of customers who leave to find the moments where things go wrong.
Who should be in the room? Journey mapping is most effective as a collaborative exercise. Include product, design, marketing, sales, customer success, and support. Each team sees different parts of the journey.
Step-by-Step Instructions
Step 1: Define Your Scope (5 minutes)
Before mapping, answer these scoping questions:
- ☐ Which persona are you mapping? Journey maps are persona-specific. A self-serve startup user and an enterprise buyer with a procurement process have fundamentally different journeys. Pick one.
- ☐ What is the starting point? Usually the moment the customer first becomes aware of your product or category.
- ☐ What is the ending point? Usually when the customer becomes an advocate (or churns).
- ☐ Are you mapping the current state or the desired future state? Do the current state first. You cannot improve what you have not documented.
Step 2: Gather Input Data (15 minutes)
Collect these inputs before filling in the template:
- ☐ Customer interview transcripts or notes (3-5 recent interviews minimum)
- ☐ Support ticket themes and common questions by journey stage
- ☐ Analytics data: funnel conversion rates, drop-off points, time between stages
- ☐ Sales team feedback on the buying process
- ☐ NPS or CSAT data segmented by customer tenure
- ☐ Onboarding completion data and activation metrics
For thorough methods on gathering qualitative data, see the user research guide and review best practices for avoiding common interview mistakes. The Product Discovery Handbook provides a full framework for synthesis.
Step 3: Map Each Stage (20 minutes)
Work through the template below stage by stage. For each stage, document:
- What the customer is doing (actions and touchpoints)
- What they are thinking (questions, concerns, expectations)
- What they are feeling (emotional state. Frustrated, excited, confused, confident)
- Where the pain is (friction, confusion, unmet expectations)
- Where the opportunity is (ways to improve the experience)
- What to measure (metrics that indicate success or failure at this stage)
Step 4: Identify Priority Improvements (5 minutes)
Review the completed map and identify the 3-5 highest-impact opportunities. Prioritize based on: severity of pain, number of customers affected, and effort to fix. The RICE framework provides a structured way to score and rank these opportunities.
The Customer Journey Map Template
Persona: [Name and brief description]
Journey scope: [Starting point] to [Ending point]
Map type: Current state / Future state
Date created: [Date]
Last updated: [Date]
Stage 1: Awareness
The customer realizes they have a problem or discovers your product/category.
| Dimension | Details |
|---|---|
| Customer goal | [What are they trying to accomplish?] |
| Touchpoints | [Where do they encounter your brand? e.g., search, social, word of mouth, ads, content] |
| Actions | [What do they do? e.g., Google a problem, read a blog post, see a social post] |
| Thinking | [What questions are on their mind?] |
| Feeling | [Emotional state: curious, frustrated, skeptical, overwhelmed?] |
| Pain points | [What friction exists? e.g., hard to find information, unclear what your product does] |
| Opportunities | [How could this stage be improved?] |
| Key metrics | [e.g., Organic traffic, brand search volume, content engagement rate] |
Stage 2: Consideration
The customer actively evaluates your product against alternatives.
| Dimension | Details |
|---|---|
| Customer goal | [What are they trying to accomplish?] |
| Touchpoints | [e.g., website, pricing page, demo, review sites, competitor comparisons] |
| Actions | [e.g., Request demo, start free trial, read case studies, check reviews] |
| Thinking | [e.g., "Will this work for my team?", "Is the price justified?", "What do other users say?"] |
| Feeling | [Emotional state] |
| Pain points | [e.g., Pricing not transparent, demo requires sales call, unclear differentiation] |
| Opportunities | [How could this stage be improved?] |
| Key metrics | [e.g., Trial signup rate, demo-to-trial conversion, pricing page bounce rate] |
Stage 3: Purchase
The customer makes the decision to buy and completes the transaction.
| Dimension | Details |
|---|---|
| Customer goal | [What are they trying to accomplish?] |
| Touchpoints | [e.g., Checkout flow, contract signing, billing setup, welcome email] |
| Actions | [e.g., Select plan, enter payment, sign contract, get approval from manager] |
| Thinking | [e.g., "Am I choosing the right plan?", "What happens if I need to cancel?"] |
| Feeling | [Emotional state] |
| Pain points | [e.g., Confusing plan tiers, lengthy procurement process, hidden fees] |
| Opportunities | [How could this stage be improved?] |
| Key metrics | [e.g., Trial-to-paid conversion rate, time to purchase, cart abandonment rate] |
Stage 4: Onboarding
The customer sets up the product and begins using it for the first time.
| Dimension | Details |
|---|---|
| Customer goal | [What are they trying to accomplish?] |
| Touchpoints | [e.g., Setup wizard, onboarding emails, help docs, first-use prompts, CS kickoff call] |
| Actions | [e.g., Create account, invite team, configure settings, complete first core action] |
| Thinking | [e.g., "How do I get started?", "Where is the feature I signed up for?"] |
| Feeling | [Emotional state] |
| Pain points | [e.g., Too many steps before value, unclear next actions, no guidance] |
| Opportunities | [How could this stage be improved?] |
| Key metrics | [e.g., Onboarding completion rate, time to first value, Day-1 activation rate] |
Stage 5: Adoption
The customer integrates the product into their regular workflow and expands usage.
| Dimension | Details |
|---|---|
| Customer goal | [What are they trying to accomplish?] |
| Touchpoints | [e.g., In-app feature discovery, email tips, webinars, support, community forum] |
| Actions | [e.g., Use advanced features, invite more team members, integrate with other tools] |
| Thinking | [e.g., "How do I get more out of this?", "Can my whole team use this?"] |
| Feeling | [Emotional state] |
| Pain points | [e.g., Feature discoverability, learning curve for advanced features, lack of integrations] |
| Opportunities | [How could this stage be improved?] |
| Key metrics | [e.g., Weekly active usage, feature adoption rates, seat expansion, NPS] |
Stage 6: Advocacy
The customer becomes a promoter who recommends the product to others.
| Dimension | Details |
|---|---|
| Customer goal | [What are they trying to accomplish?] |
| Touchpoints | [e.g., Referral program, review request, case study interview, community, social] |
| Actions | [e.g., Leave a review, refer a colleague, speak at an event, share on social media] |
| Thinking | [e.g., "This product genuinely helped me. Others should know about it."] |
| Feeling | [Emotional state] |
| Pain points | [e.g., No easy way to refer, referral incentives are weak, never asked for feedback] |
| Opportunities | [How could this stage be improved?] |
| Key metrics | [e.g., NPS, referral rate, review volume, case study participation, organic word-of-mouth] |
Emotional Journey Summary
After completing all six stages, plot the overall emotional arc of the journey.
| Stage | Emotion | Intensity (1-5) | Key Driver |
|---|---|---|---|
| Awareness | [e.g., Curious] | [1-5] | [What causes this emotion] |
| Consideration | [e.g., Cautiously optimistic] | [1-5] | [What causes this emotion] |
| Purchase | [e.g., Anxious] | [1-5] | [What causes this emotion] |
| Onboarding | [e.g., Overwhelmed] | [1-5] | [What causes this emotion] |
| Adoption | [e.g., Confident] | [1-5] | [What causes this emotion] |
| Advocacy | [e.g., Proud] | [1-5] | [What causes this emotion] |
Emotional low points to address: [List the 1-2 stages where the emotional experience is worst and what causes it]
Priority Improvements Matrix
| Opportunity | Stage | Severity (H/M/L) | Customers Affected | Effort (H/M/L) | Priority |
|---|---|---|---|---|---|
| [Opportunity 1] | [Stage] | [H/M/L] | [Many / Some / Few] | [H/M/L] | [1-5] |
| [Opportunity 2] | [Stage] | [H/M/L] | [Many / Some / Few] | [H/M/L] | [1-5] |
| [Opportunity 3] | [Stage] | [H/M/L] | [Many / Some / Few] | [H/M/L] | [1-5] |
| [Opportunity 4] | [Stage] | [H/M/L] | [Many / Some / Few] | [H/M/L] | [1-5] |
| [Opportunity 5] | [Stage] | [H/M/L] | [Many / Some / Few] | [H/M/L] | [1-5] |
Filled-Out Example: SaaS Project Management Tool
Persona: Sarah, Head of Product at a 50-person SaaS startup
Journey scope: First Google search to referring a colleague
Map type: Current state
Awareness (Example)
| Dimension | Details |
|---|---|
| Customer goal | Find a better way to manage her team's roadmap and sprint planning |
| Touchpoints | Google search ("best roadmap tool for startups"), blog post on product roadmap best practices, LinkedIn ad |
| Actions | Reads two comparison blog posts, visits three product websites, bookmarks two tools to try later |
| Thinking | "I'm wasting too much time maintaining roadmaps in spreadsheets. There has to be a better way." |
| Feeling | Frustrated with current process, hopeful that a tool can help, slightly overwhelmed by options |
| Pain points | Too many tools to evaluate. Hard to tell which is right for a small team vs. enterprise. Marketing all sounds the same. |
| Opportunities | Create comparison content targeting "roadmap tool for small teams." Be specific about team size fit. |
| Key metrics | Blog traffic from roadmap-related keywords, branded search volume |
Onboarding (Example)
| Dimension | Details |
|---|---|
| Customer goal | Get her team set up and start using the tool for the current sprint |
| Touchpoints | Welcome email series, in-app setup wizard, help center, optional kickoff call with CS |
| Actions | Creates workspace, invites 3 teammates, imports backlog from spreadsheet, creates first roadmap view |
| Thinking | "I need to show my team value quickly or they'll go back to the spreadsheet." |
| Feeling | Anxious about whether the team will adopt it. Mildly frustrated by the import process. Relieved when the first roadmap view looks good. |
| Pain points | CSV import failed on first attempt due to formatting. No clear guidance on which view to set up first. Invite flow required teammates to create passwords before seeing anything. |
| Opportunities | Offer a pre-built "Startup Sprint" template. Let invited users see the workspace before creating an account. Auto-detect CSV formatting issues and suggest fixes. |
| Key metrics | Onboarding completion rate (currently 52%), time to first roadmap created (currently 45 minutes), Day-1 team activation (currently 18%) |
Adoption (Example)
| Dimension | Details |
|---|---|
| Customer goal | Make the tool her team's single source of truth for roadmap and sprint planning |
| Touchpoints | Weekly usage, feature announcements via email, in-app tips, monthly webinar, support chat |
| Actions | Uses the tool daily for standups, tries the timeline view for the first time in week 3, sets up a Slack integration in week 4, requests a Jira integration |
| Thinking | "This is working for roadmap but I wish it connected to our dev workflow in Jira." |
| Feeling | Growing confidence in the tool. Mildly frustrated by the lack of a Jira integration. Delighted when she discovers the timeline view. |
| Pain points | No native Jira integration (most requested feature). Advanced reporting requires upgrading to a higher tier. New team members do not receive any onboarding after being invited. |
| Opportunities | Build Jira integration or prominent Zapier workaround. Send a "week 3" email highlighting the timeline feature. Create an in-app onboarding flow for invited (non-admin) users. |
| Key metrics | WAU per account (currently 3.2 of 5 seats), feature adoption for timeline view (currently 34%), Jira integration requests (127 in last quarter) |
Emotional Journey Summary (Example)
| Stage | Emotion | Intensity (1-5) | Key Driver |
|---|---|---|---|
| Awareness | Frustrated but hopeful | 3 | Current tool pain drives search |
| Consideration | Cautiously optimistic | 3 | Product looks good but hard to compare |
| Purchase | Confident | 4 | Free trial reduced risk |
| Onboarding | Anxious | 2 | Import issues and unclear first steps |
| Adoption | Growing confidence | 4 | Tool delivers value, some gaps remain |
| Advocacy | Willing but not prompted | 3 | Happy enough to recommend if asked |
Primary emotional low point: Onboarding. The CSV import failure and lack of clear guidance create anxiety. This is the most impactful stage to improve because it is where we lose the most users.
Tips for Getting the Most Out of This Template
- Use real customer quotes. Instead of summarizing what customers think and feel in your own words, paste actual quotes from interviews, support tickets, and reviews. This keeps the map grounded in reality and makes it more compelling when shared with stakeholders.
- Map one persona at a time. Resist the temptation to create a "universal" journey map. A self-serve startup user and an enterprise buyer going through procurement have completely different journeys. Create separate maps for each key persona.
- Involve frontline teams. Your support, sales, and customer success teams interact with customers daily. They know where the journey breaks down in ways that product and design teams often do not. Include them in the mapping session.
- Validate with data. After mapping the journey based on qualitative input, overlay quantitative data. Do the analytics confirm the pain points you identified? If 60% of users drop off during onboarding, the pain point you mapped at that stage is validated.
- Revisit the map quarterly. Customer journeys change as your product evolves, as you enter new markets, and as competitors shift. A journey map from a year ago may no longer reflect reality.
- Focus on moments of truth. Not all touchpoints are equally important. Identify the 3-4 "moments of truth". Interactions where the customer either deepens their commitment or considers leaving. Invest disproportionately in getting those moments right.
- Use the priority matrix. A journey map that does not lead to action is just a poster on the wall. Use the priority improvements matrix to convert insights into a ranked list of initiatives for your roadmap.
Key Takeaways
- Journey maps capture the full customer experience across six stages: Awareness, Consideration, Purchase, Onboarding, Adoption, and Advocacy
- The most valuable part of a journey map is identifying specific pain points and the opportunities they create
- Always ground the map in real customer data. Interviews, support tickets, analytics, and reviews
- Map one persona at a time and revisit the map quarterly
- Use the priority improvements matrix to translate journey insights into roadmap initiatives
About This Template
Created by: Tim Adair
Last Updated: 2/8/2026
Version: 1.0.0
License: Free for personal and commercial use