CompanyGraph
Organizations accumulate routines and systems. The important question is whether they can remove what no longer serves the work before the burden becomes a competitive constraint.
Entropy is a metaphor; inertia has a literature
“Organizational entropy” is useful shorthand for accumulated complexity, but it is not a thermodynamic measurement. The established research term is often structural inertia: the tendency of structures, routines, and accountability arrangements to persist even as the environment changes. Hannan and Freeman's 1984 paper developed that idea in organizational ecology, where reliability and accountability can make change difficult.
Persistence is not automatically waste. A hospital procedure, aircraft maintenance record, or financial-control process may be slow to change because reliability and safety matter. The question is whether the cost of persistence still buys the function it was created to protect.
What accumulates
Process burden grows when approvals, reconciliations, reporting, and handoffs are added to solve real problems but are rarely removed. Technology burden grows when old systems must be kept running alongside new ones. Relationship burden grows when customers, suppliers, employees, or regulators depend on arrangements that make a change costly. Each item may be defensible; together they can slow a decision, hide ownership, and consume people who could be serving customers.
Metrics can add another layer. A target that once approximated the business goal may survive after the goal changes. Teams then optimize the recorded measure while the underlying service, quality, or cash result deteriorates. This is a measurement problem, not proof that employees are irrational.
Tenure has two opposing effects
Long-tenured leaders and employees carry tacit knowledge about customers, equipment, contracts, failure modes, and past experiments. Replacing them can destroy information that is not written down. Continuity can also sustain trust and let a team compound learning.
The same continuity can make a mental model harder to revise. A leader who built a successful channel may defend it after customers move online. A team that knows an old system deeply may underestimate the cost of leaving it. Tenure is therefore an interaction with environmental change, not a direct cause of decline. The appropriate comparison is between the organization's learning rate and the rate at which its market, technology, regulation, or customer needs change.
A case where routines became a risk
A historical study of Moody's describes “dynamic inertia” in the credit-rating routine before the 2008 financial crisis: practices that had been reliable in one environment became difficult to revise as conditions changed. The study is a case analysis, not evidence that every long-tenured organization will fail. It shows the mechanism more clearly than a tenure statistic: a routine can remain internally coherent while its external fit deteriorates.
Corporate restructuring reports show the cost of renewal. In a recent filing, Arrow Electronics described a multi-year operating-expense plan involving personnel cash costs, non-cash impairments, and a redesign of operations. Those figures establish that simplification has a real transition cost; they do not establish that the projected savings will be achieved or that every legacy activity was wasteful.
How to tell renewal from reorganization theatre
A new org chart can add entropy rather than remove it. Renewal should change an observable constraint: fewer handoffs, faster release, lower defect or service cost, clearer accountability, shorter cycle time, or a product and process that better fit current customers. A restructuring charge or headcount reduction records an action, not its long-run effect.
Reforms also need money and authority. Decommissioning a system may require parallel operation, data migration, training, severance, and regulatory approval. Closing a site may release cash but destroy local expertise or customer access. The cheapest immediate action is not automatically the one that restores capability.
What to measure
- Decision and cycle time. Are approvals, releases, repairs, or customer responses taking longer for the same work?
- Work and handoffs. How many layers, reconciliations, and duplicate systems sit between an observation and a corrective decision?
- External fit. Are product mix, service levels, retention, defects, and pricing aligned with what customers now require?
- Learning. Does the organization conduct post-mortems, retire failed metrics, and change routines when evidence contradicts them?
- Continuity risk. Which capabilities leave with a leader, and which are documented, taught, and owned by a resilient team?
- Renewal economics. What cash, downtime, authority, and transition risk are required to remove the old arrangement?
The useful conclusion is conditional. Tenure creates an asset when it preserves knowledge while allowing assumptions and routines to change. It becomes a liability when the organization can no longer distinguish a control that protects the work from a habit that protects itself.