If your leadership team is drowning in decisions that used to move fast and no one can quite say when the slowdown started, this piece is for you. The problem is not that people forgot how to move. The structure that made speed possible was designed for a different environment, and the environment changed.
There is a specific kind of organizational failure that only becomes visible when the environment changes faster than the structure can respond.
You have seen it. The company that was nimble at twenty people and calcified at two hundred. The product team that shipped weekly at Series A and now takes a quarter to release a minor feature. The executive who made every meaningful decision when the organization was small and now makes every meaningful decision in an organization that has outgrown that architecture, and wonders why things feel slow.
The structure didn’t fail. The structure worked exactly as designed. The problem is that it was designed for a different environment, and the environment changed, and nobody changed the structure.
In mountaineering, there is a term for this. The monument. It is the fixed camp, the established route, the permanent installation that made complete sense when it was built and now constrains movement precisely because of how solid it is. Monuments are not mistakes. They are past decisions that succeeded so thoroughly they became infrastructure. And infrastructure, by definition, is hard to move.
The question is never whether you have monuments. You always have monuments. The question is whether your team can navigate around them, or whether every path runs through them.
The centralization trap
Most organizations centralize power for a legitimate reason. Early-stage companies centralize because the founder’s judgment is genuinely the fastest and most reliable decision-making mechanism available. Scaling companies centralize because consistency matters and inconsistency at scale is expensive. Established organizations centralize because accountability requires a traceable chain and distributed authority makes auditing difficult.
Each of these reasons is real. None of them ages well.
The founder whose judgment was the fastest mechanism at twenty people is now a bottleneck at two hundred. Not because their judgment got worse. Because the volume of decisions outgrew the bandwidth of a single node. The consistency that centralization delivered at Series B is now the rigidity that prevents Series C from moving. The accountability chain that satisfied the board is now the reason a product decision that should take a day takes a month.
The monument was built for good reasons. The monument is now in the way.
What makes this particularly difficult to address is that the people who benefit most from centralized authority are usually the people with the most power to change it. Decentralization is a decision that costs the decision-maker something real. Visibility, control, the feeling of being indispensable. It is genuinely uncomfortable to push authority to the edge of the organization when the organization was built around your authority being at the center.
This is not a character flaw. It is a structural incentive problem. And it doesn’t resolve itself.
“Monuments are not mistakes. They are past decisions that succeeded so thoroughly they became infrastructure. And infrastructure, by definition, is hard to move.”
What the edge of the map teaches
Operating in remote field environments teaches a specific lesson about authority that is difficult to replicate in a centralized organizational culture. When the expedition leader is unavailable (weather, injury, radio failure, simple distance) the team has to move anyway.
This is not a design choice. It is a physical constraint. The Antarctic Peninsula does not pause operations while you wait for a decision from base camp. The weather window does not extend while the junior team member escalates to someone with more authority. Either the person on the ground has the judgment and the permission to act, or the moment passes and the decision gets made by the environment instead.
The organizations that perform under genuine pressure have almost always internalized this constraint deliberately, before the crisis forced it. They have pushed authority to the edge not because it was philosophically appealing but because they did the math. A decision made at 80% quality in thirty seconds by the person closest to the problem is almost always better than a decision made at 95% quality in three hours by someone further away from it.
This is not an argument for chaos. The field team on the Antarctic Peninsula operates within a framework. Protocols, decision trees, escalation triggers, hard stops that require authorization. The framework is tight. Within the framework, the authority is distributed. The monument defines the boundary. Inside the boundary, the team moves.
“A decision made at 80% quality in thirty seconds by the person closest to the problem is almost always better than a decision made at 95% quality in three hours by someone further away from it.”
The practical architecture
Pushing authority to the edge requires two things that most organizations treat as opposites but are actually prerequisites for each other. Extreme clarity about what requires central authorization, and extreme generosity about everything else.
The centralization trap usually isn’t that leaders refuse to delegate. It’s that the boundaries are unclear, so the default becomes escalation. When people don’t know whether a decision is theirs to make, they ask. When they ask often enough and get affirmed often enough, asking becomes the habit. The organization learns, rationally, that the safe move is to surface everything upward. And the leader who created that system by being unclear about boundaries is now drowning in decisions that were never supposed to reach them.
The fix is architectural, not behavioral. It is not “empower your team” as an aspiration. It is a written map of what requires your authorization and what doesn’t. Specific, testable, revisable as the organization grows. The monument, precisely defined. Everything outside it, the team’s terrain.
In practice, this means being more explicit about decision rights than feels necessary. It means accepting that some decisions made at the edge will be suboptimal, and treating that as the cost of building a system that can move without you, rather than as evidence that delegation doesn’t work. It means stepping to the back of the line deliberately, repeatedly, and visibly enough that the team stops waiting for you to move first.
The organizations that get this right don’t feel flat or chaotic. They feel fast. Decisions happen close to the information. Problems get solved before they escalate. The leader is making fewer decisions and better ones, because the only decisions reaching them are the ones that genuinely require them.
That is not a loss of authority. That is what authority looks like when it is working correctly.
THE TEAM TEST
Look at the last ten significant decisions in your organization. Not the ones that should have gone to you. The ones that actually did.
How many of them genuinely required your specific judgment? How many arrived at your desk because the person who should have made them wasn’t sure they were allowed to? How many times did someone escalate not because the decision was above their pay grade, but because the boundaries were unclear and escalation was the safe default?
If the answer is more than two or three, you don’t have a delegation problem. You have a map problem.
Draw the monument. Define its edges explicitly. Then step back and watch what happens when the team discovers they have had the terrain all along.
