Behavioural Design
People do not behave rationally. Design for how they actually decide.
01 — TL;DR
Two sentences.
Behavioural Design is the application of behavioural economics and cognitive psychology to product decisions. It represents a foundational departure from the rational actor model: users will not do what is best for them simply because the correct action is available. They will do what is easiest, most salient, and least effortful — and Behavioural Design works by reshaping the choice environment to close the gap between intention and action.
The field draws on Daniel Kahneman and Amos Tversky's prospect theory, Richard Thaler and Cass Sunstein's nudge theory, and BJ Fogg's behaviour model. Together these establish a constraint and an opportunity: users will not behave as intended just because the correct action is present, but they will behave differently when the context around the choice changes. The most effective behavioural interventions feel invisible — they make the desired action the path of least resistance rather than the product of deliberation.
02 — When to Use
Apply this when…
When NOT to apply it
Skip it for high-stakes deliberate decisions where users need full information and reflection time — mortgage applications, medical consent, legal agreements. Skip it when the behaviour change serves the product rather than the user — that is persuasion architecture, not Behavioural Design. And be cautious in regulated contexts where nudging may conflict with informed consent requirements or fair treatment obligations.
03 — How It Works
The mechanism
Behavioural Design works by redesigning the choice context rather than the choice itself. Instead of informing users and hoping they act rationally, it changes what is easiest, most visible, and most immediate — shaping the environment so the desired behaviour becomes the path of least resistance.
Behavioural Design vs dark patterns
Behavioural Design and dark patterns use exactly the same techniques — defaults, friction manipulation, loss framing, social proof. The difference is ethical orientation, not method. Behavioural Design uses these tools to help users do what they already said they wanted to do. Dark patterns use them to make users do what the business wants against their own interests. Same toolkit, opposite direction. If you cannot articulate whose goal the intervention serves, you are probably building the wrong thing.
04 — Real Example
Nest thermostat — learning defaults and social norm framing
The traditional programmable thermostat is a textbook case of the intention-action gap. Users want to save energy and money — surveys consistently show this. But programming a thermostat requires deliberate System 2 effort: reading a manual, setting schedules, adjusting for weekends. The result: the majority of programmable thermostats are never actually programmed. The feature exists, the intention exists, the behaviour does not.
Nest solved this with Behavioural Design rather than better UI. Instead of making the programming interface easier, they eliminated it. The Nest thermostat observes what temperature users set manually over the first week, then auto-generates a schedule from that behaviour — learning defaults. Users do not need to programme anything; their existing behaviour becomes the programme. The Energy History screen then applies social norm framing ("You used 12% less energy than similar homes this month") and loss framing ("Turning up 2 degrees would cost you an extra $23 this month"). The combination of defaults, social norms, and loss framing closed the intention-action gap that decades of better thermostat interfaces had failed to address.
05 — In the Wild
Test yourself & see real examples
No examples yet — be the first.
Found a product that genuinely helps users do what they said they wanted to do? Or one that uses behavioural techniques against user goals? Submit what you found. Every approved example gets attributed to you.
Seen Behavioural Design applied well or misused? Help grow the evidence base.
06 — Common Mistakes
Where teams go wrong
07 — Variations & Related Principles
Connected ideas
Behavioural Design does not operate in isolation — it draws on and complements several related frameworks and strategies. The principles below either explain why specific behavioural tools work, shape how users experience interventions, or provide the testing infrastructure to validate which interventions actually close the gap.
The most important pairing is Behavioural Design with a clear definition of the user's own goal. Without knowing what the user is trying to achieve — in their terms, not yours — every behavioural intervention risks sliding from nudge into manipulation. Cognitive Load Theory explains the mechanism behind friction reduction: every unnecessary step imposes extraneous load that competes with the user's intention. Framing provides the theoretical basis for why loss framing outperforms gain framing in almost every behavioural context. And Lean UX provides the experimental infrastructure to test which specific intervention closes the gap for your specific population.
08 — 10-Min Exercise
Run it right now
⏱ 10 minutes · Team · No prep
Pick one behaviour your product is designed to support — one action users should take that they currently do not take often enough.
1. Estimate the intention-action gap: what percentage of users who express intent (sign up, start onboarding, add to cart, set a goal) actually complete the target behaviour? If you do not have data, use your best estimate — the number is almost always lower than the team believes.
2. For each of the six core tools — defaults, friction reduction, social norms, commitment devices, implementation intentions, loss framing — write one sentence describing how it could be applied to this specific behaviour gap. Not every tool will be relevant; skip any that do not fit.
3. For the two most promising interventions, write a testable hypothesis: "If we [specific change], we expect [specific behaviour metric] to increase by [estimated percentage] within [timeframe]."
4. Identify the smallest possible experiment you could run this sprint to test the stronger of the two hypotheses. What is the minimum change to the choice architecture that would generate measurable signal?