End-to-End Flow

An end-to-end flow maps the entire designed path from a person's first touchpoint to the final business outcome — ad to renewal, search result to referral — as one connected sequence of the product's flows. It is the master flow that the detailed flow files in this section plug into: where a journey map (04, 05) records what the person EXPERIENCES across that span, the end-to-end flow specifies what you BUILT (and instrumented) across it.

Why bother

Teams optimize the screen in front of them while the full experience leaks between screens. Signup converts beautifully into an onboarding nobody finishes; support resolves tickets into a renewal nobody sends; the landing page promises a feature the first-run flow hides. The end-to-end flow exists to catch exactly this: every handoff is drawn, owned, and measured, so "we improved our step" can't pass for "the user succeeded."

Use it when: kicking off a new product (skeleton before any detailed flow), diagnosing growth ("signups are up, revenue isn't" — the leak is between stages), or auditing an old product where each stage was redesigned separately and the seams no longer line up.

The canonical stage sequence

Discovery → Evaluation → Signup → Onboarding → Usage → Support → Retention → Renewal/Referral

Each stage is a summary node; the detail lives in a sibling file:

Example with the metric per stage

One SaaS end-to-end flow, with the number that tells you whether each stage works. The metric names follow practitioner conventions — loosely the AARRR "pirate metrics" frame (acquisition, activation, retention, referral, revenue) from Dave McClure's 2007 "Startup Metrics for Pirates" talk — conventions, not standards; define each metric precisely for your own product before anyone dashboards it.

Ad → Landing → Signup → Onboarding → First Project → Repeated Use
   → Support → Upgrade → Renewal → Referral

Ad → Landing          click-through, cost per visit   (acquisition)
Landing → Signup      visit→signup conversion         (acquisition)
Signup → Onboarding   signup→setup-complete rate
Onboarding → First    activation: % reaching first
  Project             value moment, time-to-value     (activation)
First → Repeated Use  week-1/week-4 retention,
                      frequency of core action        (retention)
Repeated Use →        contact rate, resolution time,
  Support             post-ticket retention delta
Support/Use →         free→paid or tier-upgrade
  Upgrade             conversion                      (revenue)
Upgrade → Renewal     renewal rate / churn, net
                      revenue retention (expansion)   (revenue)
Renewal → Referral    invites sent, referral-sourced
                      signups                         (referral)

Two reading rules. First, multiply, don't admire: 60% × 50% × 40% × 30% through four stages means ~3.6% of visitors ever reach repeated use — the end-to-end number no single stage dashboard shows. Second, fix the deepest leak first: improving Discovery pours more water into whatever bucket is currently leaking at Onboarding.

Relationship to funnels and journey maps

• Funnel: the measurement view — the same stages as conversion percentages, strictly forward and lossy. The end-to-end flow is the design behind the funnel: it includes loops (Support → Usage, Renewal → Referral → someone else's Discovery), re-entries, and paths a funnel flattens. When a funnel stage drops, open the flow (and its detailed file) to see what's actually on that path.
• Journey map (04/05): the experience view — same span, but evidence of what people do/think/feel, including off-product touchpoints you didn't design. Journey map finds the pain; end-to-end flow locates which built flow owns it; the detailed flow file redesigns it. Use all three; they disagree in useful ways.

How to build it

1. Draw the stage skeleton (one line, arrows) for YOUR product — rename or drop stages honestly; a free tool has no Renewal, a marketplace has two sides.
2. For each stage: entry point, exit condition ("what must be true to move on"), owning team, and the one metric per the table above.
3. Link each stage node to its detailed flow file; create missing ones rather than bloating this map — the end-to-end flow should fit on one screen.
4. Mark the handoffs (email → app, sales → product, product → billing) as explicit steps, not gaps — handoffs are where end-to-end experiences die (see Customer Journey Map's seams row and Service Blueprint for what's behind each).
5. Instrument stage-to-stage conversion before optimizing anything.

Common mistakes

• A stage list with no exit conditions — if you can't say what "done with onboarding" means, you can't measure or design it.
• Treating it as a funnel: no loops, no re-entry, no referral edge back to Discovery.
• Optimizing the easiest stage instead of the leakiest.
• Detail creep: every stage's error paths inline until the map is unreadable — that detail belongs in the sibling files.
• No owner per handoff; each team owns a box, nobody owns an arrow.
• Metrics chosen for dashboard appeal (Goodhart's law — see UX Strategy) rather than for exposing leaks.

Checklist

• Stage skeleton fits on one screen, arrows and loops included
• Entry point, exit condition, owner, and metric per stage
• Every stage links to its detailed flow file (or one is created)
• Handoffs drawn as steps with named owners, not gaps
• Referral/renewal loops drawn back to Discovery
• Stage-to-stage conversion instrumented; end-to-end product computed
• Metric definitions written down (conventions localized, not assumed)
• Cross-checked against the journey map's pain points (04/05)
• Revisited when any stage's detailed flow changes

Sources

• McClure, D. (2007). "Startup Metrics for Pirates" (AARRR) — originating talk for the acquisition/activation/retention/referral/ revenue convention (slides widely republished; slideshare.net/dmc500hats).
• Nielsen Norman Group — Gibbons, S. (2018). "Journey Mapping 101"; Kaplan, K. (2023). "User Journeys vs. User Flows" (nngroup.com) — the experience-view counterparts to this design-view map.
• Kalbach, J. (2016; 2nd ed. 2020). Mapping Experiences. O'Reilly — aligning experience maps with business models and metrics.
• Shostack, G. L. (1984). "Designing Services That Deliver." HBR — the behind-the-stages view (via Service Blueprint).