The Four Forces of Progress
Model demand as a tug-of-war: two forces push people to switch, two hold them back.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 95%
Instead of assuming more features create more demand, Four Forces frames a market as a system of behavior. A customer only switches when the forces pushing them toward change (the push of their situation plus the pull of a new outcome) outweigh the forces anchoring them in place (anxiety about the new and the habit of the present). It reveals that reducing friction often moves more people than improving the product.
Origin
Developed by Bob Moesta as the operational engine of Jobs to Be Done, co-created with Harvard's Clayton Christensen. Moesta describes it as his tactical 'method' complement to Christensen's 'theory' of JTBD.
Core principles
- 01People don't randomly do anything; a struggling moment causes demand, not the product.
- 02Demand requires energy: F1 (push of the situation) and F2 (pull of a new outcome) must exceed F3 (anxiety of the new) and F4 (habit of the present).
- 03Adding features can backfire because novelty itself generates anxiety (F3).
- 04You can grow sales without touching the product by removing friction that feeds F3 and F4.
- 05The push has nothing to do with your new product; without a push, customers literally can't see your product.
How to run it
- 1
Find the push (F1)
Identify the context or struggling moment that makes someone say 'today's the day I have to do something different.' This is the only reason they'd leave the old solution.
Pro tip Interview recent switchers and ask what in the world happened that made today the day.
Watch out No push means no movement, no matter how good your product is.
- 2
Define the pull (F2)
Articulate the new outcome or state the customer is being drawn toward. F1 and F2 together form the vector of progress.
- 3
Surface the anxiety of the new (F3)
Name what worries the customer about adopting something unfamiliar. Every time you show someone something new, you create anxiety.
Watch out Piling on features increases F3 rather than reducing it.
- 4
Surface the habit of the present (F4)
Identify what makes the current behavior sticky. People are creatures of habit and must be helped to leave the old thing.
- 5
Reduce friction instead of adding pull
Attack F3 and F4 directly. Often you don't need to change the product at all, just make the switch easier.
Pro tip Bundle away the specific frictional point even if it raises your price.
In the wild
Moesta sold downsizers a condo but they'd cancel six weeks later because they couldn't figure out how to get rid of their stuff (a frictional point / F4). He raised the condo price and included moving plus two years of storage in the deal.
→ Sales increased over 30% without changing the product itself.
Common mistakes
Believing more features win
Most people assume adding pull (features) makes people buy. It's not true; more features actually create anxiety, so the switch stalls.
Ignoring the two restraining forces
Teams obsess over push and pull but never address anxiety and habit, so customers who clearly want to switch never do.
Is it for you?
Best for
Product and growth leaders diagnosing why a clearly-better product isn't converting the customers who say they want it.
Not ideal for
Categories with no real choice (e.g. employer-provided health insurance) or deeply habitual low-consideration purchases where the switch story can't be recovered.
From the transcript
“as soon as I have a push I call that F1 Force One right and I have some idea of what's possible then I create…”
“every time I show somebody something new it actually creates anxiety right anxiety of the new yeah and I call this F3”
“if F1 and F2 are not greater than F3 and F4 they're not going to move they're not going to do anything”
“if I reduce friction which is the bottom part I actually don't have to do do anything with a product I just have to make…”
“I increase sales over 30% I love that”
From the episode
The ultimate guide to JTBD
Bob Moesta (co-creator of the framework)