CONCEPT
Essential Complexity
Brooks's term for the complexity inherent in the problem — deciding what to build, understanding user needs, balancing requirements, ensuring correctness — which no tool can eliminate because it is not an artifact of the tools.
Essential complexity is the floor beneath which no abstraction can reach. It is the work of specification, design, testing, and judgment that must be done regardless of the implementation technology. Brooks argued in 1986 that because software's essential difficulty resides here, and because no conceivable tool could automate the making of decisions about what a system should be, no single technology would deliver order-of-magnitude improvements in software productivity. The prediction was partially wrong — AI has delivered those improvements — but the mechanism Brooks identified is intact. The improvements came from eliminating accidental complexity, not from reducing essential complexity. What remains after the collapse of accidental complexity is, structurally, what Brooks identified as essential all along.
In The You On AI Field Guide
Essential complexity has four components in Brooks's analysis: specification (what should the system do?), design (how should it do it?), testing (does it actually do what it should?), and maintenance (how does it evolve as