Momentum Bias

Give people a genuine head start without taking the decision away from them.

What it is

Momentum bias is the deliberate use of a head start to get someone past the hardest part of any task: the first move. That head start can be a pre-filled draft they can edit or delete, a workspace with sensible starter content already in it, a suggested first step, or an honest checklist that shows real progress already made. It overlaps with, but is distinct from, Setup Defaults: a default is a single sensible choice offered once, while momentum bias is the broader pattern of using any visible, editable progress—defaults included—to shrink the psychological distance between “I haven’t started” and “I’m already partway there.” It is also distinct from Gamified Progress, which tracks a user’s own accumulating effort over the life of a goal; momentum bias is specifically about the opening move, before the user has done anything at all.

A new user staring at an empty project, an empty inbox, or a blank canvas faces a decision cost that has nothing to do with skill—there is simply no obvious first move. A product that hands them a populated example, a first draft built from their stated goal, or a short checklist where one or two steps are already, truthfully, ticked off turns that blank page into an editable starting point instead of a test.

Why it works

Starting is disproportionately hard because ability, not motivation, is usually the actual blocker at that moment—the same insight Friction builds its removal-first rule on. A head start attacks ability directly: there is less to do, less to decide, and less uncertainty about whether a first attempt will look right. The goal-gradient effect—people speed up as a goal feels closer, not just as it feels more valuable—means that even a small, honest amount of visible progress changes effort, not just mood, which is why a checklist with two of six boxes already filled can move someone to finish the other four faster than an empty six-box list ever would.

The mechanism only works if the progress is real and the person keeps control of it. The moment a head start becomes something owed—a progress bar padded with steps nobody asked for, a draft the user can’t meaningfully change, a streak that punishes the one day they didn’t show up—the same pull that motivated them starts to feel like pressure instead of encouragement, and User Agency is the test that catches it: told exactly how the progress bar was built, would this person still call it fair? Skip momentum bias entirely and the failure is quieter but just as real: every new user is left to solve the blank-page problem alone, with no complaint filed, just a silent drop-off before the first real step.

When to use it

• During onboarding, when a user has chosen a goal but does not know where to begin
• When a draft, template, or Setup Defaults choice can save genuine effort
• When a checklist represents meaningful steps towards an outcome
• When a user returns to unfinished work and needs a respectful re-entry point

Do

• Pre-fill only information the user expects, can inspect, and can edit
• Show progress against meaningful work, not arbitrary screens viewed
• Let users skip, remove, or change suggested steps without penalty
• Use Gamified Progress only when the indicator supports a real user goal

Don’t

• Mark tasks complete before the user or product has genuinely completed them
• Preselect paid, sharing, notification, or data-use choices for convenience
• Inflate a progress bar with vanity steps
• Turn streaks or unfinished work into guilt, pressure, or loss aversion

Founder Tip

A good head start says “here is useful work already prepared for you”, not “you owe us completion”.

Make It Yours

1. What first meaningful outcome can a new user reach quickly?
2. Which blank page could become an editable, clearly labelled draft?
3. Does every completed step represent value the user has actually received or created?
4. Which defaults require explicit choice because they affect money, privacy, or communications?
5. Can a user abandon, revise, or return later without losing their work or being shamed?

Related concepts

• Friction
• User Agency
• Habit Formation

Further reading

• The Goal-Gradient Hypothesis Resurrected — foundational research on increasing effort near a goal.
• Nielsen Norman Group: The Power of Defaults — how defaults shape decisions and where care is required.
• The Progress Principle — Teresa Amabile and Steven Kramer on meaningful small wins.
• UK ICO: Data Protection by Design and Default — why privacy-affecting defaults must protect users.

Agent skill

• Primary command: /productfeeling friction — audit truthful progress and head starts that reduce starting effort without removing agency
• Related commands: /productfeeling peaks-ends, /productfeeling states, /productfeeling delight
• When the agent should load this TTP: “head start”, “progress checklist”, “onboarding momentum”, “blank page problem”, “starter template”
• Companion handoff: Impeccable — progress UI, checklists, and editable default craft
• Feeling north star this TTP serves: genuine momentum with user control
• Anti-goals: fake progress, preselected paid or sharing choices, vanity steps, guilt streaks
• Reference path: skill/reference/friction.md