Empowerment Isn’t an Announcement

I once had a conversation with an engineering leader who was discussing a lack of empowerment among their reports. “You’re empowered!” they stated emphatically. 

This move reminded me distinctly of an episode of “The Office” where the boss Michael Scott tried to declare bankruptcy by shouting to the rest of the room, “I declare bankruptcy!” 

Loudly proclaiming something to be true worked in exactly neither of these situations. In both, the person displayed a complete misunderstanding of how the system actually works. 

Announcing empowerment is not the same as creating an environment where people can exercise it. The declaration feels like action but doesn’t change anything about the system that’s in place. Leaders often confuse stating intent with creating the conditions that make the outcome possible.

Often what’s holding a team or an org back from empowerment is a lack of safety and clarity built into the team infrastructure. Nominal authority without psychological safety is unusable. People need to know what they own, what the boundaries are, and that acting within them won’t get them burned. 

I’ve seen talented people afraid to act on initiative because of one negative previous experience. Teams remember where initiative became painful, and organizations teach empowerment through memory more than messaging. 

Another blocker to having an empowered team is not understanding clearly who owns the decisions. I’ve lost count of the number of times I’ve watched teams spend fifteen minutes trying to answer a simple question: who actually gets to decide this?

Now imagine those same people in situations where they are the decider and don’t know it. Ambiguous ownership kills autonomy quietly. Without explicit rights, people default to asking rather than acting — and that looks like disempowerment even when it isn’t.

The hardest source of disempowerment to diagnose is often the most invisible one: escalation cost. People may technically be allowed to decide but rationally avoid it because the cost of being wrong is too high. 

It takes a lot of intentional effort to build a space where failing is an accepted part of the process. 

Without a safe space to fail, calling out a lack of empowerment is infrastructure failure masquerading as individual deference.

I’ve also seen situations where someone was encouraged to operate more autonomously, took initiative, and then discovered the organization had a much narrower definition of acceptable autonomy than they realized. Not because the work itself was catastrophic, but because it created social or political friction. 

Experiences like that train people quickly. Teams learn what kinds of risks are tolerated, regardless of what leadership says in principle.

When empowerment isn’t happening, there’s one explanation leaders reach for surprisingly often. It’s leaning on the idea that people don’t want to take advantage of empowerment, that they don’t want to be leaders. You can offer people empowerment but you can’t make them lead. 

Some people genuinely don’t want autonomy, but that’s also the most available rationalization. The harder question: did they not want it, or did they learn it wasn’t safe here? 

Teams don’t learn empowerment from mission statements.

They learn it by remembering what happened the last time someone acted without asking.