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.






Comments

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...

Agile Bert joins the world of blog.

My far more technical compadre and fellow Agile Yorkshire attendee 'Agile Bert' (aka John) has joined the blogging world. Will he become a prolific blogger? Will he become a (thought) leader amongst men? Why is he called Bert? That last one actually has an answer: here

Smash the echo chamber

Who doesn't enjoy the warm glow of validation that comes from having others strongly agree with their opinions? It's a great feeling; it's encouraging,  and a gentle massage to our self-confidence. Without this experience, all but the most arrogant of us would soon be wracked with self-doubt, so it's certainly not a bad thing. But... everything in moderation! At time-of-writing I'm in the position of having a team who are incredibly comfortable in voicing their opinion.  Whether they're just brutal or a little further along the spectrum than the average developer I can't be certain, but I do know I can rely on hearing their opinions. Not a great environment if you're sensitive, but it does force me to challenge my views, thoughts, and actions on a regular basis.  And on the assumption that I'm not always correct, which my wife assures me is the case, that's a great thing! Why? Because living inside your comfort zone 24/7 can only re...