When fractional delivery leadership beats a full time hire

Senior delivery talent is scarce, expensive, and rarely needed at full capacity. A fractional model often fits the actual shape of the work.

The default response to a delivery problem is to hire a senior leader full time. A program is slipping, a regulatory milestone is approaching, a reorganisation has left a critical function without an owner, and the instinct is to open a senior requisition and start a six month search. The instinct is understandable, and in many cases it is wrong. Most delivery crises do not need forty hours a week of attention. They need ten hours of the right attention.

Fractional delivery leadership is the practice of bringing in a senior operator for a defined slice of a defined problem, with a clear outcome, for as long as the outcome requires. It is not consulting, because the operator owns the delivery rather than advising on it. It is not interim management, because the engagement is sized to the problem rather than to the calendar. Done well, it matches the actual shape of senior delivery work, which is bursty, outcome-driven, and rarely fills a working week evenly.

The shape of senior delivery work

If you watch a senior delivery leader work through a real problem, the time profile is uneven. The first two weeks are intense: stakeholder interviews, system walkthroughs, a diagnosis, an initial intervention. The next month is medium intensity: the intervention is in flight, course corrections are needed, but the day to day belongs to the teams. The final stretch is light: the new pattern is operating, the leader is mostly available for escalation and decision support, the teams are running.

Hiring a full time leader against this profile means paying for forty hours a week of capacity to absorb a workload that averages perhaps fifteen, with peaks and troughs. The excess capacity does not disappear; it gets filled, usually with work that the organisation did not previously think it needed. Some of that work is genuinely valuable. Much of it is not, and the leader ends up creating workload for the teams to justify their own capacity. This is one of the more common ways organisations accidentally slow themselves down at the senior level.

When fractional is the right model

Fractional engagements fit specific shapes of problem. A program recovery, where the diagnosis and the intervention are both bounded. A regulatory milestone, where the work has an end date and a clear definition of done. A reorganisation of how teams ship, where the new operating model needs to be designed, installed, and stabilised, but does not need a permanent owner once it is running. A capability gap during a leadership transition, where the work needs senior judgment for six months while a permanent hire is found and onboarded.

In each of these shapes, the work has a defined outcome and a finite duration. A full time hire against finite work creates a permanent role that, once the work is done, either invents new work or quietly atrophies. Neither outcome is desirable. A fractional engagement ends cleanly when the outcome is reached, and the organisation retains the capability without retaining the cost.

When fractional is the wrong model

Fractional is not always right. When the work is genuinely permanent: running an ongoing engineering organisation, owning a product line, being the accountable executive for a function, full time ownership is the right answer. When the work requires deep, continuous immersion in the day to day of the team, such as a turnaround that needs the leader to be physically present at every standup, fractional is too thin. When the organisation is small enough that a single senior leader needs to wear several hats simultaneously, splitting the role does not reduce the workload, it just adds coordination cost.

The honest test is whether the work has a definable end. If you can describe, in concrete terms, what done looks like, fractional probably fits. If the work is a permanent function with no end state, hire full time.

The market reality

There is a second reason fractional engagements are increasingly common, which is a supply side reality that organisations are slow to acknowledge. The people who have actually shipped at scale: led a major regulatory program to completion, run a large engineering organisation through a transformation, stood up a governance function that survived contact with reality, are mostly not available full time. They are running their own portfolios of work. The pool of senior operators willing to take a single full time role at any given moment is small, and the search to find one is long.

Against this constrained supply, organisations have a choice. They can run a six to twelve month search for a full time hire, accept whoever is available rather than whoever is best, and absorb the opportunity cost of leaving the problem unowned during the search. Or they can engage a senior operator fractionally, with the right experience, starting next week. The fractional path is almost always faster, often better matched to the actual problem, and usually less expensive in total.

How to scope a fractional engagement

The most common way fractional engagements fail is loose scoping. The organisation knows it has a problem, brings in a senior operator with a vague brief, and three months later neither party can say whether the engagement is succeeding. The fix is to scope the engagement around an outcome and a date, not around a role and a calendar.

A well-scoped engagement names the outcome in concrete terms: the program is back on a defensible delivery plan, signed off by the steering committee. It names the date by which the outcome should be reached. It names the success criteria, ideally three to five specific, observable signals. And it names the off-ramp: what the engagement looks like in the final month, how knowledge is transferred, who picks up the ongoing work.

With this scoping, both sides know what they are committing to. The fractional leader knows what they are accountable for and when it ends. The organisation knows what it is buying and how to evaluate progress. Misalignment, when it appears, is visible immediately rather than at the end of the engagement.

What the day actually looks like

A fractional engagement at, say, two days a week, is not two days of physical presence followed by five days of absence. It is two days of synchronous work, which means meetings, decisions, working sessions with teams, plus asynchronous coverage for the rest of the week: reviewing documents, responding to escalations, unblocking decisions. The teams the leader works with do not feel the gaps if the asynchronous coverage is real, and they do feel the gaps if it is not.

The other property of a good fractional engagement is high context retention. The leader has to come back into the work each week with the same context they left it with, which means good notes, clear handoff with the teams, and an explicit list of open decisions. Senior operators who do this well make their two days feel like four. Senior operators who do not are reduced to running diagnostic loops every week, and the engagement stalls.

The economic case

On a pure cost basis, two days a week of senior fractional capacity costs roughly forty percent of a full time hire at the same seniority. The work delivered is rarely forty percent of the work; in most cases it is closer to seventy or eighty percent, because senior work compresses, and because the absence of organisational drag time allows the operator to spend their time on the actual problem.

The economic case becomes overwhelming when you factor in the search cost, the onboarding cost, and the cost of being wrong about a full time hire. A fractional engagement that does not work can be ended in thirty days. A full time hire that does not work takes six to twelve months to exit and costs significantly more in disruption. The fractional model is not always the right answer, but in the situations where it fits, it fits very well indeed.