James King

What you do next matters

Archive for the ‘Reflection’ Category

They need to fix accountability

Posted by James King on February 26, 2010

My favourite comment for the week was me and a friend talking about a project we were consulting on. We agreed that “they need to fix their accountability”.

While we might be right, we realised that it is a bit wimpy to suggest that someone else has to fix accountability for a project you are on.

So we had a long discussion about what we could do on the project and we concluded we just needed to make sure we were clear on
- what we delegate (including escalate or ask for);
- when we are ambiguous about our own accountability for something and our own authority for getting things done
- when we were assuming someone else was “handling something” and when we thought we were.
- Next project we will go back to basics and insist on a session where we sit down and explain our roles and responsibilities to each other and then debate them.

We have already had improvements in less that a week. It was so simple that I am wondering if it is worth creating a one day course that covers nothing more than delegation, follow up and expectation setting. Would you come to a course like that or is it something you already know and do?

Posted in Consulting, Reflection | 1 Comment »

Why do the good project managers doubt themselves?

Posted by James King on September 13, 2009

I was coaching a project manager last week and we worked through several of the issues he is facing.

He was probably hoping that there were some cool new Lean or Agile tools that he could use to deal with some seemingly really difficult problems.  In fact I always hope the same thing – it makes coaching and work easier.

Sadly, and predictably, he didn’t need cool new techniques.  He was already applying common sense, accountability and a real focus on getting the best outcome for the project (best for the team, the organisation and the customer).  He was also treating people like people, risks like risks and even status reports as a way of communicating status.

Yet he was still struggling.

As we worked through his issues a couple of things came out of the conversation.  He noted that he rarely gets time to sit and reflect on the project because it is too important and too urgent.  He also noted that if it is so importantly maybe he does need time to think.

But for me what came out was the crystalisation of a pattern I was vaguely aware of.

Most good project managers struggle.

  • They start out runing small projects successfully;
  • So they get bigger and harder projects; and then
  • Eventually they either get blown up or find a sustainable rhythm between nightmare project (that they often seem to want every third project) and cruisy project (that they need every third or more projects but rapidly get bored with)

Now if they blow up, they often give up or get shunted out because they failed or struggled with something really hard.  But ironically this is exactly when they can learn to be a great project manager for future projects.  I often say I won’t hire project managers who have no scars because they need to learn from the struggles of being out of their depth or making mistakes, but I would rather someone else pay for that part of their education.

Also ironically, the good project managers seem, like the one I was coaching, to feel apologetic about struggling with really difficult projects.  They seem to feel that if they were better and more experienced the project would not have been such a struggle.

This is proabably true, but then we usually don’t know until half way through what a project will be like. So is is hard to avoid being a project manager and being in trouble.

On the other hand there are also many “sub-optimal” project managers who never feel apologetic.  Sometimes they choose easy projects, usually they ask for far more time, money and resources than a better project manager would need and still struggle to deliver, and every project they blame all problems on the complexity of the project  and claim they did an amazing job simply because the project was always in trouble and they were there to rescue it.

So it seems to be the project managers who doubt themselves that become better project managers, while the ones who blame the complexity of the project and the “dumb” stakeholders who fail to learn and yet costing their projects a lot of money for having the same problems they should have learned to avoid last project.

Posted in Observations, Reflection | 2 Comments »

On reflection

Posted by James King on September 12, 2009

Action without reflection soon turns into panic, yet I don’t know anybody who has serious time to reflect each day at work.

For example, I know of several teams who run small iterations on IT projects and still haven’t had time to sit down and think through how they plan their releases.  So in addition to having the team properly trained, I now run a training game called The Agile Release Planning Game.

The game helps people to experience the process of planning releases and iterations without getting caught up in the detail of their own projects.  So let me know  if you would like me to run the game, or would like to purchase a copy to run for your own teams and customers.

Back in the real world, I facilitate post implementation reviews for projects and post incident reviews for teams who have recently responded to a major incident.

More generally, I provide coaching to individuals in how to better deliver their projects, lift their performance or make the transition to a new (or growing) role.

I also provide workshops and coaching for teams in the areas of process and business consulting, business analsyis and effective project delivery.

You can also call me on +61 4 21 058 459, or email me at james@kingsinsight.com

Posted in Reflection | Leave a Comment »