gked2121 Customer Journey Mapper
Produce a comprehensive, actionable customer journey map spanning every stage from initial awareness through long-term advocacy.
Contents
references/journey-stages.md— the seven stages and the dimensions to analyze for eachreferences/output-template.md— exact structure for the generatedcustomer-journey.mdreferences/mermaid-diagrams.md— both required Mermaid diagrams and the satisfaction scoring guidereferences/examples.md— invocation examples, research protocol, and ambiguity handling
Workflow
Collect inputs. Gather Product/Service, Target Persona, Touchpoints (optional), and Channels. When any are missing, infer reasonable values and document the assumptions at the top of the output. Ask one clarifying question only when the product type is genuinely unclear.
Research context. Use WebSearch to ground the map in real reviews, complaints, competitor comparisons, and industry patterns. See
references/examples.mdfor the research protocol.Map all seven stages. Build a detailed stage-by-stage analysis covering Awareness, Consideration, Decision, Onboarding, Retention, Expansion, and Advocacy. See
references/journey-stages.mdfor the dimensions to cover per stage.Identify opportunities. Surface pain points, emotional states, and improvement opportunities at every stage. Include honest friction even in generally positive stages, and cross-reference how one stage's issues create downstream effects.
Generate the deliverable. Write
customer-journey.mdto the current working directory followingreferences/output-template.md. Include both Mermaid diagrams perreferences/mermaid-diagrams.md.
Required Inputs
| Input | Description | Example |
|---|---|---|
| Product/Service | What is being sold or offered | "B2B SaaS project management tool" |
| Target Persona | Who the primary customer is | "VP of Engineering at mid-market companies, 200-1000 employees" |
| Touchpoints | Known interaction points (optional) | "Google search, blog, demo request, sales call, onboarding email sequence" |
| Channels | Active marketing/sales/support channels | "Website, email, LinkedIn, phone, in-app, Slack community" |
Quality Requirements
- Minimum 400 lines of substantive content, not padded whitespace.
- Specificity: Tie every touchpoint, pain point, and opportunity to the given product and persona — no generic filler.
- Actionability: Make recommendations concrete enough to begin implementation immediately.
- Measurable metrics: State how each metric is actually measured, not just what to measure.
- Emotional realism: Reflect genuine customer psychology, not idealized happy paths.
- Honest pain points: Include real friction even in positive stages.
- No emojis anywhere in the output document.
- Mermaid validity: Use valid syntax that renders correctly.
- Consistent voice: Keep professional, strategic language throughout — a working document for product and marketing teams.
- Cross-references: Connect each stage's issues to their downstream effects.