The Easiness Ladder: Default, Then Rule of Thumb, Then Decision
First line of defence is always a default. If you can't default it, give people a heuristic — never a calculation.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 88%
A decision hierarchy for any behavior that requires repeated user effort. Rung one: remove the decision entirely with a default (automatic 401k enrollment is why Americans have retirement savings). Rung two, if the backend can't support a default: make it cognitively easier with a rule of thumb — a simple heuristic that replaces in-the-moment cost-benefit reasoning. Rung three, deliberate decision-making, is where features go to die.
Origin
Kristen Berman / Irrational Labs, offered as the alternative to budgeting features in personal finance. The defaults evidence comes from the automatic-enrollment 401k literature in behavioral economics (Thaler and Benartzi's work in the field Dan Ariely popularized). Berman links the rule-of-thumb rung to James Clear's identity-based habits when Lenny raises it.
Core principles
- 01The first line of defence in any problem is: how would you make it easier for someone to do?
- 02Logistical ease and cognitive ease are separate dials — a feature can be one tap and still be exhausting.
- 03A rule of thumb is a heuristic, not an optimum. It will be imperfect, and adherence beats precision.
- 04Behavior is not driven by attitudes, preferences or goals — it's driven by what you do. To change behavior you must change the environment.
How to run it
- 1
Try to default it
Ask whether the behavior can happen automatically without the user deciding at all. Automatic 401k enrollment defaults people into saving from their paycheck — that default, not financial education, is why retirement savings exist in America.
Watch out Defaults are hard for product teams: they usually require significant back-end infrastructure. Budget for that rather than retreating to a UI feature.
- 2
If you can't default it, design a rule of thumb
Replace the in-the-moment calculation with a standing heuristic. Instead of weighing 'is this Lyft worth three dollars to me?' every evening, the user adopts: 'I don't take Lyfts on weekdays, I take them on weekends.'
Pro tip Framing the rule as an identity ('I'm the kind of person who doesn't do X on weekdays') is the James Clear version and makes adherence easier.
Watch out Accept the heuristic will be suboptimal on any given decision. It wins on adherence across many decisions.
- 3
Redesign the environment, not the intention
Do not ship a feature whose theory of change is that the user will want it more. Goals and attitudes don't move behavior; changed environments do.
Watch out This is Berman's charge against the self-help industry: it tells you it's enough to have a goal. It isn't.
- 4
Be skeptical of any remaining user work
Whatever effort survives the ladder, prove it's worth the user's time — then measure whether they actually do it, rather than whether they say they will.
In the wild
Faced with a personal-finance client whose users demanded budgeting, Berman's alternative was not a better budgeting UI. It was to move up the ladder: default the saving where possible, and where not, replace budgeting's ongoing cognitive load (know your budget, know where you are in the month, plan, execute repeatedly) with a single standing rule.
→ The budgeting build produced zero change in spend or spend variability across 10,000 users. The ladder predicts that outcome before you build.
Common mistakes
Making it logistically easier but not cognitively easier
Teams cut taps and fields and call it done. If the user still has to weigh a decision every time, the load hasn't moved — a two-tap budgeting app is still a budgeting app.
Building for the goal instead of the environment
Assuming a motivated user will supply the effort. People want to be runners and don't run. Change what they do, not what they intend.
Is it for you?
Best for
PMs in personal finance, health, or any category where the desired behavior must repeat many times and willpower is the implicit dependency.
Not ideal for
One-off, high-stakes decisions (buying a house, choosing a surgeon) where deliberate reasoning is the point and heuristics would be reckless.
From the transcript
“kind of the first line of defense in any problem solving be how would you make it easier for somebody to do and so in…”
“so we call them rules of thumb like instead of having to decide in the moment do I do this thing and you're weighing the…”
“you'd actually make a rule of thumb that says do I do it or not so instead of deciding do you take a lift you…”
“enough you actually need to to redesign your environment to change your behavior”
From the episode
Using behavioral science to improve your product
Kristen Berman (Irrational Labs)