Following on from my last blog “Which Project Manager Do I Hire?” I thought I’d give a couple of examples of what can (and often does) happen when hiring managers only hire PMs who have managed similar projects or worked within a rival organisation, rather than choose the best “Project Manager”.
My question:
They might have managed exactly the same project for a different company, but is this a guarantee that this person is actually a good project manager who will deliver the project within time, scope and budget?
Scenario 1:
A PM who has the relevant experience / knowledge, but who isn’t necessarily a good Project Manager.
This person understands all the detail and subject matter and is able to quickly get up and running, however they make all the same mistakes that they made in their last project (that was delivered late and over budget). They can’t keep track of the costs effectively, they can’t manage / motivate their team to ensure that crucial timescales are met, they don’t know how to make (yet alone follow) a good project plan, they have poor stakeholder management skills. So the project is in turmoil, the project sponsor is unhappy. This PM has managed a similar project before and has good knowledge of the subject matter but they can’t actually manage a project effectively, or ensure that it gets delivered as and when the sponsor requires it to be.
Scenario 2:
A proven delivery focused PM who hasn’t got the relevant knowledge of the technologies / project details.
This PM has a steeper learning curve, trying to understand the technologies and project details, and will take more time getting up-to-speed with the project. This isn’t ideal, however this PM has been here many times, and is quickly able to get an understanding of the detail of the project by establishing good relationships with his technical staff / subject matter experts and utilising their knowledge.
As soon as they are up-to-speed with the detail, this PM quickly establishes control of the project, following the usual steps they use to ensure that the project runs smoothly, keeping costs on-track, appeasing stakeholders, managing expectations and managing risks and other issues. This PM uses his technical experts as trusted advisors and doesn’t get bogged down with the detail, meaning the PM has more time to spend actually managing the project, which in turn ensures the project has a much better chance of being delivered on-time and within budget.
Clearly, I think all hiring managers / project sponsors would prefer the outcome in the 2nd scenario, so why is it so often the case that they plump for scenario 1?















Posted on May 28, 2010 by Chris
Probably more of an issue with a poor recruitment process. Sounds like the recruiter hasn’t run through an interview or reference process that would get to the bottom of how successful the candidate had been in the past, or their responses/actions when facing particularly challenging scenarios. Combine this with the issue that quite a few organisations I’ve met recently don’t really understand best practice project management, and the fear of doing something different and going outside the industry and you get the scenario you’ve described.