Journey maps aren't primarily for understanding your users. Your best PMs probably understand the user journey already. Journey maps are for creating organizational alignment about where the gaps are and who owns fixing them.
That's the frame that makes them worth building.
The 5 Stages of a SaaS Customer Journey
Most SaaS products map to five stages. Some products collapse or expand these, but this structure works for the majority of B2B and B2C SaaS products.
1. Awareness: The user realizes they have a problem and starts looking for solutions. They may not know your product exists yet.
2. Consideration: The user is evaluating options. They've found you and a few competitors. They're reading reviews, watching demos, talking to peers.
3. Onboarding: The user has signed up or purchased. They're setting up the product and trying to reach first value.
4. Activation: The user has experienced the core value at least once. They're starting to build habits around the product.
5. Retention and Expansion: The user is a regular. They may be expanding usage, advocating internally, or at risk of churning.
What Belongs in Each Cell
For each stage, capture these five rows:
User Actions: What is the user actually doing? Not what you want them to do. What does the data and research say they're doing?
Emotional State (0-10): Rate the overall emotional experience. 10 is delighted, 0 is frustrated enough to leave. Keep the scale consistent across stages so you can see where the dips are.
Pain Points: What's creating friction, confusion, or dissatisfaction? Be specific. "Onboarding is confusing" is not a pain point. "Users can't find the data import option because it's buried in Settings > Advanced > Integrations" is.
Opportunities: What could you change to improve the experience at this stage? These become candidate roadmap items.
Internal Owner: Which team is responsible for this stage? Sales? Marketing? Product? Customer success? No owner means no accountability.
A Filled-In Example: B2B Analytics SaaS
This is a simplified map for a fictional B2B analytics tool targeting operations managers at mid-size companies.
Stage: Onboarding
User Actions: Signs up for trial. Receives welcome email. Lands on dashboard with no data. Tries to connect data source. Hits OAuth error with Salesforce integration. Emails support.
Emotional State: 3/10. Excitement from signup drops fast when the product feels empty and the integration fails.
Pain Points:
- Dashboard shows no data on first login, which feels broken
- Salesforce OAuth requires admin permissions the user doesn't have
- Support response time is 6-8 hours, which means the user loses a full day
Opportunities:
- Add sample data mode so the dashboard feels alive on day one
- Build a "request admin access" flow directly in the OAuth error state
- Add live chat during business hours for trial users in first 72 hours
Internal Owner: Product (dashboard, sample data, OAuth flow), Customer Success (live chat, support SLA)
Stage: Activation
User Actions: Builds first report. Shares it with manager. Gets positive feedback. Returns next day to build a second report.
Emotional State: 7/10. First real output creates genuine satisfaction, but the path to it was rough.
Pain Points:
- Report sharing requires exporting to PDF manually. No direct share link exists.
- No notification when manager views the report
- Building a second report from scratch restarts the process (no templates)
Opportunities:
- Add direct share links for reports
- Add view notifications
- Create three starter report templates based on the most common first reports
Internal Owner: Product
This pattern repeats for all five stages. The map is a living document. Update the pain points and emotional state as you get new data from research and analytics.
For more on building the research foundation that makes journey maps accurate, see the complete guide to user research and the product discovery guide.
The Template (Copy This)
Use this table structure for your map. Build one table per stage, or use a spreadsheet with stages as columns and the five rows as rows.
Stage: [Stage Name]
| Row | Content |
|---|---|
| User Actions | [What the user is doing at this stage] |
| Emotional State (0-10) | [Rating + one-sentence explanation] |
| Pain Points | [Specific, concrete friction points] |
| Opportunities | [Candidate improvements] |
| Internal Owner | [Team responsible] |
Common Mistakes
Mapping only the happy path. The most common journey map mistake. If your map shows a smooth, positive experience at every stage, either your product is exceptional or you're not being honest. Most journey maps need to show where emotion dips and why.
Making it too detailed to be useful. A journey map with 40 pain points across 8 stages doesn't drive decisions. It overwhelms them. Prioritize ruthlessly. Five sharp pain points with clear owners beat a catalog of 40.
Not assigning owners to gaps. Every opportunity on the map should have a team or person responsible. If an opportunity has no owner, it won't become a roadmap item. It'll stay on the map forever.
Building it once and never updating it. A journey map from 18 months ago is probably wrong. Update it after major product changes, segment shifts, or new research rounds.
How to Use the Map in Product Planning
At the end of a mapping exercise, you should be able to answer three questions:
- Which stage has the worst emotional experience (lowest 0-10 rating)?
- What's the highest-impact, most feasible opportunity at that stage?
- Which team owns it and what would it take to address it?
Those answers feed directly into roadmap planning. Use a prioritization framework to rank the opportunities from the map against each other. The RICE calculator is a good tool for this: score each opportunity on Reach, Impact, Confidence, and Effort.
For teams connecting journey map findings to stakeholder conversations, the stakeholder management guide covers how to present user research findings to executives in a way that drives prioritization decisions rather than just informing them.
Workshop vs. Solo
Build it solo when you need a first draft quickly, you already have strong research, or you need a working document to anchor a future workshop.
Run a workshop when cross-functional alignment is the goal, when different teams have different (and possibly conflicting) views of the customer experience, or when you want to generate organizational ownership of the outcomes.
The workshop version takes more time but produces a map that different teams feel invested in. That investment is what drives the follow-through on fixing the gaps.
A good workshop agenda: 30 minutes of input on user actions and emotional state, 45 minutes on pain points (one team at a time, so sales and CS bring their perspective before product does), 30 minutes on opportunities, 15 minutes assigning owners.