Sunday, September 6, 2009

Risky Business

I have a ‘killer question’ that I use in Project Manager interviews to gauge how senior a PM is or, if you like, whether they are a project manager or project leader.

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.

No comments:

Post a Comment