Plans — Journey Map

Candy-crush style winding path showing how a lead persona walks through the cluster from first touch to conversion, with thought bubbles per stop.

What is it?

A single visual narrative — one path per plan, not one per persona — that orders every piece on a curved spine running awareness → conversion. A single lead persona (picked from the plan's selected personas) walks the path; clicking Play animates them tile by tile. At each stop a thought bubble pops next to the persona showing the question that piece is designed to answer.

When should I use it?

You want to feel the cluster end-to-end as one persona would experience it.
You're presenting the plan to a stakeholder and want a visual that explains why each piece exists.
You're checking whether the funnel stages flow correctly (no jumps from awareness straight to conversion).

How to use it

Open the plan and click the Journey Map tab.
Pick a Lead persona from the header chip row — only that persona's avatar walks the path. The others still appear in the chip list above for context.
Click Play to animate. Pause stops the walker; Reset sends them back to the top. Click any tile to jump directly.
Watch the thought bubble at each stop — the question text comes from the piece's questionsAddressed (filled in by Gemini at plan generation).

Tips and best practices

The lead persona pick is sticky per browser session — return visits remember it.
If the thought bubbles read awkwardly, edit the piece's questionsAddressed on the Pieces tab. Older plans generated before this field existed show a default stage hint instead.
Use the journey map in client presentations — it's the most legible single visual the plan produces.

Gotchas and limits

The walker only follows the canonical spine, even if individual personas had branches in the underlying journey data. Branches render statically below the spine.
Plans with 0 personas show a "?" walker — pick at least one persona for the visual to feel right.
Static (non-animated) snapshot of this map is what lands in the exported PDF — see Export PDF.