When board packs, decision follow-through, cross-functional consolidation and executive-cadence design all land on the PMO, the organisation is running a chief-of-staff function. It has simply never named it.
Across a run of engagements, the same drift shows up in organisations of very different sizes. A “PMO manager” is hired to run the portfolio: intake, prioritisation, review cadence, delivery visibility. Within a few months, the job has quietly become a chief of staff role in all but name. The title on the org chart has not changed. The calendar tells a different story.
Nobody restructures the job description when this happens. Nothing about it looks like a restructuring. Each new duty arrives as a favour, an emergency, or simply the obvious person to ask. The org chart still says PMO. The actual week says something else, and it says it long before anyone writes it down.
The work arrives one reasonable request at a time
Nobody hands over a chief-of-staff mandate in a single meeting. It accumulates. The board pack goes to the PMO because the PMO already touches every workstream’s numbers. Somebody has to assemble it by Thursday. Chasing an overdue decision goes to the PMO because it already knows who owes what, and since when. Cross-functional consolidation goes to the PMO because it is the one seat in the building that already talks to every function. Executive-cadence design goes to the PMO too — which meeting happens when, with whom, on what evidence. It already owns the governance calendar, so it seems the obvious owner for this as well.
Each addition is defensible on its own. None of them is portfolio governance. Add enough of them together, though, and something shifts. A function built to run intake, prioritisation and delivery visibility starts spending most of its week on somebody else’s decision agenda instead.
The tell, seen more than once, is a PMO manager’s calendar: more one-to-one slots with the sponsor than portfolio review slots. The portfolio still exists. It is simply nobody’s main job any more.
The portfolio does not sit still while this happens. The intake gate is usually the first casualty. Whoever the PMO is currently helping gets heard first, and prioritisation quietly reverts to proximity rather than evidence. Nobody decided to weaken the gate. The person meant to hold it was simply in the sponsor’s office.
A chief of staff extends one person’s authority
A chief of staff exists to serve a principal — a CEO, a divisional head, whoever sits at the centre of the decisions in question. The role is decision support, follow-through on commitments, and coordination across functions, carried out in the principal’s name. Some of that follow-through happens in rooms the CoS never entered.
The defining feature is not proximity to information. A good PMO has plenty of that too. It is delegated authority. A chief of staff can close a decision, chase a commitment, or represent a position on the principal’s behalf. They do not check back for permission each time.
It is not a well-run executive assistant, either
The confusion runs in both directions, and the executive assistant deserves better than either version of it. A strong EA manages a principal’s time, correspondence, travel and meeting preparation. It is demanding work that rewards judgement, discretion, and an accurate memory for who said what to whom. What it does not carry, by design, is authority to act in the principal’s name when the principal is absent. An EA protects access to the principal. A chief of staff extends the principal’s reach past the room the principal is not currently in.
One test separates the two, and it is uncomfortable to apply. Can this person close a decision on the principal’s behalf, today, without asking first? If the honest answer is no, the role is EA-shaped, whatever the title says.
Ignore the test and two failure patterns follow. In the first, an EA quietly absorbs chief-of-staff-shaped work: chasing decisions, brokering between functions that will not otherwise speak. Nobody gives them the standing to make any of it stick, and they burn out carrying authority nobody granted. In the second, the organisation runs the pattern in reverse. It calls a genuine chief-of-staff job “a very good EA,” specifically to avoid naming and mandating it. That second pattern is the title-versus-mandate problem this site keeps returning to, wearing a different coat.
A PMO governs a portfolio; a chief of staff serves a principal
Put the two functions side by side and the boundary is clean, even where the daily traffic between them is not. A PMO is accountable for a body of work — the portfolio — on behalf of stakeholders with no particular loyalty to one another. A chief of staff is accountable to one person’s decision agenda.
PMI’s own 2025 rework of its PMO guidance frames the function as a service provider, organised around strategy, capability and delivery services. None of those services is “attend to one executive’s backlog of unresolved decisions.”
Collapse the distinction and both roles suffer. The PMO ends up reporting faithfully on everything except the portfolio it exists to govern. The principal ends up with executive support that has no defined scope, no reporting line of its own, and nobody to inherit it. Neither party asked for this arrangement. Both inherited it, one reasonable request at a time.
The succession problem surfaces last, and it costs the most. A named chief of staff can be replaced, because the role has a description, a mandate, and expectations that survive the person holding it. An informal one cannot. When the PMO manager who quietly became the principal’s chief of staff moves on, the function does not transfer. It simply stops. The principal then discovers how much of their own decision-making had been running through a role nobody had actually designed.
Strategy execution leadership is a third role again
It is worth separating a chief of staff from the strategy-execution identity argued for elsewhere on this site, because the two get conflated almost as often as PMO and CoS do. An execution leader is accountable for making an approved strategy happen at scale: the cadence, the portfolio, the performance system, the follow-through, across the whole organisation. That is a mandate gap in its own right, and a different one from this article’s.
A chief of staff’s scope is bounded by one principal’s week. Strategy delivery may sit inside that week as one topic among several. But the CoS clears the principal’s path toward decisions about it. They do not own the delivery itself.
Find the role by watching where unowned work lands
Organisations that get this right rarely start from a definition. They start from a question, held open for a quarter rather than answered in a single meeting: where does unowned executive work actually accumulate? If board material, unresolved decisions and cross-functional friction keep landing on the PMO, a chief-of-staff mandate has already been handed over. It arrived without the title, the direct line to the principal, or the standing to say no that the role requires. If the same work lands on an EA instead, the authority has arrived with nobody granting the standing to use it.
Naming the role is a decision, not a formality
None of this resolves by inventing a fourth job title and hoping the overlap sorts itself out. It resolves the way the mandate question resolves everywhere else on this site. Someone with real authority decides the chief-of-staff function exists. They give it a reporting line to the principal it serves. They draw the boundary back to the PMO in writing, rather than leaving it to whoever is available on a given Thursday.
The same instrument a PMO needs before its first hire does the job here too: a short document naming what the role decides, what it only recommends, and where it stops.
A hybrid “PMO-slash-chief-of-staff” role is not a pragmatic compromise. It is the unnamed version of the problem this piece describes, carrying the same cost forward under a single job title instead of two. The fix is not a better hybrid. It is the separation this article has been drawing throughout — one function accountable for the portfolio, one accountable to the principal, each named, each mandated, and each free to do the job it was actually meant for.
The PMO did not overreach here. It was promoted, and nobody told it.