The Three C's of Empowerment
Hi folks, first post back after the break. I hope you all had a great holiday season and that the new year is treating you kindly (at least kinder than last year). I thought today that I would go back to a topic that I have covered before, because I think I left something important out when I covered it the first time. I have written before about empowerment and what conditions need to exist before people will accept that empowerment (here) . Empowerment isn't something you can just give to someone and expect it to work, they need to accept the responsibility and authority that they are given. If they don't accept it, they will be empowered on paper but will still turn to the hierarchy to make decisions for them.
I said before that there are two key things that need to exist in order for people to accept empowerment - clarity and competence. Clarity is the organisational clarity around why the decision needs to be made and what the operational constraints and limits are on the options that can be considered. Competence is the skills and other knowledge that someone needs in order to operate in that space. Without those two, no matter how much you tell people they are empowered to act, they will not do it. Unless they feel competent and have the right clarity, empowerment will not happen. All that still holds from when I originally wrote it, but I left something out. There is a third C - Care.
Empowerment and Control
One of the most common complaints I hear when speaking to senior leaders is around a lack of empowerment in their teams. More specifically, the leader is trying to empower their people but the people are not responding - "I have told them they are empowered, but they still come to me for every little decision". Empowerment is a tricky thing. Telling people that they are empowered is easy, getting them to behave in an empowered way is a very different matter. The problem here is that we are looking at empowerment the wrong way round. Empowerment is not something you can just give to someone. While the giving of empowerment is important, it's not the only step. Empowerment only works when the receiver accepts it. You can give empowerment all you like, but if the intended recipient doesn't accept that empowerment, nothing will happen.
But why wouldn't someone accept empowerment? Everyone wants to be empowered don't they? Why don't they jump at the chance? Many years ago I worked for a very large engineering company and the management wanted to try out this brand new (It was a long time ago) empowerment thing. So they gave every employee an "empowerment card" with a statement from the CEO on it that said that anyone in the organisation was empowered to make any decision required. The idea was that if you wanted to seize empowerment by the horns and make a decision that was out of your normal role, you could whip out your card, toss it on the table and say "The CEO has empowered me to make this decision", and away you go. Sounds great doesn't it? Trouble is, not one person used it. Out of the 150,000 people in the company, not one person used one. Zero. Why?
Control vs Empowerment
There has been a lot of talk at work about increasing empowerment and employee engagement. The common complaint I get from management is that "we have empowered our people but they just won't make use of it". It's a common story. Management gives empowerment but nothing at all happens. Things go on as they did before - everyone looks to management for direction. No one takes initiative. No one takes ownership. No one is empowered.
Empowerment takes more than a few words from management. You can't just tell people they are empowered and lo and behold, they are empowered. Empowerment is something people can't be given. They need to take it, it isn't something you can give. It is something people need to become. Management can't give empowerment. What they need to do is create an environment that allows people to become empowered.
Agile Leadership
In previous posts (here, here and here) I have called out the need for really solid agile leadership to enable change. Without great leadership, change falters. We know what bad leadership looks like - directive, dis-empowering, disconnect between what they say and what they do. We all know the symptoms of bad management. But what does good management look like?
We can do the obvious and just say that good leadership looks like the reverse of bad leadership - non directive, empowering, behaves in accordance with what they are saying and so on. All that is true, but I have seen really empowering, non directive leaders who were still bad leaders at driving change. I think there is something fundamental that all leaders need to make them effective at delivering lasting change. That thing is the ability (and desire) to change themselves.