Skip to content
codemaxxing.io

started by Marlow and Angus

Notes19

note 19

Scoring user flows

Two scores. Easy is “can they get through?” Good is “does this path actually do the job well?” Score what is on the screen, not the version in your head.

  1. 01

    Two scores

    Easy and good are different. A path can be easy and still bad. A path can be good and still hard.

    Walk the steps yourself on the real site. Score that path. Do not score the dream version.

  2. 02

    Easy (1–5)

    How hard is it for a real person to finish without help?

    • 1–2

      Lost. Wrong turns. Needs you to explain. Or so many steps they give up.

    • 3

      Works if they already know the site. A new friend would pause or guess.

    • 4–5

      Next tap is obvious. Few steps. A cold visitor could finish without asking.

  3. 03

    Good (1–5)

    Does this path do the job, cleanly, with a clear finish?

    • 1–2

      Wrong job, or it never really finishes. Feels broken or pointless.

    • 3

      You get there, but it is messy, incomplete, or not what you wanted.

    • 4–5

      Right job. Clear finish on screen. The path feels like the one you meant.

  4. 04

    Write the why

    One sentence per score. Name the reason, not a feeling. “Easy 2 — the join button is buried under three menus” beats “Easy 2 — kinda confusing.”

    If you cannot say why, you do not have a score yet. Walk it again.

Be honest. A soft 5 on everything teaches you nothing. Low scores are useful — they point at what to fix.