Why do small changes at key points beat big changes elsewhere?
"Give me a lever long enough and a fulcrum on which to place it, and I shall move the world." - Archimedes. A thermostat dial: tiny movement, entire building changes temperature. The key is finding WHERE to push, not pushing harder!
Should you invest time searching for the perfect lever point?
🤔 Which thinking lens(es) did you use?
Select all the lenses you used:
🌱 A Small Everyday Story
Three machines in a factory.
One makes 100 per hour.
One makes 50. One makes 200.
They doubled the fast machine's speed.
Output stayed at 50.
The slow machine was the lever.
See more guidance →
🧠 Thinking habits this builds:
- Understanding that systems have constraints that limit overall output
- Learning to find bottlenecks before investing effort
- Recognizing when brute force wastes resources
- Appreciating that smart > hard
🌿 Behaviors you may notice (and reinforce):
- "What's the bottleneck here?" questions
- Resisting the urge to "just do more"
- Looking for small changes with outsized effects
- Understanding why some improvements don't help
How to reinforce: When they propose a solution, ask: Is this addressing the constraint? What happens if we improve something that isn't the bottleneck?
🔄 When ideas are still forming:
Some learners may think all improvements help equally. Others may default to "work harder" instead of "work smarter."
Helpful response: "If you're stuck in traffic, does it help if your car can go faster?" Help them see that the constraint (traffic) limits the benefit of non-constraint improvements.
🔬 If you want to go deeper:
- Research Eliyahu Goldratt's Theory of Constraints
- Identify bottlenecks in familiar systems (homework pipeline, morning routine)
- Discuss why companies often optimize the wrong things
Key concepts (for adults): Theory of Constraints, bottleneck, leverage, Archimedes, constraint exploitation, system optimization, brute force fallacy.