2026 — Team stability was assumed without attrition modeling
The decision failed because a temporary team composition was treated as permanent.
No attrition scenario was modeled.
Failure Type: → Assumption Failure
Crux: → Permanence Illusion
Case
A startup committed to an 18-month product roadmap assuming its current engineering team would remain intact throughout.
Decision Error
Team stability was assumed without validation.
Why It Failed
The condition was temporary but treated as permanent.
Trigger
Short-term team performance was extrapolated.
Missed Signal
No attrition or key-person dependency scenario was analyzed.
Rule
If stability is assumed, test for change before committing.
Compare / Similar Failures
Often confused with:
→ Contradictory signals were ignored
Key Difference:
Confirmation Bias Lock results from dismissing visible retention risk signals, while Permanence Illusion results from never modeling team attrition as a possibility.
Boundary:
If attrition signals were present and rationalized away → Confirmation Bias Lock.
If no attrition scenario was ever modeled → Permanence Illusion.
Related Cases
→ CAC was assumed stable without channel degradation modeling
This case belongs to: