Second-System Effect
Updated 2026-08-13
INTRODUCTION
English translation pending.
CORE DEFINITION
Identified by Fred Brooks in The Mythical Man-Month, the second-system effect is the tendency for a designer's second system to become bloated and over-engineered because it accumulates every feature and refinement the first system had to leave out. The first system is usually disciplined by inexperience and caution, while the second is built by a designer who now feels confident and wants to correct every past compromise at once. The key qualification is that this is a tendency of the designer rather than of the technology, and the danger grows with the designer's sense of mastery.
SCAFFOLDING EFFECT
Reduce cognitive load
- Feature budget: set a hard cap on scope before designing version two. - Omission review: list what was cut from version one and test whether each item is truly needed. - Complexity tax: estimate the maintenance cost of every added feature before accepting it.
Anchor fast decisions
The first system is built under real constraints, so its design stays disciplined. Success then raises the designer's confidence, and the backlog of deferred ideas becomes an attractive to-do list. Each addition looks reasonable in isolation, but the costs compound, so the result is harder to learn, test, and change than either the first version or a leaner alternative.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Second-system_effectverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS