Most organizations are not designed. They accumulate.
A reporting line gets added to solve a coordination problem in 2019. A committee gets stood up to manage a crisis in 2021. A second approval layer gets inserted after a bad quarter. None of it is wrong on the day it happens. Each decision solves the problem in front of it.
Five years later, the operating model is the sum of those decisions — and no one can quite explain why a routine pricing change takes eleven weeks to move through the system.
This is the part most operators already know. The part that gets less attention is what the system actually optimizes for once design stops being deliberate.
The drift has a direction
When an organization isn't being intentionally shaped, it doesn't drift toward high performance. It drifts toward safety.
Not psychological safety. Self-protection.
The accumulated layers, approvals, sign-offs, and review gates aren't there to make better decisions. They're there to make sure no single person owns a bad one. Every layer is a place where risk gets diffused, ownership gets shared, and the cost of being wrong gets distributed across enough people that no one carries it.
That is a rational individual response inside an irrational system. People aren't being timid. They're reading the environment correctly. The environment rewards not-losing more than it rewards winning.
So the system slowly hardens around the avoidance of visible failure. And visible failure, for most operators, means a decision that can be traced back to one name on one document.
The result is an organization that looks busy, looks compliant, and quietly stops moving.
Why this is hard to see from the top
A COO looking at this from the executive floor sees activity. Meetings are happening. Decks are being built. Initiatives are tracked. Status is reported. The metrics that matter are still inside their bands — for now.
What's harder to see is the substitution underneath.
Real decisions are being replaced by decision rituals. Real ownership is being replaced by distributed accountability — which, in operational terms, is the same as no accountability. Risk-taking is being replaced by risk-staging: long pre-read cycles, alignment meetings, pre-meetings before the alignment meetings.
None of this shows up as a problem. It shows up as a slowdown. And slowdowns rarely get diagnosed at the structural level. They get explained away as "this quarter was complicated" or "we're between cycles" or "the team needed time to socialize the change."
By the time the slowdown becomes a number on a dashboard, the structure that produced it has been in place for two or three years.
Designing against the default
Designing an organization by intent doesn't mean designing for speed. It means designing against the natural pull toward safety.
A few things this looks like in practice:
- Naming where the decision actually lives. Not the committee that reviews it. Not the forum where it gets discussed. The person who owns the call and the consequence. If you cannot point to that person on an org chart in under thirty seconds, the design is doing the avoidance for you.
- Counting the layers between intent and execution. Every layer is a place where information gets compressed, softened, or reinterpreted. The number of layers a decision has to survive is a structural property of the organization, not a cultural one. It can be measured. It can be reduced.
- Watching what gets escalated and what gets absorbed. Healthy systems escalate the things that need a wider view and absorb the things that don't. Drifting systems do the opposite — they escalate routine matters because no one wants to own them, and they absorb the structural problems because no one wants to surface them.
- Treating ambiguity as a design failure, not a leadership trait.** Ambiguity at the top can look like flexibility. Three layers down, it's a vacuum that gets filled by whoever is most risk-averse in the room.
The cost of leaving it alone
The cost of an unintentionally designed organization rarely shows up where it was created. It shows up as missed timelines, talent attrition in the second tier of management, stalled cross-functional initiatives, and a slow erosion of decision velocity that becomes visible only in retrospect.
By the time it appears in your metrics, the structural choice that produced it is years old.
That is the real argument for design by intent. Not that intentional organizations are faster, though they usually are. Not that they're flatter, though they often are. The argument is that the alternative isn't neutrality.
The alternative is a system that quietly optimizes for the wrong thing, and gets very good at it.
If this resonates, the weekly brief covers recurring patterns like this one — operational signals that show up before they reach the dashboard.