Questions to Ask a PMO
For a project manager joining an organization, an executive sponsor, or a candidate for a PMO role who is sitting down with the head of the project management office to learn how it works. The questions follow the order that conversation tends to take: what the office governs and what it only advises on, how projects are chosen and staffed, the method and reporting it requires, how it measures its own value, and what it needs from you.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Remit
What is the PMO's role in this organization, in a sentence or two?
Why ask it
Some offices only support, with templates and coaching. Some set standards and check that projects follow them, and some run the projects with their own managers. A good answer picks one and gives an example from last month; a list of every possible function usually means the remit was never settled.
Which decisions does the PMO make, and which does it only advise on?
Why ask it
Ask for one decision of each kind, such as approving a change to a deadline against recommending one. If everything turns out to be advice, the real authority sits with a steering group or a department head, and that is who you will need to convince.
Who does the head of the PMO report to, and who sponsors the office?
Why ask it
The reporting line tells you how far the office's word carries. One that answers to the chief executive or a strategy lead can usually hold a line across departments, while one inside IT or finance tends to be read as that department's project office. Neither is wrong, but it sets what the office can ask of people elsewhere.
Which projects come under the PMO, and which run outside it?
Why ask it
Many offices draw a line by cost, length or risk, and a body of work quietly sits beyond it. Ask what the line is and who decides when a piece of work is close to it. The more delivery happens outside the office, the less of the picture its portfolio report shows.
Do project managers report to the PMO, or to their own departments?
Why ask it
If they report in, the office hires, assigns and reviews them, and the standards come with the job. Where they sit in the departments, the office has to persuade, and a project manager can end up with two sets of expectations. If you are joining as one, ask who writes your review.
How many people work in the PMO, and what does each of them do?
Why ask it
The headcount sets what the office can realistically take on: two people cannot run intake, check every status report and coach sponsors as well. Ask which roles are analysts, which are project managers and which are vacant. For a candidate, the gaps in that list are usually the job.
Why was the PMO set up, and is that still its main job?
Why ask it
Offices are often created after something specific: a failed project, an audit finding, a new executive. The founding problem explains rules that otherwise look arbitrary. Whether it is still around tells you if the office is solving something or looking for its next job.
Can the PMO pause or stop a project, and when did it last do so?
Why ask it
The honest answer is often that it can recommend and a steering group decides. Either way, ask for the last case. An office that cannot recall a single project being halted may be reporting on the portfolio more than governing it.
Is this the only PMO, or are there others at department or program level?
Why ask it
Larger organizations often have several, and the trouble starts where they overlap: two templates, two reports, two views of which office has the final word. Ask whose standards win when they differ, and which office a project of yours would answer to.
What do people bring to the PMO that is not its job?
Why ask it
The answer shows how the rest of the organization sees the office: as a help desk for project tools, a place to send work nobody wants, or the group that says no. It is also a quick list of things not to ask the office for yourself.
Priorities
How does an idea become an approved project here?
Why ask it
Have them walk through the steps from first request to kickoff, with the form or business case required at each and how long the whole thing normally takes. Gaps in the account, such as 'then it gets approved', are where projects come in by the side door.
Who approves a new project, and what criteria is it scored against?
Why ask it
Listen for a named group and written criteria, such as strategic fit, cost, risk and expected benefit. 'Leadership decides', with no scoring behind it, often means the most persistent sponsor wins, which is useful to know if you sponsor a quieter project.
When there is not enough capacity for everything approved, how are projects ranked?
Why ask it
A ranked list means somebody has done the hard work of saying which project loses. If every project is a top priority, the ranking happens anyway, later, when a shared team decides whose work to do first. Ask to see where your project sits.
How many projects are active right now, and how many is the organization staffed for?
Why ask it
Two numbers, and the gap between them matters more than either one. A head of office who knows both is managing a portfolio. Where the second has never been worked out, expect people split across too many projects and dates that slip together.
How does the PMO know who is free to work on a project, and how far ahead?
Why ask it
Capacity planning is the part many offices find hardest, so a candid answer may be 'a spreadsheet and a lot of phone calls'. What you want to learn is whether named people are committed to your project before a date is promised, or found afterwards.
Who settles it when two projects have been promised the same specialist for the same month?
Why ask it
It should be someone above both projects with the ranking in hand. If the two project managers are left to negotiate, the outcome depends on who asks first or who knows the specialist's manager. Find out before you are one of the two.
How does urgent, unplanned work get into the portfolio, and what gives way for it?
Why ask it
Most organizations have a fast lane for a regulator's deadline or an executive's request. What you want is the name of the project that was delayed last time to make room. If nothing ever gives way, the cost is being paid in overtime and quality.
Where does project funding come from: a central budget the PMO manages, or each department's own?
Why ask it
Central funding gives the office real say over what starts and stops. With department funding, the executive who pays can often proceed whatever the office thinks. Ask as well who can release extra money mid-project, since the arrangement differs a great deal from one employer to the next.
How often is the whole portfolio reviewed, and what changed at the last review?
Why ask it
A review that only ever adds projects is a meeting, not a decision. Listen for something that was cut, deferred or given more people, and why: that is the reasoning you would face if your own project came up.
Method
Which delivery method does the PMO require, and how much can a team adapt it?
Why ask it
Expect to hear a named approach, such as a stage-gate model, a Scrum-based one or a house blend. For a working project manager the room to adapt counts for more, so ask for an example of a team that did it differently with the office's blessing.
Which documents does every project have to produce, and which depend on its size?
Why ask it
Ask for the actual list: charter, plan, risk register, status report, closure report or whatever they call them there. A short mandatory core with extras for large projects suggests someone has counted the cost. If a three-week project needs the same pack as a three-year one, people will fill in forms without reading them.
How does the PMO sort projects by size or risk, and what changes at each level?
Why ask it
Tiering decides how much oversight you get, so ask what tier a project like yours would land in and who assigns it. Watch for criteria that can be gamed, such as a cost threshold that work gets split up to stay under.
What are the stage gates, and who signs off at each one?
Why ask it
You want the gates in order, the evidence each one needs and who can say no. Then ask how often a project fails a gate. Gates that everything passes cost time without filtering anything.
How does the PMO work with teams that run Agile?
Why ask it
The friction is usually over fixed-scope business cases, percent-complete reporting and gates designed for a plan-first project. A thoughtful office can say what it asks of those teams instead, such as a roadmap and a regular demo. 'They follow the same process' is the reply to probe.
Which tool holds the plans and the portfolio, and who keeps it up to date?
Why ask it
The name of the system matters less than who feeds it. Where project managers update it weekly because they rely on it themselves, the data can be trusted. An office that re-keys figures from slides and spreadsheets is showing you a portfolio view a week or two behind.
How does a project manager get an exception to the standard process?
Why ask it
A defined route, with a named person who can say yes inside a few days, shows the office treats its process as a default and not a law. Without one, people skip steps quietly, and the office loses sight of exactly the projects under the most pressure.
When did the PMO last remove a template, a meeting or a step?
Why ask it
Process tends to pile up, because each rule answers some past failure and nobody is asked to retire it. A recent, specific example of something taken away suggests the office listens to the people doing the work. A long pause here is an answer too.
What training or coaching does the PMO give project managers and sponsors?
Why ask it
Some offices run onboarding, a community of practice and one-to-one coaching; others only publish the templates. Sponsors are the group most easily left out, so ask specifically what a new sponsor is told about the role.
Where do lessons from finished projects go, and who reads them before the next one starts?
Why ask it
Collecting lessons is easy and using them is not. Ask for a change to a template, a checklist or an estimate that came out of a past review. If closure reports go into a folder nobody opens, that is worth knowing before you spend a day writing one.
Reporting
What does every project report to the PMO, and how often?
Why ask it
Get the specifics: the form, the day it is due, the fields and where it goes next. For a project manager this is a fixture in every week or month, so ask to see a completed example and judge whether you would learn anything from reading it.
Who sets a project's red, amber or green status: the project manager or the PMO?
Why ask it
Where the project manager chooses the color, reports tend to stay green until the last moment. Written thresholds, such as a set slip in the schedule or the budget, take some of the judgment and the politics out of it. Ask what the thresholds are and whether the office can override a rating.
What happens in the week after a project turns red?
Why ask it
In a healthy setup, red brings help: a sponsor's attention, a decision that was stuck, an extra pair of hands. In an unhealthy one it brings more reporting and a meeting to explain yourself. The answer predicts how early the project managers around you will admit trouble.
Who reads the portfolio report, and what did it last cause them to decide?
Why ask it
A report earns its cost when someone acts on it, by moving people, releasing money or stopping something. A head of office who cannot name a decision that came out of it is producing the report for the record, and the effort that feeds it deserves a second look.
How does the PMO check that a status report matches what is really going on?
Why ask it
Possible answers include health checks, sitting in on team meetings, comparing reported progress with what has been delivered, or an independent review of the biggest projects. With no checking at all, the portfolio view is only as candid as its least candid project manager.
Which risks does the PMO watch across the whole portfolio, beyond each project's own register?
Why ask it
The ones worth an office's time are those no single project manager can see: several projects leaning on one supplier, one team or the same go-live weekend. Ask who looks at the combined picture and how a risk on your project would reach it. An office that only files the registers has left the watching to each project.
How are dependencies between projects tracked, and who owns one that crosses departments?
Why ask it
This is work only an office above the projects can do, since each project manager sees just their own end of the link. Ask where the dependencies are written down and what happened the last time one project's delay hit another.
Once a project is under way, how does a change to its scope, date or budget get approved?
Why ask it
Ask what size of change the project manager and sponsor can agree between themselves, what has to go to a board, and how long the board takes. Slow change control breeds unofficial changes, so the turnaround time is as important as the rule.
When a problem is escalated through the PMO, where does it go and how fast does an answer come back?
Why ask it
Trace one real escalation from the project manager to the person who decided it. Days are fine and weeks are a warning, because a project manager who waits a month for a ruling learns to stop asking.
How many hours a month does PMO reporting take a project manager?
Why ask it
An office that has measured this, or at least asked, is treating its own process as a cost. If the figure surprises them when you estimate it together, you have found a useful first conversation to have once you start.
Value
How does the PMO measure its own performance?
Why ask it
Weak measures count the office's activity: reports issued, templates published, people trained. Stronger ones follow the portfolio: delivery against the dates and budgets that were approved, forecast accuracy, how long a decision takes. Ask which figures go to the executives and how they have moved.
What is the hardest problem the PMO is dealing with right now?
Why ask it
Common ones are figures nobody trusts, sponsors who go around the process and more approved work than people to do it. Ask what has been tried so far. A candidate would inherit the problem, and a project manager would be working inside it from the first week.
Does anyone check, after a project closes, whether it delivered the benefits in its business case?
Why ask it
Often the answer is no, because the team has disbanded and the sponsor has moved on. If the office does track benefits, ask who owns each one after handover and how long the tracking runs. If it does not, business cases there can promise freely.
What would the executives say the PMO is worth to them?
Why ask it
You are asking for the customers' view, not the office's own. A confident head of office can quote what a particular executive relies on it for, such as one honest picture of the portfolio before budget season. A vague answer may mean nobody has asked them.
What do project managers complain about most when it comes to the PMO?
Why ask it
Anyone running such an office has heard the complaints: too many forms, reports nobody reads, late changes to the rules. Naming them without getting defensive, and saying what was done about one, is a strong sign. 'They are generally happy' tells you less than a grievance would.
What is better about project delivery since the PMO started, and how do you know?
Why ask it
Look for a before and after with some evidence behind it, even rough: fewer surprises at the steering group, earlier warnings, a shorter approval cycle. Be wary of improvements that cannot be told apart from the organization simply getting more practiced.
If the PMO closed tomorrow, what would stop working within a month?
Why ask it
A sharp way to separate what the office does from what it oversees. Good answers are concrete, such as nobody arbitrating shared staff or no single list of what is in flight. If the main loss would be the reports, that is the office's weak spot and probably its next piece of work.
What is the PMO trying to change about itself over the next year?
Why ask it
Plans might include moving from project to portfolio reporting, taking on benefits tracking, replacing a tool or adding Agile coaching. For a candidate, this is the work you would be hired into. For a sponsor or project manager, it is advance notice of which rules are about to move.
Working together
What do you need from a project manager in their first month?
Why ask it
Expect practical items: tool access and training, the reporting calendar, an introduction to the sponsor, a baseline plan by a set date. Write the list down and ask which item new arrivals most often miss.
What can a project manager or sponsor ask the PMO for, beyond the templates?
Why ask it
Examples might be someone to run a kickoff or a risk workshop, a planner's time on a schedule, an independent health check or cover while a project manager is away. Find out how to request each one and whether the cost lands on the project. Offices differ widely on this, and help that nobody knows to ask for goes unused.
What does the PMO expect of an executive sponsor?
Why ask it
For a sponsor, this defines the commitment: how many hours a month, which meetings, which decisions are yours alone. For a project manager, it tells you what you can fairly ask of yours. If the expectation is not written anywhere, ask what the office does when a sponsor stops turning up.
Who in the PMO do I call when a project is heading for trouble, before it shows in a report?
Why ask it
You are after a name, and a sense of whether an early, informal warning is welcomed or held against you. An office that offers a quiet word before the formal status changes is likely to hear bad news sooner.
Which current project shows the process working well, and could I see its documents?
Why ask it
A real charter, plan and status report teach the house style faster than any template. Notice how quickly an example comes to mind, and ask afterwards what made that project go smoothly: the process, the sponsor or the team.
If I joined the PMO, what would you want me to own by the end of six months?
Why ask it
This one is for candidates. A clear answer, such as the monthly portfolio report or the intake process, means the role has a shape. 'A bit of everything' is fine in a small office, but ask which part you would be judged on at your first review.
How to get straight answers from a PMO
Practical guidance for the conversation itself
Before the meeting
Know which seat you are in
A project manager joining the organization needs Method, Reporting and Working together most, because those set the shape of the week. An executive sponsor gets more from Priorities and Value: how a project wins its place and what the office will hold the sponsor to. A candidate for a job in the office should lean on Remit and Value, which show how much authority and how much goodwill the team has to work with.
Read what the office has published
Many offices keep an intranet page, a process chart and a set of templates. Read them first, then ask about what they leave out. 'The charter template has a benefits section. Who looks at it after approval?' gets further than asking whether there is a charter.
Bring one real project
Have a specific piece of work in mind: the project you are inheriting, the one you sponsor, or one from your last job. Asking what tier it would fall in, which gates it would pass and whose staff it would compete for turns a description of the process into an account of what would happen to you.
Choose eight to ten and put Remit first
An hour with follow-ups covers perhaps eight to ten questions. Start with two from Remit, since whether the office decides or advises changes how every later answer should be read, then take the ones that would change what you do next month.
In the conversation
Ask when it last happened
'We can stop a project' is a policy. 'We paused the warehouse rollout in the spring' is a fact. Most questions under Priorities and Reporting get a truer answer when you add 'when did that last happen?' to the end.
Ask to see the thing itself
A ranked portfolio list, a completed status report, a gate checklist: each settles in a minute what a description leaves vague. If a document cannot be shared, ask for it to be described field by field. If it does not exist, you have your answer.
Say why you want the harder ones
Questions about complaints, the office's own measures or what would be missed if it closed can sound like a challenge to its existence. A line of context helps: 'I will be explaining the PMO to my team, so I want to give them the candid version.'
Take the calendar away with you
Before you leave, get the dates that will govern your work: when reports are due, when the portfolio is reviewed, when the gate board sits. These are the easiest answers to collect and the ones you will use first.
Reading the answers
Listen to the verbs
'We recommend', 'we facilitate' and 'we encourage' describe an advisory office, whatever the organization chart says. 'We approve', 'we assign' and 'we stop' describe one that governs. Neither kind is better in itself, but you need to know which you are dealing with before you rely on it to settle a dispute.
Compare the process described with the process followed
Put two or three of the same questions to a project manager who has been there a year. The head of the office describes the design. The project manager describes what gets enforced, what gets skipped and what nobody has checked in months.
Allow for the age of the office
A PMO in its first year will not have benefits tracking or a measured view of capacity, and that is not a failing. Judge a young office by whether its head can say what is missing and in what order it will be built. An older one should be able to show what it has stopped doing.
Notice who the office thinks it works for
Some heads of office talk mostly about what the executives need to see, others about what makes delivery easier for teams. A good office serves both. One that only ever mentions one audience will feel, to the other, like either a reporting burden or a group with no backing.
Mistakes to avoid
Running the meeting as an audit
You will be working with these people, and they decide how much help a struggling project gets. Ask out of curiosity, share what worked where you were before only if invited, and save your verdict for later.
Asking only about templates
Forms are the visible part of a PMO and the least important. A conversation that never leaves Method misses who decides what gets funded, who breaks a tie over staff and what happens when a project is in trouble.
Assuming it works like the last one
Gate, tier, portfolio, steering group and even the letters PMO mean different things from one employer to the next. Ask how each works there before using the word as if you already knew.
Leaving without a name
The most useful thing to carry out of the room is the person to call when something goes wrong between reports. If you did not get one, the question under Working together is worth a follow-up email.