General Stanley McChrystal’s Empowered Execution: What Hundreds of Teams Taught Me About Getting the CEO Out of the Middle of Every Decision

One of the most common frustrations I hear from CEOs sounds something like this:

“I hired great people. Why does everything still come back to me?”

The leadership team is experienced. Functional leaders know their disciplines. The CEO wants people to take ownership. Everyone agrees that decisions should happen closer to the work.

Yet the CEO remains in the middle.

Product wants approval.

Sales wants a decision.

Engineering needs clarity.

Two executives disagree over ownership.

A cross-functional issue surfaces and everyone looks toward the CEO.

Before long, the CEO becomes the person connecting information, resolving ambiguity, prioritizing conflicts, and approving decisions throughout the organization.

General Stanley McChrystal’s concept of Empowered Execution provides a powerful way to understand why this happens.

In the Team of Teams framework, Empowered Execution means decentralizing decision-making to the level necessary to respond effectively to the speed and complexity of the environment. McChrystal Group emphasizes that people closest to an issue are often best positioned to act quickly—but only when the organization has created the conditions that allow them to make good decisions.

After working with hundreds of CEOs, founders, and leadership teams over more than two decades, I have reached a similar conclusion:

Empowerment is not telling people they have authority. Empowerment is building an organization in which people have the direction, context, capability, ownership, and trust required to use that authority well.

This is why getting decisions out of the CEO’s hands is not primarily a delegation problem.

It is an organizational execution problem.

The CEO Bottleneck Is Often Created With Good Intentions

Most CEOs do not wake up intending to become organizational bottlenecks.

In fact, the opposite is usually true.

They want speed.

They care deeply about quality.

They know the history behind important decisions.

They understand the customer.

They have relationships with investors and the board.

They have the broadest view of the organization.

And, especially during the early stages of the company, stepping into decisions works.

A problem emerges.

The founder solves it.

A team gets stuck.

The founder unsticks it.

Two people disagree.

The founder decides.

A major customer needs something.

The founder mobilizes everyone.

This behavior helps many companies survive their earliest years.

The problem is that a leadership behavior that works exceptionally well with 10 people can become a constraint with 50, 100, or 500.

More people create more decisions.

More teams create more dependencies.

More specialization means important information is spread throughout the organization.

If the CEO remains involved in the same percentage of decisions as the company grows, the organization eventually cannot move faster than the CEO can process information.

The founder who once accelerated execution can unintentionally become the limit on execution.

McChrystal’s Empowered Execution Is More Than Delegation

McChrystal Group makes an important distinction between delegation and real empowerment.

Its framework identifies four essential elements of empowerment: Authority, Capacity, Context, and Desire. Authority means people have genuine decision-making power. Capacity means they possess the skills, tools, and resources needed to act. Context means they understand how their decisions connect to the organization’s strategy. Desire means they are motivated to take ownership.

That framework resonates strongly with what I have observed.

A CEO can say:

“You own this.”

But if the person does not understand the strategy, does not know their decision boundaries, lacks the information required to act, expects their decision to be overridden, or cannot secure the resources necessary to execute, very little has actually been empowered.

The title changed.

The underlying operating environment did not.

This is why I have seen organizations promote talented people into leadership roles and then become frustrated when those leaders continue asking for approval.

The problem is not always the leader.

Sometimes the organization has never created the conditions necessary for leadership.

I Learned This Lesson Repeatedly From Hundreds of Teams

In Peak Teams, I wrote that across hundreds of venture-backed companies, I had never seen a successful organization that did not demonstrate empowered behavior across its team.

But I also learned that empowerment is rarely created by personality alone.

One of the recurring situations I encountered looked like this:

A CEO tells me their leadership team will not take ownership.

They describe capable people who continually ask questions that the CEO believes they should answer themselves.

Small decisions travel upward.

People hesitate.

Projects slow down.

Eventually the CEO concludes that the leadership team may simply not be strong enough.

Sometimes that is true.

But frequently, when we get underneath the problem, we find something different.

Roles overlap.

Decision rights are unclear.

The company’s priorities are changing faster than they are being communicated.

The CEO and another founder give conflicting instructions.

Leaders cannot see what other teams are doing.

People have been criticized enough times for independent decisions that they have learned to wait.

What appears to be a talent problem is actually an operating problem.

One CEO Thought Her Leadership Team Would Not Lead

I wrote about one version of this in Peak Teams.

A Series B CEO told me she was frustrated because senior leaders would not make decisions without involving her or her co-founder. She had hired talented people, but everything kept coming back to the founders.

Her instinct was increasingly to become more directive.

If people were not going to make decisions, she would simply tell them what to do.

But when we worked with the team, another picture emerged.

Team members felt scrutinized.

They were unclear about ownership.

Some decisions effectively required approval from two co-founders, who were not always aligned themselves.

One leader explained that they were spending time selling decisions to the founders that could have been spent executing them.

The organization had taught capable people not to act independently.

The solution was not telling them to become more empowered.

The solution was creating greater clarity around roles, responsibilities, ownership, and decision boundaries—and then requiring the founders to honor those boundaries.

Once the organization did that, the CEO described the team as feeling “unlocked.” Leaders stopped coming to the founders every few minutes for decisions, and the CEO regained time for the work she actually owned.

That experience reinforced something I have seen many times since:

People cannot fully own outcomes when the organization has not clearly defined what they own.

Clarity Comes Before Autonomy

This is one of the most important principles behind empowered execution.

Autonomy should not begin with freedom.

It should begin with clarity.

What are we trying to accomplish?

Why does it matter?

What outcome do you own?

Which decisions belong to you?

Which decisions require broader input?

What are the boundaries?

What does success look like?

Which metrics tell you whether you are succeeding?

Which other teams depend on your decisions?

When should something be escalated?

Once those questions are clear, autonomy becomes much safer.

Without them, leaders are forced to choose between two bad options.

They can make decisions independently and risk moving the organization in the wrong direction.

Or they can continually ask for approval and slow execution.

Strong operating systems remove that false choice.

They provide enough structure that people can move quickly within it.

Shared Consciousness Comes Before Empowered Execution

This is why the order of McChrystal’s Team of Teams framework matters.

Empowered Execution does not sit by itself.

McChrystal Group explicitly positions it on top of the other Team of Teams capabilities: Trust, Common Purpose, and Shared Consciousness. Empowerment becomes sustainable when those foundations already exist.

That makes intuitive sense.

If I want someone to make a decentralized decision, they need to understand the larger mission.

They need relevant information.

They need confidence in the people around them.

They need to know that the organization will support reasonable decisions made within agreed boundaries.

This connects directly to the concept of Shared Consciousness from the previous article in this series.

Shared context enables distributed ownership.

Without shared context, decentralization creates fragmentation.

With shared context, decentralization creates speed.

That is the difference between autonomy and chaos.

The CEO Should Not Be the Company’s Context Machine

A frequent reason decisions remain centralized is that the CEO possesses the broadest context.

The CEO knows why the strategy changed.

They heard the latest board discussion.

They know which customer opportunity matters most.

They understand the financial constraint.

They remember why Product made a commitment three months ago.

They know which executive is struggling.

So when a decision appears complicated, everyone naturally turns toward the person who knows the most.

That makes sense.

But it is not scalable.

The answer is not to prevent the CEO from possessing broad context.

The answer is to create an organization in which enough context is shared that other people can make good decisions without reconstructing the business through the CEO.

This is one reason organizational visibility matters so much.

Connected objectives.

Visible KPIs.

Shared priorities.

Known dependencies.

Clear decisions.

A dependable operating rhythm.

All of these reduce the informational advantage that makes the CEO necessary for routine decisions.

The CEO still sees the whole.

But other leaders can see enough of the whole to act intelligently.

Roles and Responsibilities Define the Decision Space

In Peak OS, this is why Roles and Responsibilities matter beyond an organizational chart.

A title does not define ownership clearly enough.

“Head of Product” tells me where someone sits.

It does not necessarily tell me which decisions they own.

It does not tell Engineering what Product can commit to independently.

It does not tell Sales when Product input is required.

It does not tell the CEO which Product decisions they should stop making.

Good role clarity establishes what I think of as a decision space.

Inside that space, the leader should be free to operate.

The stronger that clarity becomes, the less frequently people need to negotiate ownership in real time.

In Peak Teams, I describe how leaders often want to make decisions but do not know which decisions are actually theirs. Once the boundaries are clarified, they can run.

This is where empowerment becomes tangible.

Not:

“You should take more ownership.”

But:

“This outcome is yours. These decisions are yours. These are the constraints. These people depend on you. Here is how success will be measured. Go.”

That is executable empowerment.

Connected Outcomes Give People Direction Without Micromanagement

Roles tell people what they own structurally.

Outcomes tell them what they need to accomplish now.

Both matter.

A person can understand their job perfectly while still being unclear about what matters most this quarter.

That is why Peak connects roles to company and team outcomes.

The organization establishes its direction.

Company objectives identify what must change or be built.

Teams define the outcomes they own in support of those objectives.

Owners become clear.

Metrics provide feedback.

Then leaders can make hundreds of smaller decisions without leadership specifying every action.

This is one of the central benefits of strong objectives.

The objective provides direction without dictating every move.

That is very different from micromanagement.

Micromanagement tells people how to perform every step.

A strong operating system tells people what outcome matters, why it matters, what constraints exist, and how performance will be evaluated.

Then it gives them room to determine how best to get there.

Metrics Give Teams Feedback Without Requiring Constant Executive Inspection

CEOs often remain involved because they do not trust that they will know quickly enough when something goes wrong.

That is understandable.

If the only way to discover whether a team is executing is to ask the team repeatedly, the CEO will ask repeatedly.

That can feel like micromanagement.

But underneath it may be a visibility problem.

Strong metrics change that relationship.

The leader does not need to continually ask whether performance is on track because the system provides feedback.

The team sees it.

The CEO sees it.

Other relevant teams see it.

When something moves off course, it becomes a signal for discussion and problem-solving.

In Peak Teams, I describe KPIs as a way of measuring the business to learn the business. The purpose is not to create surveillance. The purpose is to give teams and leaders information that helps them understand performance and make better decisions.

Visibility can therefore create more freedom.

The clearer the outcomes and feedback, the less need there is for constant checking.

Operating Rhythm Prevents Empowerment From Becoming Drift

Another mistake is assuming that empowered teams should simply be left alone.

That is not what distributed execution means.

Teams still need synchronization.

The environment changes.

Priorities change.

Dependencies emerge.

Metrics move.

New information appears.

Teams learn things that affect other teams.

The solution is not to pull every decision back to the CEO.

It is to establish a predictable operating rhythm through which decentralized teams continually reconnect.

Weekly rhythms create short learning and coordination loops.

Quarterly rhythms create opportunities to adjust priorities and outcomes.

Annual rhythms reconnect execution to longer-term direction.

This is one of the reasons McChrystal Group describes leadership as creating the conditions in which decentralized teams can execute rather than simply issuing commands from above. Its “gardener” metaphor emphasizes cultivating the environment, maintaining the system, and enabling teams to act within acceptable boundaries of risk.

Operating rhythm is part of that environment.

It gives empowerment structure without turning it back into centralized control.

Triage Teaches Teams to Solve Problems Without Sending Everything Upward

Another element of Peak that supports empowered execution is Triage.

Growing companies generate problems constantly.

If every issue becomes a CEO decision, the CEO becomes overwhelmed.

If every team solves cross-functional issues independently, the organization can fragment.

Triage creates another option.

Bring important issues into a structured problem-solving process.

Understand the core issue.

Consider alternatives.

Make a decision.

Define the action.

Assign ownership.

Then move.

In Peak Teams, I describe the CEO’s role in these situations as ensuring a decision gets made when the team cannot reach one—not necessarily being the person who makes every decision. The CEO can make the call when necessary or explicitly empower someone else to do so.

That difference matters.

The CEO remains accountable for the quality of the organizational decision-making system.

But accountability does not require personally owning every decision produced by the system.

Leader as Gardener: The CEO’s Job Changes

One of McChrystal’s most useful leadership metaphors is the gardener.

Traditional leadership can be imagined as a chess master.

The leader sees the board.

The leader determines the moves.

Everyone else executes.

That model works best when the environment is predictable enough for one person to possess sufficient information and control.

Complex organizations rarely behave that way.

McChrystal Group argues that leaders in a Team of Teams create conditions for performance rather than personally controlling every action. The gardener shapes the environment, provides resources, removes obstacles, and maintains conditions that allow teams to grow and adapt.

This may be one of the hardest transitions for successful founders.

For years, their value came from having answers.

Now their value increasingly comes from creating an organization that can produce answers without them.

For years, they solved problems.

Now they must build problem-solving capability.

For years, they made decisions.

Now they need to improve decision-making throughout the organization.

For years, they connected teams.

Now they need to build systems that connect teams.

The CEO remains critical.

But the nature of leverage changes.

A CEO Should Not Be the Operating System of the Company

This is perhaps the simplest way I can describe the lesson.

In the earliest days, founders often are the operating system.

Strategy runs through them.

Information runs through them.

Decisions run through them.

Priorities run through them.

Problem-solving runs through them.

That may be necessary.

But it cannot be the final organizational design.

At scale, the CEO should build an operating system that allows the organization to execute.

Shared direction gives people context.

Connected outcomes create focus.

Clear roles establish ownership.

Metrics provide feedback.

Visibility creates situational awareness.

Operating rhythm synchronizes teams.

Triage solves cross-functional problems.

Learning loops help the organization adapt.

These capabilities collectively reduce the number of situations in which someone has to ask:

“What does the CEO want us to do?”

And increase the number in which people can say:

“I understand what we are trying to accomplish, I know what I own, I have the information I need, and I can make the decision.”

That is organizational leverage.

The Test of Empowerment Is What Happens When the CEO Is Not in the Room

There is a simple test I often think about.

What happens when the CEO is not there?

Do decisions stop?

Does the meeting end with, “We need to ask the CEO”?

Do two functional leaders have enough shared context to resolve a dependency?

Can a leader make a decision inside their role without worrying it will be reversed later?

Can teams understand whether they are on course without the CEO interpreting the data?

Can people resolve most problems at the level closest to the work?

If the organization can execute only when the CEO is present, then the CEO is still part of the operating mechanism.

That may be acceptable early.

It becomes increasingly dangerous as the company grows.

The objective is not to make the CEO unnecessary.

It is to make CEO intervention intentional rather than habitual.

Some decisions absolutely belong with the CEO.

Most should not.

Boards and Investors Should Pay Attention to Decision Dependency

There is also an important governance implication.

A company can look strong while carrying significant CEO dependency.

Revenue may be growing.

The leadership team may be impressive.

Strategy may sound clear.

Yet if most meaningful decisions still require the CEO, the organization may not actually be scaling.

Boards and investors should therefore look beyond the quality of the CEO.

They should ask whether the CEO is creating leadership capability around them.

Do executives own meaningful outcomes?

Are decision rights clear?

Can functions coordinate without the CEO acting as intermediary?

Does information move across teams?

Are risks surfaced early?

Do leaders make and defend decisions?

Is the operating rhythm strong enough to maintain alignment while authority is distributed?

A powerful CEO can create a powerful company.

A powerful organizational system can create a company capable of performing beyond the bandwidth of any single CEO.

AI Will Increase the Need for Empowered Execution

Artificial intelligence makes this issue even more important.

AI is increasing the speed at which people can analyze information, create work, explore options, and act.

That means more decisions can potentially happen closer to the work.

But faster decentralized capability can create faster organizational fragmentation if direction and ownership are unclear.

The future organization cannot respond by routing every AI-enabled decision through senior leadership.

That would eliminate much of the speed AI creates.

Instead, organizations will need stronger decision architecture.

Clear strategic context.

Defined ownership.

Visible outcomes.

Explicit guardrails.

Reliable operating rhythm.

Escalation paths for the decisions that truly require higher authority.

The more capable individuals and teams become, the more important it becomes to define the environment within which that capability can be exercised.

Empowered Execution is therefore not becoming less relevant.

It is becoming more important.

What Hundreds of Teams Taught Me About Empowerment

Across the teams I have worked with, the strongest patterns are remarkably consistent.

Empowered organizations are not organizations without structure.

They usually have more clarity.

People understand where the organization is going.

They understand their role.

They understand what they own.

They understand what success looks like.

They have visibility into relevant parts of the organization.

They know when to make the decision themselves.

They know when collaboration is required.

They know when escalation is appropriate.

And they trust that if they make a reasonable decision within those boundaries, leadership will support them.

That creates speed.

It also creates leadership development.

People become better decision-makers because they actually get to make decisions.

Teams become more capable because they are responsible for outcomes.

CEOs gain leverage because leadership capacity expands throughout the organization.

The company becomes less dependent on heroics at the top and more dependent on capability throughout the system.

The Goal Is Distributed Ownership, Not Distributed Chaos

General Stanley McChrystal’s concept of Empowered Execution captures one of the central challenges of organizational scale.

Leaders need decisions to move closer to the people with the best information.

But simply giving away authority is not enough.

People need common purpose.

They need trust.

They need shared consciousness.

They need clear roles.

They need outcomes.

They need feedback.

They need decision boundaries.

They need an operating rhythm that reconnects them to the organization as conditions change.

That is what turns empowerment from a leadership slogan into an organizational capability.

After working with hundreds of teams, I have become convinced that one of the defining transitions of scale is this:

The CEO must stop being the place where execution comes together and start building the system through which execution comes together.

That does not make leadership less important.

It makes leadership more leveraged.

The best leaders are not the ones who make the most decisions.

They build organizations capable of making more good decisions without them.

That is Empowered Execution.

And that is one of the central ideas Peak OS is designed to operationalize.

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?