Users don't always behave the way they say they will
Users say they want simplicity.
Then they choose the more complicated option.
They say privacy matters.
Then they click "Accept All."
They say they'll use a feature.
Then they never return to it.
This isn't irrational.
It's human behavior.
The gap between what people intend to do and what they actually do is one of the most important ideas in Behavior Design.
The intention–behavior gap
Daniel Kahneman's Thinking, Fast and Slow describes two modes of thinking:
System 1
Fast, automatic, intuitive.
System 2
Slow, deliberate, analytical.
Many digital interactions happen under System 1 conditions.
Users are:
scanning
multitasking
rushing
relying on familiar patterns
trying to minimize effort
So what someone says they want to do in an interview may be very different from what they actually do inside a product.
That's why observed behavior is often more useful than stated preference.
Friction can beat motivation
Product teams often try to change behavior by increasing motivation.
Better messaging.
More benefits.
Stronger calls to action.
But BJ Fogg's Behavior Model highlights three factors:
Motivation + Ability + Prompt
If an action is difficult, motivation alone may not be enough.
A user might genuinely want to complete a task but abandon it because it requires:
too many steps
too much information
too many decisions
unclear instructions
Sometimes the best behavioral intervention isn't better persuasion.
It's less friction.
Defaults shape decisions
Defaults are powerful because they remove the need to decide.
Users often accept:
preselected options
recommended settings
default payment methods
suggested plans
This is known as the default effect.
Richard Thaler and Cass Sunstein explore the influence of defaults and choice architecture in Nudge.
The important design question is not simply:
"What should the default be?"
It's:
"What default best supports the user's interests?"
Defaults are powerful precisely because users often don't change them.
Context changes behavior
Behavior doesn't happen in a vacuum.
The same user can behave differently depending on:
time pressure
device
environment
distractions
emotional state
task complexity
Someone may intend to carefully compare five plans.
On a phone, while rushing between meetings, they may choose the first acceptable option.
This is why designing for an imaginary "average user" can be misleading.
Design for the moment of interaction.
Design for what users actually do
Instead of asking only:
"What do users want?"
Ask:
"What are users likely to do in this context?"
Then design accordingly.
That can mean:
reducing unnecessary steps
simplifying choices
making important actions obvious
using meaningful defaults
surfacing relevant information at the right moment
preventing predictable errors
This doesn't mean designing around the assumption that users are irrational.
It means designing around how humans actually behave.
Influence comes with responsibility
Behavior Design gives product teams significant influence.
It can help users:
make decisions
complete tasks
build useful habits
avoid mistakes
But the same techniques can also create manipulation.
A useful ethical boundary is:
Does the design help users achieve their goals, or mainly help the business get what it wants?
Good choice architecture should preserve:
autonomy
transparency
meaningful choice
user control
The goal is better decisions, not coerced decisions.
Takeaway
Users don't behave according to intention alone.
Their behavior is shaped by:
context → friction → defaults → cognitive shortcuts
That's why effective Behavior Design starts with observing what people actually do, not only what they say they'll do.
If you design only for stated preferences, you may build what users describe wanting.
If you design for real behavior, you can build experiences that work in the real world.
