Second-system syndrome—also called the second-system effect—is the risk that a successor to a small, successful system becomes over-designed. After the first system succeeds, its architect may try to add ideas and features set aside during the original design. Fred Brooks described this as a tendency, not a rule that every second system fails.
What does second-system syndrome mean?
The term refers to a particular design transition: building a successor after a relatively small, elegant system has succeeded. It is not simply another name for any second release or for feature creep in general. The Jargon File uses “second-system syndrome” as an alternate name for the second-system effect and describes the risk in the successor to a successful system. The Jargon File’s definition provides that terminology.
As an Amazon Associate I earn from qualifying purchases.
In chapter 5 of The Mythical Man-Month, “The Second-System Effect,” software engineer Frederick P. Brooks Jr. explains the mechanism: a first design is often restrained while its architect is learning, but ideas deferred from that work accumulate. After the first system succeeds, confidence can make the architect more willing to add those embellishments to its successor. Brooks’s warning is captured in his line, “This second is the most dangerous system a man ever designs.” Brooks’s chapter presents the idea as a design risk, not a universal law.
How can the effect appear?
Too many features or generalizations
A successor can become overbuilt when deferred features and “frills” are added without enough regard for whether they serve the new system’s objectives. The problem is not ambition by itself; it is allowing accumulated ideas to outweigh demonstrated needs, implementation cost, and the system’s purpose.
#1 Best Overall
Refining techniques built on obsolete assumptions
Brooks also describes a related form of over-investment: continuing to refine techniques whose purpose has been made obsolete by a change in basic assumptions. This is different from adding new features. The design risk is carrying forward and polishing an approach that no longer fits the system being built.
What examples did Brooks use?
Brooks used the IBM 704 and its successor architecture, the IBM 709, later embodied in the 7090, as a historical illustration. He wrote that the 709’s operation set was so rich that only about half of it was regularly used. He called the Stretch computer a stronger example of the effect. These are Brooks’s illustrations in his chapter, not a modern empirical study or proof that ambitious successors inevitably fail. Read Brooks’s account in chapter 5.
How can a team apply Brooks’s warning?
Brooks’s central discipline is “thoroughgoing, careful, and sympathetic communication between architect and builder.” In practice, a team considering a successor or redesign can use that advice to frame a discussion—not as a validated scoring test, but as a way to make trade-offs explicit:
- Which proposed features address demonstrated needs, and which are additions carried over from ideas deferred in the first system?
- What complexity and implementation cost does each addition bring, and do the estimates fit the available budget?
- Have the system’s basic assumptions changed enough that inherited techniques should be retired rather than refined?
- Have architects and implementers compared alternatives against agreed objectives, including implementations that meet those objectives in a different way?
This approach keeps design choices tied to objectives and budget while allowing implementation experience to inform architecture—both themes in Brooks’s discussion. His chapter explains the communication and budgeting advice.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Where can you read Brooks’s full discussion?
The concept appears in chapter 5, “The Second-System Effect,” of Frederick P. Brooks Jr.’s The Mythical Man-Month: Essays on Software Engineering. The publisher page describes the 1995 anniversary edition, published by Addison-Wesley Professional, ISBN 0201835959. See the publisher’s edition information.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
