The Pendulum of Power: When Directive Leadership is the Only Way to Save Your Product

In mainstream product management circles, "autonomous product teams" and "extreme roadmap ownership" get treated like sacred text. We're told the only way to build a high-performing organization is to give teams total independence: to design their own sprints, run their own discovery, and experiment their way to success.

But when an organization faces an existential threat, whether it's a sudden market collapse, a major technological shift, or an aggressive regulatory deadline, that consensus-driven culture can turn into an expensive, bureaucratic bottleneck.

When Airbnb CEO Brian Chesky dismantled the company's decentralized, splintered subdivisions and pulled them into a single, centralized organization under one roadmap, it sent shockwaves through the tech community. To many, it looked like a step backward into command-and-control bureaucracy. It was actually something closer to wartime leadership.

Having supervised more than 50 product missions across industries at Product People, I've seen firsthand that directive leadership isn't a relic of the past. Applied with clear boundaries, it's a high-leverage tool that can pull an organization out of stagnation and chaos.

‍

The Trailing Indicators: When Decentralization Costs Too Much

Decentralization and team autonomy aren't inherently good or bad. They're situational tools. When your market is stable, your revenue is predictable, and your foundation is secure, autonomy is a powerful vehicle for exploration and incremental innovation.

But when conditions change quickly, whether externally or internally, keeping a scattered, autonomous structure becomes a liability. Organizations rarely centralize before it's too late, so leaders need to watch for three trailing indicators that a decentralized model is failing:

1. Speed to impact is decaying. Look at your trajectory over a rolling two- to five-year window. Measure the gap between spotting a business opportunity and proving it out or turning it into revenue. If growth is dropping while the time to ship meaningful updates keeps climbing, your consensus-driven process is choking execution.
2. Everything is a priority, which means nothing is. Listen to frontline feedback. When product managers and engineers keep saying they're unsure what the company is actually aiming for, that's priority dilution setting in. Teams end up spinning their wheels on small, disconnected features that don't move the business.
3. Accountability is diluted. As cross-functional teams multiply, ownership of core outcomes gets fuzzy. Committees replace individual decision-makers, and internal politics start to outweigh customer value.

‍

The Misconception of Autonomous Teams: Innovation vs. Systematic Growth

The tech industry's insistence that teams must always have absolute autonomy rests on a misunderstanding of what autonomy is actually for.

Autonomy is built for innovation. But innovation isn't the same thing as systematic, predictable business growth.

If a company has a solid financial foundation, steady cash flow, and market stability, it can afford to fund independent teams to experiment, fail, and stumble onto non-linear ideas. But if the company is stagnating or failing to address a mid-term market or technological shift, letting teams chart their own course gets dangerous fast.

When a business is facing real structural risk, it doesn't need a dozen teams running isolated design sprints. It needs centralized, authoritative alignment to execute on the obvious, non-negotiable work required to survive.

‍

From the Field: Halting Chaos to Force Critical Compliance

I once worked with an organization that was completely paralyzed by its own consensus culture. The company prided itself on being innovative, agile, and fast-paced, and leaned heavily on design sprints and decentralized experimentation.

But the market around them had shifted. Government agencies had introduced strict compliance requirements with real mid-term consequences. If the product didn't comply within a tight window, the company would lose its license to operate in that market entirely.

Despite how existential the threat was, the decentralized structure made it nearly impossible to act. Executive leadership agreed publicly that compliance mattered, but kept greenlighting every other team's independent project too, saying things like "yes, compliance matters, but these other product ideas are also great."

That mixed messaging left teams stuck. Product managers were genuinely worried about the company's survival but had no real capacity to hit the regulatory deadline, since they were also being told to keep their existing roadmaps running.

To break the deadlock, we paused the autonomous model and moved to a directive approach. We built a single, tightly controlled compliance roadmap for roughly a year. Leadership stepped in and froze secondary projects, pulled back engineering capacity, and pointed every available resource at the regulatory milestone.

It wasn't a comfortable transition. Teams didn't enjoy losing their creative freedom or watching pet projects get shelved. But because the mandate came with real clarity about why it was necessary, people understood the trade-off. Centralizing command unblocked execution, got the company to full compliance, and protected its market footprint.

‍

Preventing Burnout: The Mechanics of Time-Bounded Centralization

Directive leadership is expensive to run. It puts enormous cognitive load and pressure on the executives holding the roadmap, while frustrating the product managers who lose their day-to-day autonomy. Since none of us are immune to blind spots or limited perspective, staying centralized for multiple years will eventually burn leadership out and harden into a toxic culture.

To use wartime leadership without permanently damaging your culture, it needs a built-in expiration date.‍


Before making the pivot, leadership needs to sit down with the organization and set expectations up front. Something like: "We're entering a highly structured, centralized sprint for the next X months to hit this specific milestone. This isn't because our agile culture was wrong; it's because business safety comes first right now. Once we hit this milestone, we'll dismantle this bottleneck and go back to a creative, decentralized model."

Framing directive leadership as a temporary tactical move, not a permanent cultural shift, creates psychological safety. The team can tolerate losing autonomy because they can see the finish line, and executives are protected from burnout because they know the weight of the roadmap only sits on them for a fixed, sustainable stretch of time.

‍

Decompression: Switching Back from Wartime to Peacetime

When the crisis passes, or the milestone is hit, leaders often make a second mistake: they drop all the controls at once and create a power vacuum. Getting back to peacetime takes a managed, two-part approach.

1. Broadly Defined, Executive-Driven Focus

Peacetime doesn't mean doing random things with no direction. Leadership still needs to communicate a clear focus, just a broader one. Instead of a strict compliance checklist, the directive shifts to macro-level business goals. For example:

• "For the next six months, our focus is expanding into new geographic markets."
• "This quarter, we're maximizing average contract value per enterprise client."
• "Our primary metric for the next half-year is client satisfaction and net promoter score."

That high-level clarity sets the boundaries of the playing field, so the organization stays aligned without leadership having to manage the granular details.

2. Time to Think and Decentralized Ideation

Once the macro-direction is set, teams need dedicated time and space to translate it into their own areas of responsibility. Autonomy doesn't switch back on overnight. It takes structured rituals to get teams back into a creative mindset.

Leaders can help this along with a hackathon, an offsite brainstorm, or structured workshops focused on mapping new solution paths. Teams work independently to shape their plans, present their ideas back to the wider organization for feedback, and build bottom-up roadmaps that tie back to the company's overall vision. That deliberate process lets teams reclaim ownership with confidence, bringing the company back to a healthy, innovative peacetime mode without losing structural alignment.

‍

Conclusion: A Call to Leadership Action

The real lesson from Brian Chesky's Airbnb turnaround isn't that you should permanently become a centralized micromanager or kill off autonomous discovery. It's that good leadership means having the flexibility to shift your organizational structure when the market reality around you changes.

Stop treating popular product management frameworks as absolute dogma. Look honestly at your organization's output speed, revenue growth, and alignment. If your decentralized teams are stuck in endless committee discussions while the product stagnates, put the peacetime playbook down. Step in, centralize the roadmap, set an explicit timeline, and push the organization forward until your foundations are secure again.

‍