Project Manager: five mistakes when defining the role
Updated: Nov 3
"Project Manager" is one of the broadest job titles on the market. It is used by someone who coordinates the construction of a plant, by someone who runs a software team with Scrum and by someone who manages a PMO's project portfolio. If your job posting doesn't say which one you need, you will get candidates from all three.
And talent is scarce. According to PMI, there are almost 40 million project professionals in the world today, and up to 29.8 million more will be needed by 2035.
1. Using the title without saying what kind of projects
An IT Project Manager, a construction Project Manager and a software implementation Project Manager do very different jobs, and experience does not easily transfer from one industry to another. Say what projects the person will lead, how large they are and what kind of team they will work with.
2. Confusing Project Manager with Product Manager or Product Owner
A Project Manager delivers a project on time, in scope and on budget. A Product Manager decides what gets built and why. A Product Owner prioritizes the work of an agile team. If you combine all three into one role, you are describing a job almost nobody has done.
3. Asking for every certification
PMP, Scrum, PRINCE2, ITIL… A long list shrinks your candidate pool without telling you who will do the job well. A Harvard Business School study found that 67% of US job postings for production supervisors required a college degree, while only 16% of people already in that role had one. A degree is not a certification, but the pattern is the same: asking for requirements that even the people doing the job don't meet.
Ask for the certification the role actually needs, and explain why. For example, because a client requires it in the contract.
4. Not saying how much authority the role has
Will the person manage a budget? Does the team report to them directly, or do they coordinate people they don't manage? Those are two different jobs, and someone who has only done one may not succeed in the other.
5. Asking for a methodology the company doesn't use
If the company works with waterfall plans and long approval cycles, asking for "agile experience" attracts someone who will clash with how work gets done. Describe how the team works today, not how you would like it to work.
How we do it at Beethon
When possible, we meet the client's team before defining the profile. When that isn't possible, we study how the company presents itself: its website, its services and who it speaks to.
For some Project Manager searches we also design our own assessment. It combines technical cases from the client's industry (budgets, critical path, risk) with an internationally validated personality inventory. We review the key answers with the candidate in the interview.
Need a Project Manager? Tell us what projects they will lead at beethon.com.
Angel Rossio Millán
IT Headhunter | Master's in Human Resources Management, EAE Business School Barcelona
Sources




