Only half of NHS staff feel involved in decisions that affect their work. In one of the world’s most admired healthcare systems, staffed by some of the most skilled professionals anywhere, half the workforce don’t feel empowered.
This isn’t an NHS problem. It’s a leadership problem that occurs everywhere that complexity meets hierarchy.
Talk to frontline staff in any large organisation and you’ll hear the same frustration. Scientists who can’t order basic lab supplies without various approvals, social workers drowning in bureaucracy and process while children remain at risk, software engineers in growing startups watching decision-making slow as the company scales and local government officers who know exactly what their community needs but lack authority to act.
The pattern is identical across all of these examples; capable people, doing complex work, stripped any decision making power.
There is a bit of a paradox that makes this particularly painful. The 2024 NHS Staff Survey shows that 87.76% of staff say their role makes a difference to patients. These are people who chose healthcare because they wanted to help, and are motivated, skilled, and committed.
The same survey shows:
• 50.11% feel involved in decisions affecting their work
• 61.82% feel safe to speak up
• 49.52% believe their concerns will be addressed
Research consistently shows that staff involvement in decision-making is the single strongest driver of organisational performance. In healthcare, it predicts care quality, patient safety, staff retention, reduced mortality, and innovation. In other sectors, the correlation is equally strong; employee autonomy predicts everything from customer satisfaction to profitability.
We say we value our people. Then we build systems that ignore them.
In complex systems, leaders instinctively reach for control. They add more rules, more escalation, more approval layers. They do it because it feels safer. If we can just specify the process tightly enough, standardise the approach and require sign-off at each stage, surely we can prevent errors?
Unfortunately, complexity doesn’t work that way and tighter control doesn’t solve complex problems, it creates new ones such as bottlenecks, delays, workarounds, disengagement, and cynicism from talented people who have stopped trying to improve things because “it’s not worth the hassle.”
The pharmaceutical industry knows this pain intimately. Drug development is exquisitely complex, yet many pharma companies have layered so much process onto their scientists that innovation is suffocated under the weight of approvals. The scientists who could solve the problem are too busy filling in forms to explain why they need a chemical that costs £30.
What the Military Learned (The Hard Way)
The military’s painful education on this began long before modern warfare.
October 25th, 1854 during the Crimean War, Lord Raglan, the British Commander-in-Chief, sat on high ground with a clear view of the battlefield below. He could see Russian forces removing captured British guns from Turkish positions on the Causeway Heights and decided that this needed to be stopped.
He scribbled an order: “Lord Raglan wishes the cavalry to advance rapidly to the front, follow the enemy, and try to prevent the enemy carrying away the guns.”
The order went to Lord Lucan, commander of the Cavalry Division, positioned down in the valley. From where Lucan stood, the terrain blocked his view entirely. He couldn’t see the Causeway Heights and couldn’t see any Russians removing guns. The only guns he could see were Russian artillery positioned at the far end of the North Valley which was a completely different target, heavily defended from three sides.
Lucan was confused. “Attack what? What guns, sir?”
Captain Nolan who was delivering the order, was already furious with Lucan for what he saw as timid leadership. In anger, he flung out his arm: “There, my Lord, is your enemy! There are your guns!”
The gesture was vague, pointing toward the Russian battery at the end of the valley. Not the guns Raglan meant. The wrong target entirely.
Lucan read the order “with much consideration, perhaps consternation would be the better word, at once seeing its impracticability for any useful purpose whatever.” He knew it was suicide and so did Lord Cardigan who would lead the charge. When given the order, he pointed out the obvious: “the Russians have a battery in the valley to our front, and batteries and riflemen on each flank.”
But the culture didn’t allow for questions. Lucan replied: “I know it, but Lord Raglan will have it. We have no choice but to obey.”
Six hundred and seventy cavalrymen charged into what would be immortalised as “the valley of death.” They were fired on from three sides. Captain Nolan was killed in the first moments possibly trying to correct his fatal error. Within twenty minutes, nearly 300 men were dead or wounded and forty percent of survivors were casualties.
What went wrong?
Raglan had situational awareness, Lucan didn’t. Raglan wrote vague orders. Nolan delivered them without clarity, and the system demanded compliance.
If Lucan and Cardigan had been empowered to question orders that made no tactical sense, the charge would never have happened. If Raglan had understood that his view wasn’t Lucan’s view, he would have written clearer orders. If the culture had valued psychological safety over blind obedience, someone would have stopped it.
Instead, six hundred men charged because the system confused following orders with doing the right thing. It was a perfect demonstration of what happens when you combine vague direction with a culture that punishes questions and rewards compliance.
The lesson took decades to learn fully, but eventually, the military developed something called Mission Command. Traditional command-and-control worked when warfare was predictable with mass armies, clear front lines and slow-moving communications. Commanders could plan in detail because the situation tomorrow would roughly resemble today. That model collapsed when warfare became fast, networked, and unpredictable.
Mission Command is a leadership philosophy built on a simple principle. Leaders define what needs to happen and why it matters. Frontline teams figure out how. Crucially, they’re empowered and expected to adapt or question when the situation changes or the order doesn’t make sense. Decision-making authority sits at the lowest appropriate level, psychological safety is non-negotiable and initiative is rewarded, not punished. The Light Brigade wouldn’t have charged if Mission Command had been the British doctrine in those days.
When General Stanley McChrystal took command of Joint Special Operations in Iraq in 2004, his elite task force was losing because Al Qaeda operated as a fast-moving network, and the military was a slow-moving hierarchy.
McChrystal transformed his force into a network that involved radical transparency, daily briefings connecting everyone and decisions made by those closest to the problem. They went from hierarchy to network, and they started winning.
The distance from the Light Brigade to McChrystal’s task force measures more than 150 years and shows the shift from “follow orders, don’t think” to “understand the mission, then execute with judgment.”
What This Looks Like in Practice:
If you think that Mission Command is about abandoning all structure, you have the wrong picture. It’s about providing clear intent, then trusting people to figure out how.
❌ Command-and-control: Every spending decision needs approval.
✅ Mission Command: Teams manage budgets within clear parameters.
❌ Command-and-control: New processes are designed centrally and rolled out to everyone.
✅ Mission Command: Intent is set centrally, solutions are designed locally.
❌ Command-and-control: Incident reviews focus on “who’s at fault?”
✅ Mission Command: Teams run quick learning reviews: “What happened, what did we learn, what changes now?”
❌ Command-and-control: Staff wait for permission to improve things.
✅ Mission Command: Staff are trusted to make changes within clear boundaries.
The King’s Fund research shows that NHS organisations are among the most hierarchical of all sectors, but it is not unique. Large corporations, government departments, even scaling startups default to the same pattern. As organisations grow, they add layers, layers add delays, and delays frustrate the very people you hired for their knowledge, skills and experience. That gap between engagement and empowerment isn’t an accident. It’s been built over decades of centralised control, and that control impacts capability.
In complex systems, the opposite is true. Excessive control creates the illusion of safety while introducing new risks such as exhausted staff, workarounds that bypass the official process and good people leaving for organisations that trust them.
The best staff leave first because they have options.
The Real Challenge:
The question for leaders isn’t whether Mission Command sounds nice in theory. The question is ‘what would it take to actually implement it?’
What would it take to move from “check with your manager” to “you know what is best”? From “wait for approval” to “act within your authority”? From “this is how we’ve always done it” to “what does success look like, and how will you achieve it?”
If Mission Command works on battlefields, it can work anywhere. The principles are the same whether you’re commanding troops, running a hospital, developing drugs or delivering public services.
The risk isn’t giving capable people more autonomy, it is continuing to believe that smart people need permission to do what you hired them to do.
If half your workforce feels unempowered, it is because the system doesn’t trust them.
That’s the problem worth solving.
