Occam’s Razor + Sunk Cost Fallacy + Systems Thinking
Every unnecessary feature in your product is a gravestone. It marks where you couldn’t admit you were wrong. Sunk cost fallacy turns past investments into future prisons. Most founders die defending corpses.
Core Insight
You’re not building features. You’re building monuments to mistakes.
You build a feature nobody wants. Sunk cost fallacy won’t let you delete it. So you add three more features to “fix” it. Now you’re maintaining four things nobody wants. The complexity isn’t in the feature, it’s in your head.
The paradox: The longer you defend the wrong complexity, the more complexity you create defending it.
Key Concepts
Occam’s Razor
Simplest wins. Not because simple is easy. Because every added part is another failure point. Complexity is expensive in speed, in clarity, in the cognitive load it puts on everyone who touches it.
Sunk Cost Fallacy
You already spent six months building it. So you can’t delete it. That would make the six months meaningless. Your brain would rather burn the next six months than admit the last six were wasted.
Systems Thinking
Some complexity is architecture. Some complexity is hoarding. Systems thinking is the ability to tell the difference. Architecture serves users. Hoarding serves your inability to let go.
Founder Applications
Example 1: Instagram’s Feature Bloat
Simple photo sharing in 2010. Then filters. Then Stories. Then Reels. Then Shopping. Then IG TV. Then Threads. Each addition created complexity layers. Users confused. Engagement drops. 85% defensive complexity.
Lesson: The feature you can’t delete becomes the reason you build ten more.
Example 2: Quibi’s Complexity Death Spiral
$1.75B raised. Horizontal AND vertical video. Custom CMS. Celebrity content. Mobile only. No TV casting. Proprietary tech. Complexity overload. Nobody understands it. Company dies in 6 months.
Lesson: The innovation you can’t kill is the one that kills you.
Example 3: Toyota’s Simplicity System
Problem detected. Five Whys analysis reveals root cause. Simplest fix? Implement. Measure. Works? Keep it. Fails? Remove it. Continuous improvement loop. Necessary complexity only.
Any worker can pull a cord and stop the entire assembly line. Sounds insane? Stop a $50 million/day operation because one person sees a problem? But that’s systems thinking. The complexity of fixing defects after production destroys more value than stopping production early.
Simple rule: stop the line. Complex outcome: highest quality cars in the world. They chose necessary complexity (empowering every worker) over emotional complexity (protecting management ego).
Lesson: The hardest complexity to add is the kind that admits you’re wrong.
Why It Works
Your brain runs on prediction engines. When reality breaks a prediction, you feel pain. Physical pain. Same brain regions as a broken bone. You predicted the feature would work. You told your team. You built roadmaps around it. You told yourself you’re smart. Then it flops.
Now your brain has two options: (1) Update the prediction (admit error, feel pain, move forward), or (2) Defend the prediction (add complexity to make reality match the story).
92% of founders choose option 2. Not because they’re dumb. Because pain avoidance is stronger than truth-seeking. So they add features. Each one is a patch over the original wound. Each patch creates new wounds that need new patches.
Occam’s Razor isn’t about simplicity. It’s about pain tolerance. Can you feel the wound of being wrong without covering it? Systems thinking asks a different question: “Does this complexity make the system work better, or does it make me feel better?” One grows value. One grows scar tissue.
The real ratio: 85% of product complexity exists to protect founder feelings, not solve user problems.
Master Visual: Complete System
The Death Spiral
- Mistake leads to sunk cost trap
- Multiple patches compound the problem
- Complexity explosion: maintaining unwanted features
- Occam’s Razor cuts through defensive complexity
Formula
C_total = C_necessary + C_defensive
85% Defensive (Ego) + 15% Necessary (Function) = Total Complexity
Today’s Reframe
Complexity is scar tissue from wounds you won’t feel.
Reflection Prompt
Which feature are you keeping alive because deleting it would mean admitting you were wrong?
