Jevons Demand-Rebound Test
Check whether efficiency expands total use instead of shrinking demand
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 96%
Steven Bartlett invokes Jevons paradox while discussing whether AI coding will eliminate programmers. He defines the basic mechanism as cheaper supply leading to more use, then argues that easier software creation may cause many kinds of organizations and workers to build more technology. The reusable test begins with the unit whose cost or effort falls, identifies customers and use cases newly made viable, estimates the resulting rebound in total demand, and then separates market-level growth from the fate of individual roles. That distinction matters: more software could be produced while some entry-level tasks still disappear. The model therefore challenges a simple efficiency-equals-less-demand assumption, but Bartlett's claim that coding demand is exploding is an observation in the episode rather than a complete labor-market analysis.
Origin
The host identifies the mechanism as Jevons paradox; extracted from The Diary of a CEO.
Core principles
- 01Lower unit cost can increase total consumption
- 02Automation can expand a market while changing its tasks
- 03Demand depends on new uses as well as old jobs removed
- 04A rebound is a hypothesis that needs measured adoption
- 05More output does not guarantee more employment in every role
How to run it
- 1
Define the efficiency gain
Specify what becomes cheaper, faster, easier, or more accessible. Measure the change per unit where evidence exists.
Pro tip Use the customer's full cost, including skill and waiting time.
Watch out A claimed efficiency gain should be tested in real use.
- 2
Find newly viable users
Identify people and organizations that could not justify the old cost. Estimate which of them can now adopt the product or activity.
Pro tip Look beyond the industry's current customers.
- 3
Find newly viable uses
List activities that were previously too expensive, slow, or specialized. Rank them by frequency and willingness to adopt.
Pro tip Ask what users would do ten times more often at one-tenth the friction.
Watch out Possible use cases are not realized demand.
- 4
Estimate the rebound
Combine lower use per unit with growth in users, frequency, and applications. Calculate whether total demand falls, stays level, or rises.
Pro tip Model weak, medium, and strong rebound cases.
Watch out The paradox is not a universal law that total use must rise.
- 5
Map role-level effects
Separate expansion of the overall market from displacement of particular tasks and career entry points. Identify the capabilities that become more or less valuable.
Pro tip Track tasks before aggregating them into jobs.
Watch out A growing market can still eliminate specific roles.
- 6
Measure and revise
Track adoption, total output, prices, and employment after the efficiency change. Replace the forecast with observed rebound data as it arrives.
Pro tip Choose an early indicator for each new user group and use case.
In the wild
Bartlett argues that easier coding may increase software demand because media companies, lawyers, and executive assistants can all create more technology. In the same discussion, he acknowledges that some entry-level white-collar roles are already under pressure.
→ The market for software may expand even while the composition of programming and analyst work changes.
A reporting tool cuts the cost of producing a weekly analysis by 90%. Existing customers generate more reports, and smaller teams begin using reports they previously could not afford, while manual data-cleaning tasks decline.
→ Total reporting volume rises even though labor per report falls.
Common mistakes
Assuming efficiency always cuts demand
Lower costs can unlock new users, greater frequency, and previously uneconomic applications.
Assuming rebound protects every job
Total market growth can coexist with displacement of particular tasks and entry routes.
Treating the paradox as certainty
The strength of any rebound must be measured in the specific market.
Is it for you?
Best for
It is best for market sizing and workforce planning when automation sharply lowers the cost of producing something.
Not ideal for
It is not ideal as proof that every efficiency gain creates jobs or that resource use must always rise.
From the transcript
“Jeb's paradox is the old analogy, cheaper, you use more of it.”
“When creating technology becomes easier, every company starts using more technology.”
From the episode
Financial Crash Expert: In 3 months We’ll Enter A Famine! If Iran Doesn’t Surrender It's The End!