customer-journey-map
Visualize customer interactions across all stages—from awareness to loyalty—with documented actions, touchpoints, emotions, KPIs, and team ownership.
- Maps five core stages (Awareness, Consideration, Decision, Service, Loyalty) with customer actions, emotions, touchpoints, business goals, and responsible teams for each
- Combines customer empathy with measurable KPIs to identify pain points and align cross-functional teams on the end-to-end experience
- Requires upfront persona definition, stakeholder input, and touchpoint inventory; designed for ongoing quarterly updates rather than one-time use
- Includes anti-patterns guidance (distinguishes from user story maps and service blueprints) and prioritization framework to focus improvements on highest-impact opportunities
Purpose
Create a comprehensive customer journey map that visualizes how customers interact with your brand across all stages—from awareness to loyalty—documenting their actions, touchpoints, emotions, KPIs, business goals, and teams involved at each stage. Use this to identify pain points, align cross-functional teams, and systematically improve the customer experience to achieve business objectives.
This is not a user flow diagram—it's a strategic artifact that combines customer empathy with business metrics to drive actionable improvements.
Key Concepts
The Customer Journey Mapping Framework
Adapted from NNGroup's framework and Carnegie Mellon's PM curriculum, a customer journey map documents:
Horizontal structure (stages):
- Awareness: Customer first learns about your brand
- Consideration: Customer evaluates your offering
- Decision: Customer makes a purchase
- Service: Customer uses the product/service post-purchase
- Loyalty: Customer becomes a repeat buyer and advocate
Vertical structure (for each stage):
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1K