User journey flow

The flow must be available at all times and updated dynamically if possible. Transparency is non-negotiable: all PMs and all team members should have access to it. A map locked in a single PM's Figma is not a flow — it's a souvenir.

The structure of the flow is defined based on observed activity, not on assumed paths. Every node and every edge carries a percentage — the share of users that reached that step or took that branch over the rolling window. The data drives the diagram, not the other way around.

The visualization is a tree of all the steps with the option to zoom in and out. At each step, the percentage of users present is shown. This is a flow analysis tool — its job is to:

• Highlight blockers. Where does volume drop off? How sharply?
• Surface dead ends. Steps from which users cannot continue and cannot return.
• Reveal lack of options. Branches that should exist but do not.
• Catch no-return paths. Flows that trap users into a state they cannot exit gracefully.

It is, above all, a strong visualization tool — the kind that makes a problem obvious in three seconds during a stakeholder review.

Each path is associated with the proper tags (segment, surface, funnel stage) and can be visually highlighted. From there, data can be pulled and the path can be linked to Jira tickets — past and present — that touched it.

This is what makes the flow an operational artifact rather than a pretty picture: ROI analysis on what was done, the cost it had, the KPIs before and the KPIs after — all attached to the segment of the flow it concerns.