Skip to main content

Empowerment?

The reason I titled this post with a question mark is that I believe empowerment to be a very misused term.

Here's the Cambridge dictionary definition:


Of course, you know this already.
Yet for some, "to empower" has become synonymous with "to abrogate responsibility"

Or in other words, passing the buck to your team:

 'boss we need help dealing with team x'
'you're empowered to deal with that'

 This is just crappy leadership.

 Of course, you have to empower people so you're not a blocker.
Of course, you have to give people additional responsibility to help them develop beyond their current role.

But when you 'empower ' someone, you retain the accountability overall.  It's not a get-out-of-jail-free card to blame them if things don't go as planned or to turn around months later and say 'well you can't complain.  I empowered you to do it and you failed'

 No.  If you're my boss and I fail.  We both failed.  You can't be unapproachable or unavailable and then complain that I didn't ask for help.

That's your job.

 --- As a side note, it always astounds me to see perfectly intelligent project managers understand this concept as it relates to them and their boss, yet entirely miss the point as it relates to their project team.  No matter how much responsibility is shared out amongst members of the team, YOU are still accountable. So tempting as you might find it to throw an unsuspecting team member 'under the bus' (it's not the 1980s, stop being a pest), it almost always reflects badly on you. ---

Some don'ts and do's.
Don't micro manage me
Do give me the freedom to be creative (if there's a 
level of trust I'll discuss it with you anyway)

Don't make me bring every decision to you (I'll either feel you don't trust me or that it's a reflection of your own insecurity)
Do let me make the day to day decisions (that's what 
you're paying me for after all) and trust that I'll 
come to you where required (albeit with a set of 
options or solutions)

Don't make me feel that being empowerment means I'm supposed to know it all and can't ask questions.
Do be there for support and advice when I need it.
(Especially true for experienced PMs in a new organisation 
- remember most inductions are pretty basic so 
on day 1 I'm unlikely to know exactly how 
you implement all of your processes)

Don't blame me when something goes off track.
Do make success and failure a shared 
endeavour (if I'm well supported and delivering, 
it looks like you run a tight ship).

If you know a leader in need of taking responsibility lock them in a room with this video featuring ex-Navy Seal and motivational legend Jocko Willink:


Video by TEDx Talks.

Labels:

Comments

Post a Comment

Popular posts from this blog

Continuous (Self) Improvement

“Everyone thinks of changing the world, but no one thinks of changing himself.” - Leo Tolstoy Introduction: Most people talk a great game about continuous improvement.  And as a group, most of us truly agree with and see the benefits of, the concept as applied to our projects and teams. Sprint Retrospectives, Post Implementation Reviews, 5S, DMAIC, PDSA (not the dog people) and so on. But... Do you practice it personally ?  I don't mean training courses, formal development plans and all the other bureaucracy that people step through stoically every year in a bid to get a pay rise.  I'm referring to the small (but meaningful) improvements we can make every day. Or to work in an Agile principle: "At regular intervals, the team (of one in this case) reflects on how  to become more effective, then tunes and adjusts  its behavior accordingly." Step 1: Feedback (aka input to the CI process): Of course, all improvements need to be identified in the first
Post a Comment
Read more

"We are Agile!"

A phrase Project Managers hear a lot, and one that occasionally proves to be at least partly true. As it's most often spoken rather than written, it is hard to know whether the speaker means 'agile' or 'Agile'.  I find that asking the question ('big A' Agile or 'small a' agile?) can reveal a lot about that person's knowledge of the 'Agile' world.  If you find yourself asking the people around you this question and you receive blank faces or confused responses you can be fairly certain you haven't landed in a particularly Agile organisation, rather you're somewhere that has rolled out a buzzword in the hope of improving speed of delivery. Organisations tend to fall into one of the following categories: - Comfortably Waterfall - Fine . This organisation knows how it wants to work and perhaps has reasons why they prefer to keep projects waterfall. - Waterfall but concerned they need to get on the Agile bandwagon - Confused .
Post a Comment
Read more

Continuous (self) improvement - a personal note

It's a standard Saturday morning and I'm sitting working on my phone at the kids' dojo while they practice sparring drills.  Their coach is giving them some feedback and I'm returning to feedback in this post. When I wrote the last blog on Continuous (self) improvement I was thinking about it in the abstract and although I had many real-life examples in mind, I was then confronted with an opportunity to share an instance almost immediately after it occurred. I write this the morning after a team social occasion (aka leaving drinks) and although I don't drink (medical reasons - don't judge me...) my colleagues certainly do.  These events can be fertile ground for picking up people's feelings and frustrations at work. Sometimes a shared rant is a bonding exercise Sometimes it's an opportunity to let a teammate feel listened to. And sometimes it's a chance to learn how people feel about you or your performance. Over the years it
Post a Comment
Read more