Definition
Complexity management is the discipline of designing systems that handle work whose volume or interaction richness has exceeded what any individual expert can hold. It is the wider practice of which Gawande's checklist is one tool. Other tools include cross-discipline communication protocols, redundancy (two pilots, two engines, four-eye reviews), explicit dispersal of decision authority, simulation training, and post-incident loops that feed structural fixes back into the procedure.
The recognition driving the discipline is the same one driving The Checklist Manifesto: in many modern fields, the unaided human mind is no longer the right unit of reliability.
Why it matters
How it works
The discipline moves through four steps. First, diagnose the problem class — is the failure mode a missed routine step (simple), a missing piece of integration between specialists (complex), or genuinely unknown territory (research)? Second, pick a tool fit to the class — a task checklist for simple, a communication checklist for complex, a research investment for the third. Third, design with the constraints of the actual operator in mind — working memory limits, attention budgets, social hierarchies that suppress speaking up. Fourth, build the loop that lets the system learn — incident investigation, root-cause analysis, structural fix, distribution, ongoing measurement.
Aviation has all four moves institutionalised. Medicine has fragments of each. Software has the first three for some teams and rarely the fourth. The visible difference between fields that handle complexity well and those that don't is rarely talent or budget; it is whether the four moves are practiced together as a discipline.