10x Forcing Function
Demand a tenfold improvement to force a redesign instead of more grinding
- Difficulty
- Advanced
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 98%
The 10x Forcing Function reframes an improvement problem so that simply grinding harder is mathematically or physically insufficient. First define the result and imagine it operating at ten times the current level. Then test whether the existing method can scale: a business obtaining customers through local meetups cannot attend ten times as many without running out of time. That constraint forces different questions about people, channels, automation, or an entirely rebuilt process. The power of the model is not a promise that every result will become ten times larger. It is the requirement to leave the current groove and design from the ground up when incremental effort cannot meet the target. Risk still matters; the new design should not expose the whole system to a multiply-by-zero outcome.
Origin
Pearson uses power-law framing as a counterweight to his own tendency to grind toward five-percent improvements instead of reconsidering the system.
Core principles
- 01A tenfold target cannot usually be reached by doing ten times more
- 02Extreme targets expose the limits of the current method
- 03A forcing function makes alternative system designs necessary
- 04Incremental improvement and reinvention serve different situations
How to run it
- 1
Define the target result
Choose one measurable outcome that matters. State what ten times better or larger would mean in that context.
Pro tip Use an outcome rather than an activity count.
Watch out A vague 10x ambition cannot force a concrete redesign.
- 2
Break the current method
Try to scale the current approach on paper and identify the resource that makes tenfold execution impossible. Time, attention, or local reach will often reveal the ceiling.
Pro tip Make the bottleneck explicit before proposing alternatives.
Watch out Do not assume working harder removes a structural constraint.
- 3
Generate different systems
Consider new channels, delegation, automation, or a ground-up redesign that changes the limiting relationship. Require each option to explain its leverage.
Pro tip Ask what must become structurally different, not merely faster.
Watch out A bigger version of the same process may still carry the same ceiling.
- 4
Test without multiplying by zero
Run a bounded test of the redesigned mechanism and compare it with the desired outcome. Preserve survival by limiting catastrophic downside.
Pro tip Use a small experiment to validate leverage before replacing the whole system.
Watch out A spectacular possible upside does not justify a ruinous failure mode.
In the wild
A business wins customers by attending local meetups. Because one person cannot attend ten times as many, the 10x question forces consideration of other people, other channels, or a different acquisition system rather than a busier calendar.
→ The growth discussion shifts from more effort to a scalable mechanism.
Common mistakes
Multiplying the same activity
Trying to perform a time-bound activity ten times more often avoids the redesign the question is meant to force.
Ignoring catastrophic downside
A radical option is not useful if one failure can destroy the entire system.
Is it for you?
Best for
It is best for constrained systems where more effort cannot scale the existing acquisition, production, or delivery method.
Not ideal for
It is not ideal when steady incremental improvement is sufficient or a radical experiment introduces ruinous downside.
From the transcript
“what would it look like if this was like 10 times better”
“you can't go to ten times as many meetups right like it just won't there's there's no way just doing more”
“usually that means kind of reinventing the thing from the ground up”
From the episode
Discover Your Life’s Core Values & Operating Principles - Taylor Pearson - #199
Taylor Pearson