Organizational Inertia

In the AI Story

Inertia operates through the scar tissue of every rule, process, and habit that was created to cope with a limitation. When the limitation is removed — by technology, regulation, or structural change — the scar tissue remains. Team structures persist because they once distributed coordination load, even after the coordination they distributed has been automated away. Sprint cadences persist because they once provided synchronization points, even after synchronization has become unnecessary. Specification processes persist because they once compressed intention into forms engineers could act on, even after the language interface has made compression obsolete. Each practice was rational under the old limitation. Each is now, to varying degrees, inertia.

The danger of inertia is that it is locally defensible. A manager continuing to run two-week sprints can cite every benefit the practice provided: predictable cadence, regular synchronization, team alignment, stakeholder updates. The benefits were real — under the coordination constraint. The manager cannot easily see that the benefits were artifacts of the constraint, and that removing the constraint has removed the need for the practices that addressed it. The sprint feels disciplined. The sprint is inertia.

Goldratt's prescription is the fifth Focusing Step: if the constraint has moved, return to Step One. This injunction is the hardest of the five because it requires admitting that practices that succeeded are now obsolete. The organization that built its culture around sprint discipline will resist the admission that sprint discipline has become inertia. The engineering leader whose identity is bound up with Scrum mastery will resist the recognition that Scrum was the right answer to the wrong constraint. The inertia is not just organizational; it is personal, professional, cultural.

Segal's account in The Orange Pill of the discourse splitting into Upstream Swimmers and Believers is an inertia phenomenon. Each camp is defending a version of the old rules: the Swimmers defending the craft practices that arose under the coordination constraint, the Believers defending the optimization metrics that arose under the same constraint. Neither is engaging with the fact that the constraint has moved and that both sets of practices are now inertia in different directions. The Goldratt simulation's intervention is to ask the question neither camp is asking: where is the constraint now, and what practices are adequate to managing it? The question requires releasing attachment to old rules that once worked — the hardest organizational move there is.

Origin

Goldratt's treatment of inertia developed across his career but received its most explicit articulation in Necessary But Not Sufficient (2000). The novel's ERP implementation case dramatizes an organization crippled by inertia even after adopting powerful new technology — the technology was necessary but not sufficient precisely because inertia prevented the old rules from changing.

Key Ideas

Old rules are scar tissue. Practices designed to address removed limitations persist and become the new constraint if not deliberately retired.

Inertia disguises itself as discipline. The organization committed to practices that once worked experiences its persistence as strategic consistency rather than blindness.

The fifth Focusing Step addresses inertia. When the constraint moves, return to Step One. The injunction is methodological but also psychological: it requires releasing attachment to successful practices.

The AI transition is producing inertia at civilizational scale. Engineering hiring, sprint cadences, velocity metrics, specification processes — all rational under the coordination constraint — persist unexamined.

Inertia is personal as well as organizational. Professionals whose identities are bound up with old practices resist the recognition that the practices have become obsolete.