5L UX Onboarding Flow

What 5L evaluates and when to use it

The 5L UX Onboarding Flow helps a team diagnose and improve the path to a new user's first valuable outcome. Use it when sign-up works but new users stall before the product does anything useful for them.

A 5L review produces three things:

• a bounded onboarding journey, from entry to first value;
• evidence-backed findings, each linked to TYPENORM's pattern registry;
• a revised flow with explicit hypotheses and the checks that will test them.

The five Ls are lenses applied to the same journey. They are not five onboarding screens or mandatory sequential phases. The review keeps observation, interpretation and recommendation separate, records where each piece of evidence came from, and introduces no new scoring system.

Define first value

Before looking at a single screen, define the user, the relevant context and the first valuable outcome: the earliest point at which the product does something this user came for.

Record whether that outcome comes from research or is a working assumption. A working assumption is a legitimate starting point, but it stays labelled as one until evidence supports it.

The five lenses

Each lens asks a different question of the same journey. The pattern associations under each lens come from TYPENORM's pattern registry.

Language

Can a new user understand what the interface says and what each screen is for?

Starting pattern associations:

• CLR-003 — Internal language in the interface
• CLR-002 — Screen purpose unclear

Load

What does the journey ask of the user before they reach first value?

Starting pattern associations:

• EFF-001 — Detours before first value
• CTX-002 — Known information requested again
• CNV-001 — Wall before value

Layout

Can the user see what to do next and read what matters?

Starting pattern associations:

• CLR-001 — No clear primary action
• CLR-004 — Critical text hard to read
• CLR-006 — Controls not recognizable as controls

Logic

Does the journey hold together from one step to the next?

Starting pattern associations:

• CTX-001 — Context lost between steps
• DEC-002 — Critical information after the decision
• ERR-004 — No safe way back

Loop

Does the product tell the user what is happening, where they are, and when they have arrived?

Starting pattern associations:

• FBK-001 — Silent wait
• FBK-002 — Multi-step flow without progress
• FBK-003 — Completion not acknowledged
• ERR-001 — Error without a recovery path

These are starting associations, not exclusive buckets. The same pattern can matter under several lenses. Record a finding once, under the lens that explains it best, and don't double-count it under the others.

Review one journey with evidence

1. Define the user, the context and the first valuable outcome.
2. Trace the actual route from entry to that outcome, including branches and failure states.
3. Inspect the journey through all five lenses.
4. Record observations, fit rationales, consequences and uncertainties using the Frictions Map structure.
5. Prioritize using the case severity approach and contextual impact, keeping reach and confidence separate.
6. Propose changes and specify how to evaluate first-value completion, understanding and guardrails.

Turn findings into a revised flow and a test plan

A 5L review ends with a revised flow, not a list of complaints. Each proposed change states the hypothesis behind it and how the team will check it: whether more new users reach first value, whether they understand what they reached, and which guardrails must not get worse.

An illustrative example, not drawn from a real product: a team collaboration product asks new users to invite colleagues before they have created anything. Under Load, that request reads as a detour before first value. The revised flow moves the invitation to the point after the user's first piece of work is saved. The hypothesis is that more new users reach that first saved piece of work; the checks are first-value completion, whether users still understand how to invite colleagues later, and invitation volume as a guardrail.

This example is not an observed product finding, and it is not proof that invitations should always be deferred. In a product whose first value depends on a colleague being present, the invitation may be the first value.

How to start

Run a first pass over your onboarding with UX Snapshot, or request a UX audit to have our team review the journey with you. To assess clarity across the whole product rather than one onboarding path, use the sibling UX Clarity Framework.