Builder's Brain
Builder's Brain · the neuroscience of building · ◉ Evergreen

Give them a head start they didn't earn

by Shreyansh Ojha·4 min·Working Theory

Here’s an experiment with coffee cards that should change how you build any progress bar. Researchers handed customers a loyalty card at a car wash. Half got a card with eight stamps to fill; the other half got a card that needed ten stamps but arrived with two already stamped for free. Do the arithmetic and the two are identical — both groups need eight more washes to earn the reward. But the second group, the ones handed a head start they hadn’t earned, completed the card at nearly double the rate, and got there faster. Two free stamps on a longer card beat a shorter card starting from zero. Nothing about the work changed. Only the frame did.

Two things are going on, and both are useful. The first is the goal-gradient effect: the closer you get to a goal, the harder and faster you push toward it. It’s old — Clark Hull watched rats run faster down the final stretch of a maze than the first — and it holds in people just as cleanly: purchases accelerate near a reward, effort ramps as a bar fills. The second is endowed progress: if you give someone artificial forward motion — start them at 20% instead of 0% — you drop them into the part of the curve where the pull is already working. An empty bar sits at the flat, unmotivated bottom. A bar that’s already moving borrows the acceleration of being near the end, even when the end is exactly as far away in real terms.

starts at zero — 8 to go starts at 2 of 10 — also 8 to go same 8 left — the endowed card gets finished more.
Identical work remaining. The card that arrives already in motion drops the user into the accelerating part of the curve. Original diagram · Working Theory

The build moves are almost embarrassingly concrete. When you show a setup checklist, don’t start it at zero — count the account they just created, the email they just verified, as steps already done, so the bar reads “3 of 7” on arrival instead of “0 of 4.” When you design a profile or onboarding, order it so the first thing is trivially easy and already half-true, and let the momentum carry into the harder asks. For any progress toward a reward — a plan, a streak, a completion meter — the acceleration lives near the finish, so make the finish feel close early rather than parking people at a distant, flat-bottomed start. You’re not adding work. You’re changing where on the curve the user begins.

The honest caution is the same one every motivation tool comes with: the progress you endow has to be real, or at least fairly framed. Counting steps the user genuinely completed is honest. Inventing a “80% done!” bar that secretly resets, or that measures nothing, is the dark-pattern version — it works once, and then the user notices the finish line receding and stops trusting your bars entirely, which poisons every future one. And be clear-eyed about the size of the lever: endowed progress moves completion rates among people who already wanted the reward. It doesn’t make anyone want something they didn’t. It’s a nudge on follow-through, not a substitute for a reason to start.

So the question for any first screen with a goal behind it: are you asking the user to set out from zero, or handing them a card that’s already moving? The work in front of them can be identical. Whether they finish it often isn’t.

The science, to look up: the goal-gradient effect and endowed progress (Ran Kivetz, Oleg Urminsky & Yuhuang Zheng, 2006, 'The Goal-Gradient Hypothesis Resurrected' — the car-wash loyalty-card study); Clark Hull's original goal-gradient work in animals; the near-miss and progress effects in motivation. Real and replicated, but a framing effect of modest size — it moves rates, it doesn't manufacture desire.

Liked this? Get the next one in Working Theory.

Going weekly in August (it's in beta now). One genuinely interesting read on building, the brain, and the science most people missed.

Got a reaction, a counter-example, or something I missed? Reply by email — I read everything.
◉ join in

Where have you hit this — in a product you use, or one you're building?

Threads open here soon. For now, the conversation lives two clicks away — discuss on GitHub, or just reply by email. I read and answer everything.