Checklists need a total and a completed count for progress

What it is

An onboarding checklist splits “becoming usable” into ticks. Progress only exists if people can see how many steps there are and how many are done, as in “3 of 5” or an equivalent bar. “Next” alone, ticks with no denominator, or items silently added mid-way, turn the list into a to-do black hole. This entry is the checklist as a progress device that makes remaining work estimable. It is not whether each item has real value, and not how to diagnose a stall.

Why it happens

The goal-gradient effect needs a visible end. The checklist turns first use from “how much longer” into a computable gap; ticked items make sunk cost explicit, remaining items a finite debt. Without a denominator, every completion might have more behind it, and the gradient has nothing to attach to. A denominator that grows (3 of 5 becomes 3 of 8) voids progress already paid, and the checklist itself reads as a dishonest gate. Progress must also remain visible when the list is collapsed: a chrome line “2 left,” or closing the panel closes the end. Checklists are kin to form steppers, but items are usually completable in any order, so position is not “step 3” but “3 of 5 done”—count matters more than sequence.

Studying it

Build the same setup items as no progress, current item only, “x of n,” and a version that increases n mid-way.

Independent variables: whether a denominator is shown, whether n changes, whether progress remains visible when collapsed. Dependent variables: share who finish all items, completed count at abandon, estimate of remaining work, whether people say items were sprung on them.

Lab checklists are short and compress the gradient. Live products often inject marketing into “finish setup,” which measures a trust break. When order is free, do not use “current step” as the only progress; measure perception of the denominator.

Where it stops holding

One or two setup steps do not need a heavy bar; “still need to connect email” is enough. An always-on “improve your account” list has no stable n and must not pretend to be a finishable onboarding. Experts and migrants have already closed these skills; checklist progress is noise and should be permanently dismissible. When items grow or shrink with plan, lock the denominator at entry and say “n steps for your plan”; do not silently add items after an upgrade and keep the same bar.

Applying it

• Fix “x of n done” in the checklist title or beside it; keep an equivalent when collapsed, not a denominator that exists only in the open panel.
• Lock n when the list is entered; if choices drop items, update the denominator and say why; never grow n before completion without saying so.
• Allow out-of-order ticks; let progress reflect count, not a fake “step 3” that implies a forced order.
• Verify by asking, collapsed and expanded, how many steps there are and how many are done. No denominator, or a silently grown n, means the progress device failed.

Related

• Within the group: H2.09.2 Checklist items should produce value, not ceremonial ticks · H2.09.3 When completion stalls, isolate the stuck step · H2.09.4 Too many checklist items become a burden, not guidance
• Adjacent: H1.01 Form length and multi-step · E5.10 Steppers · H2.02 Empty-state Guidance
• Search terms: onboarding checklist · goal-gradient · setup progress