Sign In Try Free
Workflow-specific products Content, decks, briefs, proposals, legal, and sales each have a clearer buying path.
Review before delivery Draft, edit, collaborate, approve, and export in the same workspace.
Security + procurement path Security policy, support, and Azure Marketplace buying are public.

Gixo Lumen · slide guide

Journey Map Slide

A journey map slide shows the stages someone passes through and what happens at each. It earns its place when it marks where the journey actually breaks — a map with no friction marked is decoration, because every journey has friction.

Lumen layoutProcess
Use it whenShowing where an experience breaks

Last reviewed: August 2026

What belongs on it

  • Four to seven stages. Fewer is a list; more stops being readable across one slide.
  • Stages named as the person experiences them. Their language, not your internal process names.
  • What happens at each stage. One line, concrete.
  • Where it breaks. Marked visually. This is the reason the slide exists.
  • Evidence. A number or a verbatim quote against at least the problem stages.
  • Who owns each stage. Especially where ownership changes hands — that is usually where it breaks.

Getting it right

Weak versionStronger version
Internal process namesThe words the customer would use
Every stage looks equally fineFriction points marked clearly
Twelve stagesFive, with sub-steps in the appendix
Assumed experienceQuotes or numbers per stage
No ownersOwner per stage, handoffs visible

Common mistakes

  • No friction marked. A journey where everything looks fine is not describing a real journey.
  • Internal vocabulary. If your stages are named after your teams, it is a process diagram, not a journey.
  • No evidence. An imagined journey is a hypothesis; label it as one if that is what it is.
  • Too many stages. Past seven the slide becomes a diagram nobody reads in the room.
  • Missing the handoffs. Journeys break where ownership changes, so make those boundaries visible.
Every slide guide here names the Lumen layout that produces it, so you can build the slide directly in a blank deck. Manual building is free and unlimited, and PPTX export carries no paywall on any plan.

Frequently asked questions

What is a journey map slide?

A slide showing the stages someone passes through in an experience, what happens at each, and where the journey breaks down.

How many stages should a journey map have?

Four to seven. Fewer is really a list, and more than seven stops being readable on a single slide in a room.

What makes a journey map useful rather than decorative?

Marked friction points backed by evidence. A map where every stage looks fine is not describing a real journey and gives the audience nothing to act on.

Should stages use customer language or internal names?

Customer language. Stages named after your internal teams make it a process diagram, which answers a different question.

What Lumen layout do I use?

The Process layout for stage flow, or Timeline where the stages are strongly time-based.

Other slide guides

Build this slide in a blank deck

Add the Process layout and fill it in. Manual decks are free and unlimited on every plan, and export to PPTX with no paywall.