LEADERSHIPWeeks to result

Empowered Execution

Push decision-making authority to the people closest to the problem, armed with shared consciousness

Problem it solves

ineffective leadership

Best for

Organizations where decision speed is critical and leaders cannot possibly understand ground conditions as well as the people on the front lines

Not ideal for

Situations requiring tight regulatory compliance or where errors have catastrophic irreversible consequences without any room for correction

Overview

Why this framework exists

Empowered execution is the practice of pushing decision-making authority to the individuals and teams closest to the problem, on the condition that they are armed with the shared consciousness needed to make those decisions wisely. It reverses the traditional model where subordinates provide information upward and leaders push commands downward. Instead, leaders provide information and context downward so that subordinates, armed with understanding and connectivity, can take the initiative. The guiding rule becomes: if something supports our effort, as long as it is not immoral or illegal, you can do it.

Core principles

8 total
  1. The 70 percent solution today is better than the 90 percent solution tomorrow, but empowered people often deliver the 90 percent solution today
  2. Leaders provide information so subordinates can decide; the old model where subordinates provide information so leaders can decide is reversed
  3. Decentralize until it makes you uncomfortable; the sweet spot is on the brink of instability
  4. An individual who makes a decision becomes more invested in its outcome
  5. The person on the ground comprehends complexity in ways that defy visual and audible remote monitoring
  6. Simply removing constraints without providing context is dangerous; empowerment requires shared consciousness
  7. Eyes On, Hands Off: if you can see what is happening, you do not need to control it
  8. If something supports our effort, as long as it is not immoral or illegal, you can do it

Steps

5 steps
  1. Establish Shared Consciousness First
    Empowered execution only works when people have the contextual understanding to make wise decisions. Before pushing authority down, ensure that information flows freely and that people at every level understand the strategic picture. Nelson's captains could fight independently at Trafalgar only because Nelson had spent decades cultivating their judgment and ensuring they understood the overall strategy.
    Pro tipIf you try empowerment without shared consciousness, you will get chaos. The order matters: transparency first, then autonomy.
    WarningSkipping this step is the single most common failure mode. Empowerment without context produces well-intentioned but uncoordinated action.
  2. Reverse the Information Flow
    Instead of subordinates reporting information up so that leaders can decide, have leaders push information and context down so that subordinates can decide. Pump general-officer-level awareness throughout the ranks. Give people used to tight orders and limited visibility the insights once reserved for senior leadership.
    Pro tipMcChrystal used the metaphor of the Visible Man: if subordinates made their operations transparent, he would watch from a distance. If they did not, he would perform exploratory surgery.
  3. Begin Pushing Authority Downward
    Start delegating decisions that you could technically make yourself. This will feel like shirking responsibility. It is not. The most confident subordinates will begin making decisions above their pay grade and simply informing you afterward. Publicly endorse their initiative to create a multiplier effect where more people begin taking matters into their own hands.
    Pro tipThe first time a subordinate makes a major decision without asking, publicly support it in front of the organization. This sends a stronger signal than any memo about empowerment.
    WarningSome subordinate leaders will try to hold authority at their level rather than pushing it further down. Watch for this and intervene.
  4. Establish the Guardrails
    Define the boundaries simply: if it supports the mission and it is not immoral or illegal, do it. This replaces complex approval matrices with a clear principle that people can apply in real time. When the most common question you ask your force is 'What do you need?' instead of 'What do you want to do?', the transformation is working.
    WarningThere will be growing pains. Occasionally you will learn about decisions for the first time from partner agencies. Support the decision publicly and coach privately.
  5. Adopt the Eyes On, Hands Off Posture
    Use technology to maintain visibility into operations without using that visibility to micromanage. Supervise processes, not individual decisions. Ensure the organization avoids silos and bureaucracy rather than making individual operational calls. The leader's job shifts from chess master to gardener.
    Pro tipMcChrystal could monitor any operation in real time via video and radio, but he never told operators what to do on a raid. Having situational awareness helped him do his part better, not reach in to do theirs.
    WarningFor instinctive micromanagers, this is the hardest step. The capability to intervene is not permission to intervene.

Checklist

Saved in your browser

Examples

2 cases
The Task Force's Raid Acceleration

Under the old system of centralized approval, the Task Force managed ten to eighteen raids per month. By 2006, with empowered execution in place, the force conducted three hundred raids per month with minimal increases in personnel and funding. Junior operators and analysts made decisions that previously required general-officer approval.

OutcomeThe force was running seventeen times faster, and the quality of decisions actually improved because the people closest to the problem understood ground conditions better than remote commanders.
Nelson at Trafalgar

Admiral Nelson spent decades cultivating his captains' independent judgment and ensuring they understood his overall strategy. At Trafalgar, his perpendicular attack created chaos in which his empowered captains thrived while the enemy, trained to follow flags, flailed. When Nelson was mortally wounded mid-battle, his captains continued fighting without missing a beat.

OutcomeFrench Vice-Admiral Villeneuve observed after the battle: to any other nation the loss of a Nelson would have been irreparable, but in the British fleet, every captain was a Nelson.

Common mistakes

3 traps
Empowering without first establishing shared consciousness
Simply removing constraints without providing context produces well-intentioned chaos. Nelson's captains could act independently only because they understood the overall battle strategy. Without shared consciousness, empowered execution is just decentralized confusion.
Using new technology to centralize rather than empower
Modern communications give leaders the ability to micromanage from thousands of miles away. The temptation to use real-time video feeds and radio to direct every operation is overwhelming. But centralization at speed produces bottlenecks that the enemy exploits.
Confusing empowerment with abdication
Empowered execution is not total autonomy. Leaders must still set strategic direction, maintain the information ecosystem, and model the culture. The gardener tends the garden constantly; she just does not tell each plant how to grow.

Origin story

How this framework came to be

Even after building shared consciousness, the Task Force was still not fast enough. Decisions that required McChrystal's approval created bottlenecks. McChrystal realized that the 70 percent solution today was better than the 90 percent solution tomorrow. But when he actually began pushing authority down, he discovered his estimates were backward: the people on the ground were delivering the 90 percent solution today instead of the 70 percent solution tomorrow. The quality of decisions went up, not down, because the people closest to the problem understood the complexity in ways that defied remote observation.

Source

Traced to primary
Source · BOOK
Team of Teams: New Rules of Engagement for a Complex World
General Stanley McChrystal · 2015
Open source →

Related frameworks

Browse all Leadership →