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 i...
Post a Comment
Read more

The case for Project Management in Agile?

OK, I know how most of the Agile community feels about Project Managers: Process over People Meetings Documentation Urrgh... But however you name the role (Agile Delivery, Scrum Master, Project Manager) and whoever does it  - someone needs to help the team to: Plan Track Deliver Communicate Being a group of incredibly talented engineers does not give a team the right to ignore 3.5 of these. All too often, engineers want to dive in to designing and building great software, but see planning as a hassle, tracking as a waste of time (or an abuse of their rights), communication as an alien concept and delivery (the fun bit) as something that will be done when it's done. It may be popular to talk about being a 'self-organising team' and railing against any form of 'order' being imposed.  But why is that order being imposed?  Maybe it's to deal with the chaos that your s-o-t has failed to deal with so far. As organisations scale and the senior leadership gets further a...
Post a Comment
Read more

Agile Armchair Generals

If you're an Agile practitioner of any sort you will understand what I mean by Armchair Generals (if not, it may be an idea to check if you are one..). Apropos of nothing an email arrives that questions the management of your project in terms of whether it is properly 'Agile'. Feedback is, of course, a great tool.  But it must always be understood within the context of the person providing it. So when the email lands questioning the type of contingency you've built into your project or the depth of analysis performed on your requirements set, ask yourself: 1. Has the questioner spotted something you and the team have missed? It happens.  That's why independent reviews can be helpful. 2. Has the questioner misunderstood something about your project?  If so, maybe your communications weren't quite clear enough or they've missed something - it happens, we're all busy. If the questioner has understood the topic correctly and is simply disagreeing ...
Post a Comment
Read more