Sunday, September 6, 2009
Risky Business
The question is… “Tell me a bit about how you approach risk on a project.”
The junior project manager will tell you about their risk register. How they fill it out at the beginning of the project, give everything a rating, list a mitigation for every risk and maybe a bit about how they cut and paste the register into the steering committee report every fortnight. If you took a peek at one of these risk registers you would see entries like: “Risk that resources won’t have the required skills”, or “Risk that hardware won’t be delivered in time” or even (and this is a real one I’ve seen) “Risk that application won’t work in production”.
The experienced project leader will give you an altogether different answer. They might mention their risk register in passing, but what they’ll mainly tell you about is how they use risk to maximise the output of the project. They’ll talk about how they are taking one particular risk in order to mitigate another (e.g. not involving a difficult stakeholder in every meeting so that they don’t create trouble and disrupt progress). And how they are balancing a risk finely to increase the productivity of the team (e.g. regularly changing a team member’s role on the project team depending on requirements).
They also aren’t distracted by attempting to mitigate risks that are standard on every project (e.g. “Risk that illness will impact the schedule”), because they are always closely involved with the project and will deal with these issues if and when they arise.
If you were to ask one of these project managers to tell you about the risks on their project, they’ll be able to recite the big ones off from memory – starting with the ones that they are currently watching on a daily basis. They don’t wait for a steering committee meeting to tell their sponsor and stakeholders about changes to the risk profile of the project; they actively and regularly keep them informed.
Most importantly, they aren’t frightened by risk. They use risk, rather than being controlled by it.
Saturday, August 29, 2009
#Fail
But what do you do as the project manager when one of your decisions turns out to be a bad one? When you make a call that is later obviously a mistake?
Well firstly, you should apologise to the team. Properly. And with sincerity. Chances are someone else is going to suffer more than you will from your bad decision.
Then you should quickly move on to making things better.
Sometimes, this is easy. You can just reverse your decision and go back to the way things were. Or there was a clear ‘other’ choice so you can now give that a go. But sometimes it’s not that simple. It might now be too late to change your mind, either because too much time or money has been sunk into a particular path or because it just doesn’t make sense to make more change.
Those are the times when leadership skills come in handy. If life has been made more painful for the team, then you need to put a lid on any recriminations or complaining that ensues. Explain why the decision has been made, allow the team to vent – and then set the expectation that there is no going back over old ground again and again. Actually, this applies no matter why a team finds itself in the position of having to continue on a path that is less than ideal. But it is particularly important when there is the additional emotional baggage of someone in the team having made a ‘mistake’.
There is no easy answer to dealing with decisions that turn out to be bad ones. But the one thing you can be sure of as a project manager is that you’re going to have to do it. The only way to avoid it would be to never take any risks or make any finely balanced decisions – and if you do that, you have no hope of ever delivering a project on time and within budget.
Tuesday, August 25, 2009
Over Sharing
I have been given feedback on a number of occasions that people like working with me because I keep the team informed of what is going on. I have also received feedback that I am telling people too much and worrying them unnecessarily – although interestingly this has only ever come from observers peripherally involved in the project, never from a core team member.
My instinct has always been to err on the side of ‘over communication’. If you’re going to take a risk, I think it is better to risk saying too much and potentially overwhelming the team. The alternative is that you risk not telling them something that they need to know.
I think this is particularly important in a ‘difficult’ project situation. The more the team know in those circumstances, the more empowered they feel. This can help them to help themselves, and also to feel more in control of the problems.
I suppose the thing to weigh up is what the damage is that can be done by telling the team something that they might not ‘need’ to know. In most situations, the worst case is that you have to do a bit of hand-holding with some of the team to address their concerns. If you have a properly functioning and cohesive team, they will tend to support each other through any uncertainty and not place too much emphasis on it. If your team is still in the ‘storming’ phase, then perhaps you might want to be more cautious, but even then you could be doing more harm than good by keeping them in the dark.
One thing that is worth noting is that it can make a difference how you communicate. If there is a worrying situation developing, present it to the team as something that you are looking after but feel they should be aware of. Avoid the temptation to make it their problem too.
So I say go for it. Tell your team what’s going on. You might even find that it lightens the burden of some of the exterior pressures.
Sunday, August 23, 2009
Why does your team follow you?
I’ve recently been thinking a lot about what makes a good team leader. What is the difference between a leader who people like to work with and one who they dread?
One answer is whether or not you care about your people - do you care what they think of you?
When recently I first took over a role managing a large group of people, a number of people cautioned me that I might find it difficult because I ‘like to be liked’. I see where they are coming from – if you are too concerned about people being your friend, you may have trouble making tough decisions because of the risk you will upset people.
But in fact, I think wanting people to like you is a good thing in a leader. It means that you are thinking about their feelings when you make decisions. In trying not to upset people, you are in fact considering them as individuals and therefore more likely to minimise the impact on them. At the very least, it encourages you to communicate difficult news with compassion and empathy.
If you don’t care about the people in your team, you are more likely to make decisions based on other factors such as cost or convenience. While this might not be a big deal a lot of the time, happy people are productive people so any gains you make could well be quickly lost.
Thinking through the impact of decisions on people and then taking the time to communicate personally is the best way to make them feel an important and valued member of the team.
So yes, I do care if you like me or not.