If your organization has reorganized around the same tension three times in the last two years, this piece is for you. You are not making bad calls. You are treating a polarity as if it were a problem, and the two require completely different responses.
Map your team’s route through an active crevasse field. You cannot “solve” a crevasse field. You navigate the tension between speed, to minimize time in the danger zone, and caution, to avoid stepping into the void. Every step is a re-decision.
Most leaders treat ongoing organizational tensions (centralized control versus team autonomy, speed versus safety, specialization versus generalization) as problems to be definitively solved. They pick a side. They declare a winner. In high-stakes environments, that reflex is the exact source of the next crisis. When you treat an interdependent tension as a binary choice, you force the pendulum to swing violently, and the team lives with the extreme downsides of whichever side you chose.
The tell: problem vs. polarity
THE TEAM TEST
What is the specific “problem” your team has successfully “solved” three different times in the last two years, only to watch the organization violently swing back in the exact opposite direction?
Demonstration
The Velocity of Overshoot
A team in deep centralization. Set the speed of the corrective swing toward team autonomy. Then release the pendulum.
Ready
The team sits in deep centralization — past the warning band, into the danger zone. The corrective swing has not yet begun.
If a specific tension surfaced in your mind, and it almost certainly did, you are not looking at a problem that keeps recurring. You are looking at a polarity that keeps getting misdiagnosed as a problem.
The distinction is load-bearing. A problem has a solution. A polarity has two poles, each with genuine upsides and genuine downsides, and the only way to manage it is to navigate the tension between them continuously. The moment you declare the problem solved, you have stopped navigating. You have pitched a tent on the ice and gone to sleep.
The math of the pendulum
Drag the figure across the plateau. Notice what happens at the extremes. Notice what the velocity slider does to the severity of the crash when you overcorrect.
The crevasses aren’t on one side. They are on both sides. And the faster you swing from one extreme to the other, which is exactly what happens when you treat a polarity as a problem to solve, the deeper into the opposite danger zone you land.
Three things the model makes visible.
The productive range is narrow and requires active navigation. It is not a stable equilibrium you reach and maintain passively. On a glacier, you are always moving, always reading the surface, always making micro-corrections. The leader who thinks they have “solved” centralization versus autonomy has stopped navigating. They have pitched a tent on the ice and gone to sleep.
The downsides of each pole are not bugs. They are the signal. When your organization starts showing the downside symptoms of whichever pole you are currently committed to (bottlenecks, disengagement, fragmentation, chaos), that is not a failure. It is the polarity telling you it is time to weight toward the other pole. The symptom is the compass. Most leaders treat it as an indictment of the last decision rather than navigation data for the next one.
Velocity is the real killer. A slow drift toward one extreme, caught early, corrects gently. A violent swing, driven by crisis, new leadership, or a “this time we’ll get it right” reorganization, almost always overshoots. The pendulum carries momentum. The organization that spent two years in extreme centralization doesn’t gently arrive at healthy autonomy. It careens past it into fragmentation. And then someone new declares the problem solved by swinging back.
Both/and execution
The Team Test question names this pattern exactly. If the answer came to you immediately, the tension your organization has “solved” three times, you are not looking at a bad strategy. You are looking at an unrecognized polarity being managed as though it were a problem.
The fix isn’t a better solution. It’s a different relationship with the tension itself.
Shifting a high-performance team from exhausting either/or debates into both/and execution requires teaching them that structural tension isn’t a sign of dysfunction. It is the actual engine of their performance. The team stops asking “which is right?” and starts asking “which pole are we currently on, and what is the early symptom that we are drifting too far?”
That is a different conversation. It is quieter. It doesn’t produce clean quarterly wins. It also stops producing the two-year reorganization cycle that is quietly draining your best people.
THE TEAM TEST
What tension is your team currently trying to solve today that actually just needs to be managed?
If you can name it, you already have the diagnostic. The next meeting is where you stop trying to end the debate and start navigating it.
