mcpField

Customer Journey Mapper

github.com/eddiebe147Marketing & growth46 installs
Repository

About Customer Journey Mapper

Customer Journey Mapper is a skill for mapping and improving customer experiences, for marketing, CX, and product teams. It covers journey stages, touchpoints, emotions, friction, and opportunities across channels.

Key features

  1. 01Journey stage and goal mapping
  2. 02Touchpoint and channel audits
  3. 03Emotion and friction analysis
  4. 04Persona-based journey development
  5. 05Journey gap and opportunity analysis
  6. 06Optimization and measurement planning

Use cases

  1. 01Mapping a persona's customer journey
  2. 02Auditing touchpoints across channels
  3. 03Finding friction and missing interactions
  4. 04Prioritizing experience improvements

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/eddiebe147/claude-settings --skill customer-journey-mapper

After installing, type/customer-journey-mapperin Claude Code to confirm it loaded.

Details

From the project README

Customer Journey Mapper

Visualize and optimize every step of the customer experience from first awareness to loyal advocacy. This skill helps you understand how customers actually interact with your brand, identify friction points, and design experiences that convert and retain.

Customers don't think in channels - they think in experiences. This skill provides frameworks for journey stage definition, touchpoint mapping, emotion tracking, and gap analysis. Transform siloed channel thinking into holistic experience design that meets customers where they are.

Essential for marketing strategists, CX professionals, product managers, and anyone designing customer experiences.

Core Workflows

Workflow 1: Journey Stage Mapping
  1. Stage Definition - Awareness, consideration, decision, retention, advocacy
  2. Customer Goals - What they're trying to achieve at each stage
  3. Questions and Concerns - What they need to know
  4. Touchpoint Inventory - Where they interact with brand
  5. Content Needs - Information required at each stage
  6. Conversion Actions - Desired behaviors per stage
  7. Transition Triggers - What moves them forward
Workflow 2: Touchpoint Analysis
  1. Channel Mapping - All interaction points
  2. Touchpoint Audit - Quality of each interaction
  3. Moment of Truth Identification - Critical experiences
  4. Friction Point Detection - Where customers get stuck
  5. Emotional Journey - Highs and lows of experience
  6. Gap Identification - Missing touchpoints
  7. Optimization Prioritization - Where to improve first
Workflow 3: Persona Journey Development
  1. Persona Selection - Which customer to map
  2. Scenario Definition - Specific journey context
  3. Step-by-Step Documentation - Detailed journey stages
  4. Thought Capture - What customer is thinking
  5. Emotion Mapping - How they feel at each point
  6. Pain Point Highlighting - Frustration moments
  7. Opportunity Tagging - Improvement possibilities
Workflow 4: Journey Optimization
  1. Friction Removal - Eliminate barriers
  2. Moment Enhancement - Elevate key experiences
  3. Gap Filling - Add missing touchpoints
  4. Consistency Improvement - Align cross-channel
  5. Personalization Points - Where to customize
  6. Measurement Integration - Track journey metrics
  7. Continuous Improvement - Ongoing optimization cycle

Quick Reference

ActionCommand/Trigger
Map journey"Map customer journey for [persona]"
Stage definition"Define journey stages for [product/service]"
Touchpoint audit"Audit touchpoints for [journey stage]"
Friction analysis"Identify friction in [journey/channel]"
Emotional mapping"Map emotional journey for [scenario]"
Gap analysis"Find gaps in customer journey"
Moment enhancement"Improve experience at [touchpoint]"
Journey template"Create journey map template"

Best Practices

  • Start with research - Journeys should reflect reality, not assumptions
  • Map from customer perspective - Their experience, not your processes
  • Include emotions - How they feel matters
  • Be specific - "Awareness" is too vague; define clearly
  • Cross-functional input - Sales, support, product all have insight
  • Prioritize ruthlessly - Can't fix everything at once
  • Moments of truth - Focus on make-or-break experiences
  • Measure journey health - Metrics at each stage
  • Iterate continuously - Journeys evolve
  • Visualize effectively - Maps should be scannable
  • Include offline - Physical experiences count
  • Consider negative paths - Map what happens when things go wrong
  • Segment journeys - Different personas, different journeys
  • Test changes - Validate improvements with real customers
  • Share broadly - Journey maps inform entire organization

Comments

Markdown supported