The Zone of Benefit (3x Rule)
A product must make the customer at least 3x better before they notice enough to switch and pay.
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 90%
A threshold model for how much better than the status quo a product must be before customers actually care. A 20% improvement goes unnoticed by humans; only a 2-3x improvement — either compressing the workflow or inflating capability (same time, far more output) — crosses the 'zone of benefit' where people notice, feel it, and part with money. It doubles as an ICP-finder because the customers who feel the 3x most acutely are your least price-sensitive true fans.
Origin
Articulated by Oji Udezue, drawing on behavioral economics (people work for leisure and work just enough to afford it) and his framing of product management as 'impedance-matching technology to humans.'
Core principles
- 01People won't pay for anything that doesn't visibly shrink their workflow or give them a superpower
- 02A 20% improvement is invisible to humans; the effect must be noticeable
- 03The threshold is roughly 2-3x — three times faster, or three times the output for the same effort
- 04Your best customers aren't price-sensitive because they fundamentally get the value
- 05The people who feel the 3x most acutely reveal your true ICP
How to run it
- 1
Measure the current workflow
Draw or quantify the customer's existing workflow — the time, steps, or output involved in doing the job the status-quo way.
- 2
Measure the workflow after your product
Draw the same workflow after the customer uses your software and compare the two as horizontal lines to see how much shorter it becomes.
Pro tip Measure the lines literally — is it 2x shorter? 3x shorter? That number is your signal.
- 3
Check it clears the 3x bar
Confirm the improvement is roughly 3x in speed or output. Below that threshold, humans won't notice and won't overcome switching costs.
Watch out A merely-better product (20-50%) will fail to trigger switching even if it is genuinely superior — 'good enough, whatever.'
- 4
Use the zone to find your ICP
As you cross ~100 users, watch for the people who say 'I really care about this.' Those who feel the 3x most keenly, and are least price-sensitive, are your true target audience.
Pro tip Post-launch, interview your most enthusiastic users and derive their workflow change to confirm where the 3x is landing.
In the wild
Udezue notes that when you make something 20% better, people around you — just as humans — simply don't notice. For a product to register, it has to deliver at least 2-3x so the user consciously says 'this is offering enough value for me to make a switching cost.'
→ Establishes the practical floor below which product improvements don't convert to adoption or revenue.
Common mistakes
Shipping a marginally-better product and expecting adoption
Founders build something 20-50% better than the status quo and are baffled when customers shrug. Below the ~3x threshold the improvement is imperceptible and doesn't justify switching costs.
Chasing price-sensitive customers for a 3x product
Your best customers aren't price-sensitive because they fundamentally understand the value. Optimizing for the people who haggle means you're not talking to the ICP who actually feels the zone of benefit.
Is it for you?
Best for
Founders and product leaders validating whether a new product or feature is differentiated enough to win, and pinning down who feels that value most.
Not ideal for
Regulated or compliance-driven purchases where switching is mandated rather than chosen, or infrastructure sold on cost rather than felt productivity gains.
From the transcript
“if you do something 20 better often people just around you just as a human people don't notice”
“it has to be at least two three more X for people to say you know what this is offering enough value for me to…”
“your best customers aren't price sensitive for what you're shooting for because they get it right”
“draw the current approximate average workflow for your Target customer at least what you think is a target and then draw the workflow after they've…”
From the episode
Picking sharp problems, increasing virality, and unique product frameworks
Oji Udezue (Typeform, Twitter, Calendly, Atlassian)