PMO & delivery · 31 October 2026 · 3 min read
Before you hire a PMO Manager, agree which decisions they can influence
Hiring a PMO Manager? Define their remit, decision rights and responsibilities before choosing the title or writing the job advert.
You are preparing a PMO Manager brief. The responsibilities include governance, reporting, risks, dependencies and stakeholder management.
It sounds familiar. It may still leave the most important question unanswered:
What will this person be able to influence when they find a problem?
A PMO can have a broad strategic remit or a more focused delivery-support role. Either can be appropriate. The difficulty comes when the job description promises one and the organisation expects the other.
Start with the situation the person will face
Consider a hypothetical programme. Two projects need the same technical team. Both sponsors say their deadline is essential. The resource conflict appears in the programme report every week.
What should the PMO Manager do?
They might document the conflict, prepare options for a decision forum, challenge the assumptions behind the deadlines or make a recommendation about priorities. They might have authority to change the plan within agreed limits.
Those are different levels of responsibility. They call for different experience and support.
A hiring brief should explain which of them applies.
Separate preparing a decision from making one
For each major responsibility, distinguish the work the PMO performs from the decision someone else owns.
For example:
- The PMO gathers capacity information; a named leader agrees resource priorities.
- The PMO makes dependencies visible; delivery owners agree the response.
- The PMO consolidates benefits information; business owners remain accountable for the benefits assigned to them.
Your arrangement may be different. The useful step is to make it explicit.
If a role is expected to challenge senior stakeholders, identify the sponsor who will support that challenge and the route for unresolved issues.
Describe the work behind the reporting
“Produce a weekly dashboard” describes an output.
Explain what the dashboard is for. Which decisions should it support? Who reads it? What happens when it identifies a risk that cannot be resolved within the delivery team?
The answer helps distinguish a reporting-heavy role from one that requires stronger programme analysis, facilitation or portfolio experience.
It also gives candidates a more accurate picture of the job.
Use the interview to explore judgment
Ask candidates to work through a short, realistic situation drawn from the role. Use an invented scenario rather than asking them to solve a live business problem for free.
You could ask:
- What information would you need before escalating this dependency?
- How would you present options when two sponsors disagree?
- What would you do if a report stayed green but the underlying evidence was incomplete?
- How would you explain the limits of your authority without leaving the issue unresolved?
Listen for the reasoning, the questions they ask and their understanding of accountability. A polished template on its own tells you less.
Write a brief both sides can use
Before publishing, complete these sentences:
- This role exists because…
- The person will be responsible for…
- They can decide…
- They can recommend or escalate…
- Their sponsor will…
- We will assess their contribution through…
If the hiring team gives different answers, resolve that discussion before interviewing.
The title can stay PMO Manager. What matters is that the remit, authority and expectations belong to the same job.
Hiring, or ready for your next move?
Tell us about the work, the team and the skills you need, or explore roles that match what matters to you.
