When the winds of change blow
Hierarchy works well when conditions are stable and problems are known. During transitions, its limits become visible. What replaces rigid structure is not chaos, but ownership, with decision making moving toward those closest to the work.
Ever notice how organizations sometimes just... stop? Not with a bang, but a whimper. No big announcement that the old rules are out the window, no memo saying "processes suspended." It just happens. Quietly. Usually when things get uncertain, and suddenly, that neat org chart doesn't tell anyone what to do next anymore.
Most companies are built for smooth sailing. You've got your clear roles, your "ask this person then that person" steps, your review meetings, your approval forms. That stuff works brilliantly when everyone knows the goal and there's no rush. Hierarchy brings order, keeps things stable. But what happens when the ground starts shaking?
The Org Chart Gets Heavy When the World Shifts
Think about those times of big transition. Markets flip overnight, new rules drop out of nowhere, or that big plan everyone believed in suddenly makes no sense. At this point, you're not just following a recipe; you're trying to figure out what the meal should even be. The job isn't to do the plan, it's to discover the plan.
This is where the traditional hierarchy starts feeling less like a guide and more like a heavy anchor. The people at the top, who have the power to make decisions, are often the furthest from the messy details. Meanwhile, the folks on the front lines? They've got the freshest info, the real pulse of what's happening, but not much formal say. In calm times, you can manage this push and pull. But during big changes, it becomes a total roadblock.
So, what happens? Everything slows down just when you need to speed up. Meetings pile up, "alignment" becomes the goal instead of action, and everyone waits for certainty that simply doesn't exist anymore. It's not that people are bad at their jobs; it's just that a system built for predictable problems is now facing the totally unpredictable.
During change, waiting isn't playing it safe. Waiting is the risk.
Process Isn't Evil, But It's Got a Blind Spot
You often hear people complain about "managers" versus "operators," or "process" being the big bad villain. But that misses the point. Process isn't evil. It exists for good reasons: to help companies grow, make fewer mistakes, and do things consistently. Without it, most businesses wouldn't even survive their first few years.
The real issue is that process is designed for repeating what you already know, not for discovering new things. When you're not even sure what the problem is, blindly following steps doesn't reduce risk; it just puts off actually learning anything. When things are uncertain, delaying action often costs more than making a quick, reversible mistake.
Why do "operators" often seem better at handling these moments? It's not that they're braver or smarter. It's their vantage point. They see the consequences firsthand, get immediate feedback. There's no escaping reality. If something breaks, it breaks right in front of them. This closeness to the action creates a natural drive to do something, even when they don't have all the answers.
Managers, on the other hand, are trained to keep things steady. In stable times, their job is to create predictability through standardizing things, getting everyone on the same page, and reviewing everything. Those skills are super valuable. But if they stick to that exact playbook during big shifts, they can unintentionally slam the brakes on the whole organization. Seeking endless consensus makes sense when mistakes are costly. But when conditions are changing fast, waiting often costs even more than a misstep.
Decisions Shift to the Front Lines
What looks like hierarchy "collapsing" is really just decisions moving to where the action is. When formal authority needs perfect clarity to act, it loses its power. But when judgment can thrive in ambiguity, it gains influence. Decisions naturally gravitate to the edges of the organization, where information is fresh and feedback is instant.
You see this in everyday ways:
- Engineers push out urgent fixes without waiting for a dozen sign-offs because a live system issue demands speed.
- Product managers pivot their plans mid-cycle because what they thought was true in the market has clearly shifted.
- Founders scrap old roadmaps because a new opportunity or threat has emerged.
None of this is rebellion. It's smart adaptation to new realities.
Leadership During the Whirlwind
Great leaders recognize this shift and adjust their own game.
Peter Drucker famously said, "The best way to predict the future is to create it." During transitions, leadership isn't about protecting the old system; it's about shaping the new one. Instead of piling on more rules, they focus on removing obstacles. They clarify who can decide what right now, they define the goals instead of dictating every how, and they create a safe space for people to act without fear of being crushed for a reasonable mistake.
This isn't leaders stepping back; it's leading differently. The aim isn't to get rid of structure entirely, but to make it flexible enough so people can learn and adapt. Organizations that nail these transitions loosen up the hierarchy temporarily but keep accountability sharp. People get permission to act, but not to hide. Mistakes are okay, but ownership is still crystal clear.
The Real Enemy: Standing Still
The biggest screw-ups I've seen during change weren't from bad decisions. They were from hesitation. Teams waiting for approvals that never arrived. Managers insisting on process even when speed was everything. Leaders hunting for certainty in a world where certainty had simply vanished.
On the flip side, the organizations that thrived understood that hierarchy is a tool, and you use the right tool for the right job. In stable times, it brings efficiency. In unstable times, it needs to bend, or you go around it. Knowing when to switch gears, that's a core leadership superpower.
My Own Simple Rule
This whole idea even changed how I operate when things are fuzzy. Instead of asking, "Is this technically my job?" I ask, "Am I willing to own the outcome?" If the answer's yes, I act or help someone else act. If it's no, I step aside. It cuts through the fog without needing a fancy title.
As that old Chinese Proverb reminds us:
"When the winds of change blow, some people build walls and others build windmills."
Titles don't vanish, but they stop being the main thing that organizes everyone. What matters more is good judgment, being close to reality, and a willingness to truly own the results. Hierarchy isn't failing in these moments. It's being put to the test. The outcome depends entirely on whether leaders let it adapt, or stubbornly insist it stays exactly as it was.