A full-time PMO director is a default, not a requirement. Whether two or three days a week is enough depends less on the size of the portfolio than on whether the organisation can hold the thread between visits.
Boards rarely ask whether a fractional PMO director would do the job. They assume the seat needs a full-time occupant, then argue about the salary or the day rate. The more useful question is how much director the organisation can actually absorb, at this stage of its strategy. Sometimes the honest answer is five days a week. More often than most sponsors expect, it is two or three: a fractional PMO director is enough when the PMO team and its routines can carry the work between the director’s days.
Three employees out of ten was a design, not a staffing gap
I once worked with a PMO of around ten people in a young industrial organisation. Roughly a third of them were employees. The rest were contractors, external change managers and consultants on service agreements. At first sight it looked like a rented PMO, the kind of structure an auditor would flag as a dependency risk.
It was a deliberate choice, and a sound one. The organisation did not yet need a full-scale PMO. It did not have the competences in-house, and its strategy placed them much later, once operations had stabilised. Hiring a complete permanent team at that point would have meant paying for capability years before the strategy could use it.
Yet the organisation still wanted a small permanent core, and that core was the clever part. Those few employees absorbed what the external specialists brought in. They held continuity when contractors rotated, owned the templates and the cadence, and turned money spent on outside services into knowledge that stayed in the building. Without them, every external invoice would have bought work and left nothing behind.
The same logic applies to the director’s seat. If the PMO itself can be designed around what the strategy needs now, so can its leadership.
Governance runs on cadence, not on hours
The assumption behind a full-time PMO director is that governance consumes hours. It mostly does not. It consumes cadence: a portfolio review that happens every month, a decision forum that meets every week, a reporting cycle that closes on a known day. Between those points, the work belongs to the project managers and the line.
An organisation that learns to batch its topics changes the arithmetic. Decisions wait for the forum instead of chasing the director down the corridor. Status questions go into the reporting cycle instead of ad-hoc calls. Escalations arrive prepared, with options and a recommendation, because everyone knows when they will be heard.
That discipline is learned, and the learning is part of the value. Once it takes hold, two or three days a week covers the governance load comfortably. In my own practice, this has been the pattern rather than the exception.
There is also a less comfortable point. A full-time director often creates the very demand that justifies the full-time role. When someone is always available, everything routes through them, and the organisation never learns to run its own cadence. Fewer days can produce a more capable PMO, not a weaker one.
Fractional works only when someone holds the thread between visits
A fractional model has preconditions, and they are not negotiable. The first is a core team that keeps the system running on the days the director is absent. Even two or three permanent people are enough, provided they own the cadence rather than merely attend it.
The second is a fixed rhythm. The director’s days should coincide with the forums, reviews and decision points, set months ahead, not negotiated week by week. The third is a working agreement on what a day actually means: hours, availability outside them, and how urgent matters reach the director in between. A day rate buys a day, not the person, and fractional arrangements fail fastest where nobody wrote that down.
The fourth precondition is a clear job. A fractional director designs, steers and builds capability. They do not personally produce every report, chase every action or sit in every project meeting. If that is the role the organisation actually needs, it needs more hands, not a director.
It fails where work arrives faster than any cadence can absorb it
Fractional is the wrong answer in a crisis. When a programme is in recovery, decisions arrive daily and cannot wait for Thursday. The same is true of the first weeks of any engagement, when the director has to learn the organisation, meet the people and build the cadence that later makes fewer days possible. A sensible pattern is to front-load: full-time for the first one to three months, then a planned step down.
It also fails without a core team. A part-time director with nobody holding the thread is not a fractional PMO. It is an absent one, with a gap of three or four days every week.
And it fails without a mandate, which no number of days can compensate for. A director who cannot take or force decisions becomes a part-time tracker, reporting on progress they have no authority to change. That problem is not caused by the fractional model, but the model makes it visible faster. The mandate has to come before the manager, whatever the contract says about days.
Finally, some work genuinely needs presence: cultural integration after an acquisition, a site start-up, a team in open conflict. Those are reasons to be in the building, and a good fractional director will say so before signing.
Remote removes costs nobody books as PMO costs
My recent contracts have been either fully remote or strongly hybrid, and the economics of that are easy to underestimate. Remote work does not only shorten the director’s week. It removes a whole category of spend that rarely appears in the PMO budget because it sits in travel and facilities lines.
Flights, hotels, per diems and the travel time billed alongside them simply disappear. For a director based in another country, they can add a meaningful share on top of the day rate itself. A fractional remote arrangement removes them entirely, or reduces them to a planned on-site visit around the key forums.
IT costs often shrink too. In practice, the only thing the client may need to provide is an account in its Microsoft 365 tenant. The director brings a professionally managed, encrypted device and handles their own data protection on their side.
That last point deserves precision rather than enthusiasm. The client remains the controller of its data, and the director works inside the client’s policies: multi-factor authentication, access rules, confidentiality and data-processing terms. Remote does not mean outside the client’s controls. It means the client does not have to buy, ship and support the hardware to apply them.
Remote also has a limit worth stating plainly. It works best once trust exists. A few days on site at the start, and around the forums that matter most, buy more than they cost.
The real deliverable is a PMO that needs its director less
The strongest argument for a fractional PMO director is not the saving. It is the direction of travel. Two or three days a week forces the director to transfer capability rather than hoard it, because the system has to run without them for most of the week.
That transfer should be planned, not hoped for. The core team takes over the cadence piece by piece. The director’s days move from running forums to coaching the people who run them. And when the strategy finally calls for a full-scale PMO, the organisation decides its scale deliberately and builds it on people who already know how its governance works.
At that point the fractional director either scales up into a broader role or hands over cleanly. Both are good outcomes. The bad one is a director who is still needed five days a week in year three.
The test was never how many days the director spends in the building. It is what still runs on the days they are not.