Asking the PMO for facts about the portfolio is good practice. Asking it to settle what an initiative is for, which of two should win, or what to stop is something else: it hands the sponsor role to a function with neither the knowledge nor the mandate to decide.
A PMO can supply the facts a portfolio decision needs, but sponsorship, meaning ownership of what an initiative is for and which trade-offs it wins, must stay with a named executive, because no PMO holds the mandate to decide. Most organisations meet this pattern at a hopeful moment. The PMO has just done something genuinely useful: it has put every so-called project on one table, where the leadership team can see it all at once. The table provokes exactly the right questions. Then some of those questions travel to the wrong address, and sponsorship quietly moves to a function that cannot hold it.
Putting every “project” on the table is the PMO’s most valuable early act
The first full inventory of an organisation’s work is rarely a pleasant document. It is longer than anyone expected, and not everything on it is a project. Some entries have no sponsor. Others have two. Several solve the same problem from different departments, each unaware of the others.
None of this is really the PMO’s discovery. The work existed before; it was simply scattered across departmental lists, spreadsheets and people’s heads. What the PMO adds is a single view, built on one set of definitions, that nobody can dismiss as partial.
That first table is also where the lines that are not projects at all become visible. It shows, in one page, what an organisation accumulates when nothing decides what enters the portfolio.
A complete table provokes better questions than any report
Something changes in the room when everyone can see the full list. Managers who have only ever defended their own initiatives start reading everyone else’s. The questions arrive almost on their own.
Why are three teams working on the same customer problem? Who decided to start this one, and is that person still here? What would happen if we stopped it next month? Which of these would we approve today, knowing what we know now?
These are the most valuable questions an organisation can ask about its own work. Most of them could not be asked before, because nobody could see enough of the picture to form them. A status report answers the questions its authors anticipated. A complete table raises questions nobody anticipated, and those lead to decisions.
This is also the moment sponsorship starts to wake up. An executive who sees their initiative next to a competing one, both drawing on the same scarce engineers, suddenly has something to decide. Visibility does not create accountability on its own. It does remove the comfortable fog in which nobody had to exercise it.
The trouble starts when an answer is treated as a decision
Here the pattern turns. The executive who has just read the table sends questions on scope, overlap and priority to the PMO. Often that is exactly right. The PMO holds the data, and an executive who wants to understand an overlap before discussing it should ask for the facts.
The problem begins when the question is not “what do we know?” but “what should we do?”. What is this initiative actually for? Which of these two should continue? Can we stop this one? A PMO can analyse those questions and even recommend an answer. Unless it holds an explicit mandate for that kind of decision, it cannot settle them. When the executive treats its reply as the settlement, nobody with the authority to decide has decided anything.
Who is asking matters too. An executive asking about someone else’s initiative has a simple better route: its sponsor. An executive asking the PMO what their own initiative is for has a harder problem. That executive is the sponsor, and the question is theirs to answer.
Every portfolio question already has a named address
PMI’s portfolio standard distinguishes the roles involved: sponsors, a portfolio manager, a portfolio governance body, the PMO, and the programme and project managers who run the work. Read together, that separation suggests a simple discipline: route each kind of question to the role able to answer it.
A question about scope belongs to the sponsor, who answers for the business case, working with the project or programme manager, who knows what the work actually contains. A question about overlap belongs to the sponsors of both initiatives. Where they cannot agree, it moves up to the portfolio governance body. A question about priority belongs to that body from the start, because choosing between initiatives is the defining act of portfolio management.
The portfolio manager, a role that in many organisations sits with the head of the PMO, prepares those choices. It analyses, compares initiatives against agreed criteria and recommends. That is a substantial contribution. It is still a recommendation, and the decision stays with the people who will answer for its consequences.
The PMO decides only what it has been mandated to decide
A PMO owns the portfolio process, not its content. It can show where two initiatives overlap in scope, budget or people, and flag which entries lack a business case, a sponsor or a finish date. Modelling what stopping one of them would free up, and saying which option the agreed criteria favour, is part of the same job. All of that is legitimate, and much of it is what made the table useful in the first place.
Some PMOs go further, and rightly so. A governance body can delegate real decisions to them: rejecting a proposal that fails the intake criteria, holding an initiative that misses a stage gate, moving people between initiatives within agreed limits. A PMO with that kind of written charter and mandate decides, and should. Its authority is borrowed from the body that delegated it, defined by limits, and visible to everyone it affects.
Even a well-mandated PMO, though, does not answer for the business case. It cannot explain to customers why the initiative they were promised was cancelled, and it does not carry the outcome the initiative was meant to deliver. Those consequences stay with the sponsor. So the test is not whether the PMO decides, but whether it decides within a mandate someone gave it. Under pressure from a direct question from an executive team member, that boundary is the first thing to blur.
Every settled question teaches the wrong routing
The uncomfortable part of this pattern concerns the PMO itself. When an executive asks a direct question, many PMO leaders don’t stop at a recommendation. They are capable, they have the data, and settling the matter feels like service.
Yet a PMO that decides a sponsor’s question on the sponsor’s behalf is not being helpful. It is quietly taking a decision nobody has given it.
Each such answer trains everyone involved. The executive learns that the PMO resolves portfolio questions. Sponsors learn they can stay out of the conversation about the work they answer for, and project managers learn that nobody will ask them. The PMO drifts from portfolio governance into portfolio authorship. Within a few months, whoever writes the summaries is effectively shaping the portfolio. It is the familiar trap of ownership without authority, with the PMO caught in the middle.
Visibility pays only when the table meets its sponsors
The fix is not to make the table less visible. It is to put the table, its sponsors and its project managers in the same room, regularly, with a governance body entitled to decide. The PMO’s job in that room is to prepare and convene, not to rule. It brings the overlaps, the gaps and the unsponsored entries, with its analysis and recommendations, and it makes sure each one leaves with a name and a date.
That requires a small shift in how the PMO handles incoming questions. When an executive asks what to do about two overlapping initiatives, the useful reply gives the facts, offers a recommendation, names both sponsors and proposes the decision for the next portfolio review. It turns “find out about this” into “decide between these options”, so the meeting decides rather than commissions more research. It also records what was decided, so the same question does not return next quarter in different words.
Some questions will find no sponsor at all. That is a finding in its own right. An entry nobody will sponsor is not a project in any governable sense; it is a label, a habit or someone else’s work. Converting it, closing it or moving it to a dependency list is often the first real portfolio decision an organisation takes.
Sponsorship is a modest job, but not an optional one
None of this asks executives to run projects. The sponsor role usually takes less time than executives fear, but it takes regular time, and it cannot take none.
The sponsor’s job, stage by stage, is a longer story. In practice, a sponsor does five things that nobody else in the structure can do for them:
- Answers for the business case. Why the work exists, what it should deliver to the business, and whether that still holds when circumstances change.
- Secures and protects resources. The budget and the people, including when other priorities start competing for them.
- Decides beyond the project manager’s limits. Scope, cost or timing changes that the project or programme manager is not entitled to approve alone.
- Resolves escalations. Conflicts and blockers that nobody below the sponsor can settle, and that are taken to the portfolio governance body when they cross into another sponsor’s work.
- Makes sure the result is used. Once the work is delivered, the benefits only arrive if the organisation actually adopts what it paid for.
Not every senior leader has that time for every initiative that carries their name. That is a fair constraint, not a failing. The answer, though, is not to route the role through the PMO. It is to sponsor fewer initiatives, or to hand sponsorship explicitly to someone with both the time and the authority to decide: named, announced and backed.
When a leadership team cannot find enough sponsorship time for its portfolio, the portfolio is telling it something. It is larger than the organisation can steer. Deciding what to drop is a portfolio decision too, and an executive is exactly the right person to take it.
Portfolio maturity is a routing measure
A simple test for any leadership team. For one month, note where the questions that need a decision actually end up: what an initiative is for, which one continues, what stops. If sponsors and the portfolio governance body settle them, with the PMO’s analysis in hand, the portfolio is being governed. If the PMO settles them, the sponsor role is vacant, whatever the governance documents say.
Maturity models measure processes, templates and tools. This test measures something harder to fake: whether the people with the authority to decide are the people actually deciding.
A mature portfolio is not one where the PMO knows every answer. It is one where nobody mistakes the PMO’s answer for the sponsor’s decision.