Behavioral Science for Product Teams: Why Users Don't Do What They Intend

Why does the rational-user model keep failing product teams?

Because it smuggles a false assumption into every design review: that users will read, compare, and decide carefully. Herbert Simon called the reality bounded rationality — people decide with limited time, limited information, and limited attention, and they satisfice: they take the first acceptable option, not the optimal one.

Watch a real usability session and you’ll see it constantly. Users don’t evaluate your pricing page; they scan it and anchor on the first number. They don’t read your onboarding copy; they pattern-match for the button that looks like progress. Nobody is being lazy. This is what a fast, efficient brain does — and it’s the brain every interface is designing for, whether the designer admits it or not.

What are System 1 and System 2, and why should designers care?

Kahneman’s framework divides thinking into two modes. System 2 is slow, deliberate, effortful — the mode users are in when they’re comparing enterprise plans. System 1 is fast, automatic, and cued by the environment — the mode they’re in for almost everything else.

The design consequence is blunt: most of your interface is experienced by System 1. That means cues, defaults, and layout do the steering, not arguments. A user doesn’t decide to follow the big primary button; the button’s prominence is the decision, made before deliberation starts. This is why tiny contextual changes — a label, a default, the order of options — routinely outperform entire persuasion campaigns. You’re not persuading the pilot. You’re designing the cockpit, and the cockpit flies the plane.

What is the COM-B model, and how do you use it on a real flow?

COM-B says a behavior happens only when three things are present: Capability (can they do it?), Opportunity (does the context allow it?), and Motivation (do they want to?). Remove any one and the behavior stops — no cue, no habit; no bike lane, no amount of motivation produces cycling.

Run it on any failing flow and the diagnosis sharpens immediately. Users not completing KYC? Capability: is the document step confusing? Opportunity: are they on a bus on a phone with no document in reach? Motivation: does the reward for finishing arrive too late to matter? Most teams instinctively reach for motivation — more copy, more incentives, more push notifications. COM-B tells you to check capability and opportunity first, because shrinking a step or moving it to a better moment is cheaper and usually the actual fix.

The behavior loop matters too: action, feedback, learning. Behaviors that get clear, immediate feedback repeat; behaviors that get silence disappear. It’s why habits form, why incentives work, and why your empty success screen is quietly training users to disengage.

Where does this leave your roadmap?

Three habits to steal from the field:

1. Diagnose drop-off with COM-B before rewriting copy. Most “messaging problems” are capability or opportunity problems in disguise.

2. Design for System 1 first. Make the right action the obvious, automatic one; reserve System 2 demands for decisions that genuinely deserve them.

3. Audit the context, not the user. When behavior fails, the question is never “what’s wrong with these users” — it’s “what in this context is beating their intention.”

Once you see products this way, you can’t unsee it. Every screen is a choice environment. The next article in this series covers the tools for designing that environment deliberately: nudges, defaults, and choice architecture.

Applying behavioral science to real funnels — diagnosing why users drop and fixing the context, not the copy — is core to our UX strategy work.