LibraryZenithRequest a breakdown
Research DocsStandardExperience strategyTeam handoff

Documentation reference

Journey Map

A journey map shows how a user moves through a problem, product, or service over time. It connects user actions, touchpoints, emotions, pain points, opportunities, and product moments.

Overview

What this document is

A journey map shows how a user moves through a problem, product, or service over time. It connects user actions, touchpoints, emotions, pain points, opportunities, and product moments.

Journey mapUXCustomer experienceTouchpointsOpportunities

Fit signals

When to use it

  • The product spans multiple steps, channels, or stakeholders.
  • Users drop off, get confused, or need handholding across a flow.
  • A founder needs to understand the full experience before designing screens.
  • Product, marketing, sales, and support need one shared view of the customer path.

Audience and ownership

Who uses it

Founders, designers, product managers, marketers, and service teams improving an end-to-end customer or user experience.

FounderUX designerResearcherProduct managerMarketer

Before and after

Where it fits in the build chain

Idea Brief
BRD
PRD
Research
IA
Design System
Architecture
SOW
QA Plan
Launch

Gather before writing

Inputs required

  • Journey stage template
  • Pain/opportunity matrix
  • Touchpoint map
  • Metrics-by-stage checklist

What each part should cover

Section-by-section guide

Stages

Describe the stages clearly enough that a founder, teammate, or AI agent can use it without needing hidden context.

Actions

Describe the actions clearly enough that a founder, teammate, or AI agent can use it without needing hidden context.

Touchpoints

Describe the touchpoints clearly enough that a founder, teammate, or AI agent can use it without needing hidden context.

Pain points

Describe the pain points clearly enough that a founder, teammate, or AI agent can use it without needing hidden context.

Opportunities

Describe the opportunities clearly enough that a founder, teammate, or AI agent can use it without needing hidden context.

Metrics

Make the standard observable so the team can review, approve, or reject the output without guessing.

Practical workflow

How to create and use it

  1. 01Choose a specific persona and journey.
  2. 02Map stages, actions, touchpoints, emotions, and blockers.
  3. 03Identify product, content, service, and automation opportunities.
  4. 04Feed opportunities into PRD, IA, onboarding, and roadmap.

Copy into your workspace

Starter template

  1. 01Pick one persona and one journey.
  2. 02Map stages, actions, touchpoints, pains, and questions.
  3. 03Identify opportunities, owners, metrics, and experiments.
  4. 04Connect journey outputs to PRD and design priorities.

Make the draft usable

Weak vs strong examples

Objective

Weak

Create a journey map for the product.

Strong

Map user stages, actions, emotions, pain points, touchpoints, opportunities, and product interventions. Define the decisions it must unlock, the inputs required, and the handoff assets needed for the next team.

Handoff

Weak

Share the document with the team.

Strong

Share the approved journey map with owners, open questions, acceptance checks, and the next document in the build chain.

How to know it is useful

Quality checklist

  1. 01The map follows a specific persona and journey.
  2. 02Pain points link to opportunities or product decisions.
  3. 03Touchpoints and ownership are visible.
  4. 04The map informs PRD, IA, onboarding, or service design.

Before you hand it off

Document readiness checklist

  • The journey map has a named owner and approval path.
  • The business or product decision this document supports is explicit.
  • Inputs, assumptions, and open questions are separated from confirmed facts.
  • Scope boundaries and non-goals are clear enough to prevent silent expansion.
  • The document can be handed to a teammate, agency, or AI agent without hidden context.
  • The map follows a specific persona and journey.
  • Pain points link to opportunities or product decisions.
  • Touchpoints and ownership are visible.

Generate the first draft

AI prompt

Draft prompt

Create a journey map for this product and persona. Include journey stages, user goals, actions, touchpoints, emotions, pain points, questions, blockers, opportunities, product interventions, content needs, metrics, owners, and PRD implications.

Avoid these

Common mistakes

  • Mapping a generic lifecycle instead of a real user journey.
  • No evidence or user quotes.
  • No product decisions attached to opportunities.
  • Ignoring non-product touchpoints like sales, email, and support.

Use this after the draft

Handoff assets

  • Journey map
  • Opportunity backlog
  • Stage metrics
  • PRD and onboarding implications

Suggested build path

What to create before and after

Before

Idea Brief

Keep this connected so the build stays traceable.

Current

Journey Map

Use this page to create the working draft.

After

PRD

Keep this connected so the build stays traceable.

Zenith CTA

Need this shaped for your business?

Zenith can turn rough notes into a founder-ready journey map.

Bring your idea, current docs, users, constraints, and open questions. We will help make the next decision clear.

Request a breakdown