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

Push them and they push back

by Shreyansh Ojha·5 min·Working Theory

Tell a two-year-old they can’t have the blue cup and the blue cup becomes the only cup in the universe. We never fully grow out of it. There’s a reflex that fires the moment a person senses a freedom being taken away — a specific, motivating flash of resistance — and it doesn’t care whether the thing being pushed is actually good for them. Deny them an option and they want it more. Force them toward an option and they dig in against it. Psychologists call it reactance, and it is one of the most under-respected forces in product design, because it turns your most forceful tactics into their own worst enemy.

Jack Brehm laid out the theory in 1966, and the core is simple: people believe they have a set of free behaviors, and when one of those freedoms is threatened or eliminated, they experience an unpleasant arousal — reactance — that motivates them to restore it. The restoration takes predictable forms. They do the forbidden thing, or want it more (this is the whole engine of “forbidden fruit” — banning a book sells it). They resist or derogate the thing being pushed. They reassert control some other way. The key subtlety, and the one builders miss, is that it’s triggered by the feeling of a threatened choice, not by constraint in the abstract. A limit you understand and accept doesn’t provoke it. A limit that feels like someone strong-arming you does.

Now walk through a typical “growth-optimized” flow with that reflex in mind, because it’s a minefield of freedom-threats. The onboarding tour you can’t skip. The modal with a hidden or grayed-out close button. The “you must upgrade now” wall with a countdown ticking. The newsletter popup that reappears the instant you dismiss it. The autoplay that decides for you. Each of these is engineered to force an action — and each one, by threatening the user’s sense of choice, spins up reactance that pushes against the exact behavior you’re trying to extract. The user doesn’t consciously think “my autonomy is threatened.” They just feel a flash of irritation, and that irritation attaches to your product and to the action you wanted. You didn’t increase conversion. You manufactured resistance and pointed it at yourself.

"this threatens my choice" invite · nudge force · coerce → reactance gentle heavy-handed how hard you push → chance they do it →
A nudge raises compliance; past the point where the user feels their choice threatened, more pressure drives the desired action down — often below where you started. Original diagram · Working Theory

The build moves are mostly about protecting the user’s felt autonomy while still guiding them. Offer, don’t force. “Want the quick tour?” with a clear no converts better over time than a tour that traps them, because the yes is theirs. Always leave a visible exit. A close button that’s easy to find is not a leak in your funnel; it’s the pressure-release valve that keeps reactance from firing — paradoxically, people are more likely to stay when they can clearly leave. Give a reason, not a command. “Verify your email so we can recover your account if you’re locked out” threatens choice far less than a bare “you must verify,” because an explained constraint reads as sensible rather than coercive. Preserve the sense of choosing. Even a small, real option — “start with A or B” — restores the feeling of control that a single forced path removes. And notice when you’re using reactance for the user’s goals instead of against them: a commitment device someone opts into (“lock me out of this app after 10pm”) works precisely because they chose the constraint, so it doesn’t threaten a freedom — they installed it.

The honest objection is that plenty of forcing clearly works — required fields, mandatory 2FA, hard paywalls that do convert. True, and the distinction matters: reactance is about felt freedom-threat, and a constraint that’s obviously necessary, clearly explained, and applied to everyone reads very differently from one that feels arbitrary or manipulative. There’s also real individual variation — some people are far more reactance-prone than others, and it varies across cultures — so this is a strong tendency, not a universal law. But the asymmetry is reliable enough to design around: the marginal push is much likelier to backfire than the marginal invitation.

So before you add pressure to a flow that isn’t converting, consider that the pressure itself may be the problem. The instinct, when people won’t do the thing, is to force them harder. Reactance says that past a point, every additional shove makes them want to do it less — and the move that actually works is the counterintuitive one: loosen your grip, hand back the sense of choice, and let them walk toward the thing instead of being dragged.

The science, to look up: psychological reactance theory (Jack Brehm, 1966; Brehm & Brehm, 1981); the 'forbidden fruit' / scarcity-as-threat findings; trait reactance and its individual and cultural variation. A robust effect whose strength varies by person and framing — it's triggered by threatened *felt* freedom, not by constraint as such.

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.