Skip to main content

Be kind to yourself.

Would you push your project team until they snap?  Of course not, you believe in sustainable pace.

Would you expect them to consistently sacrifice family time to achieve unviable targets?  Of course you wouldn't, you'd rather they delivered consistently over time while maintaining their work-life balance.

Would you have them work when they're ill?  No, you're not a monster.

I could go on, but hopefully you get the point.

Unless you're an appalling relict of an aggressive 1980s management style, you protect your team.  You realise they're humans with individual lives and needs outside work.

But do you apply the same standards to yourself as project manager?

There's a tendency in our roles to pick up any slack ourselves, to look after the team and the project as a priority.  After all, who gets hauled over the coals if things fall behind?  Whose career could be stalled (or ended in case of a contractor) by one catastrophic deployment?

The longer hours and calls with fire-breathing stakeholders is why we get a couple percent more pay than the rest of the team, right?

Sure.  And we love it.  It makes us feel useful.

But burned out people make mistakes.  Even seemingly unstoppable beast-mode project managers.



So take your own advice.  Learn to say no (politely), take your holidays (all of them), and if you're ill, recover (no logging on to check on things). The world won't fall apart and you might just enjoy life a bit more before the job inevitably takes you out in your 50s.






Labels:

Comments

Post a Comment

Popular posts from this blog

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

Project Team morale and how it is affected by YOUR leadership style.

If I asked what qualifies someone to lead an IT Project you might immediately think of literal qualifications; a degree, a PRINCE2 practitioner certificate, DSDM certification. You might think of the practical skills needed to achieve Project Management tasks; the ability to plan, management of RAID/CARDI items, stakeholder communication. All of these things are vital to managing a project, but as we're often reminded: Management ≠ Leadership And projects need leaders.   Why?  Because people need leaders.  Humans are pack orientated creatures and we are most comfortable within a structure that supports and guides us.  Within a project the same is true.  The 'doers' usually thrive within a supporting structure that takes care of their (professional) needs and protects them from attack.  Without Developers and Testers the rest of the project team is just a lot of expensive * flesh. In a mature and capable project team there is a certain joy to be ...
Post a Comment
Read more