home / skills / gtmagents / gtm-agents / journey-mapping

This skill helps teams map cross-functional journeys using data-backed insights to align stakeholders and drive actionable improvements.

npx playbooks add skill gtmagents/gtm-agents --skill journey-mapping

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.3 KB
---
name: journey-mapping
description: Use to facilitate cross-functional journey mapping with data-backed insights.
---

# Journey Mapping Toolkit Skill

## When to Use
- Kicking off new persona journeys or refreshing existing ones.
- Preparing workshops with stakeholders across marketing, product, CS, and sales.
- Auditing journey artifacts for consistency and completeness.

## Framework
1. **Preparation** – collect VOC findings, telemetry, and existing documentation; define scope, persona, and goals.
2. **Stage Definition** – align on lifecycle stages, success metrics, and ownership.
3. **Touchpoint Mapping** – capture channels, emotions, expectations, and supporting systems.
4. **Gap Identification** – document friction points, root causes, and opportunities.
5. **Action Linking** – connect gaps to initiatives, success metrics, and measurement plans.

## Templates
- Journey storyboard canvas (stage, touchpoint, emotion, KPI, owner).
- Persona one-pager with goals, pains, and preferred channels.
- Gap log sheet (issue, impact, evidence, owner, next step).

## Tips
- Keep sessions interactive with pre-read data and live polling.
- Include frontline voices (support, sales, CSMs) for real-world context.
- Version control maps so improvements are traceable over time.

---

Overview

This skill helps teams run cross-functional journey mapping workshops and produce data-backed customer journey artifacts. It combines a clear five-step framework with ready templates to align stakeholders, surface gaps, and link findings to measurable initiatives. The goal is actionable maps that drive prioritized improvements across marketing, product, sales, and customer success.

How this skill works

The skill guides preparation by collecting VOC, telemetry, and existing docs, then facilitates stage definition, touchpoint capture, gap identification, and action linking. It provides structured templates (storyboard canvas, persona one-pager, gap log) and prompts to surface evidence and owners. Outputs include versioned journey maps, prioritized gap logs, and measurement plans tied to KPIs and initiative owners.

When to use it

  • Kicking off a new persona journey or refreshing an existing one
  • Preparing a cross-functional workshop with stakeholders from marketing, product, CS, and sales
  • Auditing existing journey artifacts for consistency and completeness
  • Prioritizing customer experience improvements tied to measurable outcomes
  • Creating alignment on lifecycle stages, success metrics, and ownership

Best practices

  • Collect VOC and telemetry before sessions so discussions are evidence-led
  • Invite frontline staff (support, sales, CSMs) to surface real customer behavior and pain points
  • Use live polling and interactive exercises to keep workshops focused and participatory
  • Define clear owners and measurable success metrics for every identified gap
  • Version control maps and logs so improvements and decisions are traceable over time

Example use cases

  • Run a half-day workshop to define lifecycle stages and align on owner responsibilities
  • Audit an existing onboarding map to identify friction points and propose tracked fixes
  • Develop persona one-pagers and storyboard canvases before product launch to align go-to-market teams
  • Maintain a gap log that links customer issues to product, content, or operational initiatives with owners and KPIs
  • Prioritize CS and sales handoff improvements by mapping touchpoints and measuring churn impact

FAQ

How long should a typical journey mapping workshop take?

Plan for 2–4 hours for a focused session; a full discovery and mapping effort often spans multiple workshops over 1–2 weeks with prep and follow-up.

What evidence should I bring to workshops?

Bring VOC summaries, support tickets, product telemetry, NPS comments, and any existing maps or playbooks to ground discussions in real data.