Beyond IT: Winning the Mandate to Run Every Department's Services

📍 IN BRIEF

Expanding the platform beyond IT is not a bigger delivery programme, it is a sales campaign aimed at executives who owe you nothing, and it is won on earned sponsorship, built from translation, proof and patience, one department at a time.

Teams that treat the expansion as delivery with extra scope stall, while teams that treat it as selling a service operating model to peers they cannot direct tend to get there. I have watched enough platform teams attempt this crossing to know how it looks, and the capability is almost never the constraint. The mandate is.

Across an out of the box implementation, every task has exactly one accountable role, and the Platform Owner is accountable for around 1/3 of the total tasks. The Business Sponsor, the executive whose backing decides whether cross-functional expansion happens at all, is accountable for well under 1%. Yet that same sponsor sits in the informed and consulted columns of a RACI on around 40% of total activities, this means the role that matters most to expansion barely appears in the plan, because the work that wins and keeps a sponsor happens outside it. That gap is what this essay is about.

Your authority ends where the org chart says it does

Beyond IT you cannot direct anyone, you can only be worth listening to.

Inside IT, a platform owner holds real authority, setting standards, controlling the backlog, able to insist when persuasion runs out. The moment the conversation moves to HR, finance or legal, every one of those instruments vanishes. The head of HR does not care about your roadmap, the general counsel has never read your operating model, and nothing you say in that room is binding on anyone in it.

So the role changes character, and outside IT the platform owner is less a technologist and more a teacher and advisor. The winning version of that role spends its time explaining what a service operating model would do for the other department's own goals, in the other department's own words. HR do not run incidents, they handle cases, and payroll does not want a configuration record, it wants the month closed without a scramble. If your pitch needs the listener to learn your vocabulary before they can hear the value, you’re already failing.

There is also a reputation to overcome, and it is worth naming plainly. In most organisations the platform is filed under IT tools, and that filing is not hostility but the natural reading of years of evidence. It changes only when a department watches the platform solve a problem it recognises as its own.

Every department already runs services, whatever they call them

Discovery is translation, and the evidence is usually sitting in shared mailboxes.

One platform owner tells the story of asking a general counsel to describe the legal department's services, and the answer came back flat. We do not do services, we do stuff. So the platform owner asked a different question, how many shared mailboxes does legal run that do not belong to an individual, and the answer turned out to be six. NDA review, contract review and four more, each one a queue with requesters, work in progress and an outcome someone was waiting on. The service catalogue existed, it was just wearing an inbox.

That exchange is the whole discovery method in miniature. Departments outside IT rarely describe their work as services, and asking them to adopt your framing before you have understood theirs is how these conversations die. Start from their work instead, from the shared mailboxes, the spreadsheets that queue requests, the one person everyone emails when a thing needs doing. These are services in the wild, and they are countable, nameable and improvable.

The education runs both ways, because while the department learns what the platform can carry, you are learning how the department actually operates, what it measures and where it hurts. That knowledge is what turns your second meeting from a demonstration into a proposal.

Sponsorship is bought with proof, one department at a time

Two or three modest pilots buy the conversation that a strategy deck cannot.

The temptation, once an executive shows interest, is to go large with a flagship programme, an enterprise business case and a new steering committee, but the evidence points the other way. Expansion gathers force from two or three small pilots chosen precisely because they need very little change from the department adopting them, and a modest win inside HR, captured honestly and told in HR's language, does more for the next conversation than any strategy paper.

⚠️ COMMON PITFALL

The flagship first move. An enterprise-wide announcement before any department has seen proof creates sponsors on paper and sceptics in practice, and it spends credibility that a small pilot would have earned back with interest.

Proof also recruits messengers, because a director who has watched a pilot succeed in their own department stops being an audience and starts being an advocate, and an advocate inside the function carries weight you never will. The director of HR convincing their own CHRO is worth ten platform presentations, because the recommendation travels along a line of trust that already exists.

And when sponsorship comes, it should cost the sponsor something, because interest is free. Sponsorship is a budget line, or people seconded to the work when money is tight, and an executive who speaks warmly about the platform while committing nothing to it has not sponsored anything. They have subscribed to a newsletter.

A mandate is not adoption

A signature ends the argument, but only behaviour ends the resistance.

The most dangerous moment in a cross-functional expansion is the day you win the mandate, because it feels like the finish line and it is nothing of the kind. Even with an executive sponsor signed up, funded and enthusiastic, the department below them can still quietly decline to change, since competing priorities do not evaporate and the IT-tool reputation does not dissolve on contact with a memo.

What separates sponsors whose departments adopt from sponsors whose departments comply on paper is behaviour. Sponsors who show up, visibly and repeatedly, through the life of the change. Sponsors who build a coalition with their peers rather than delegating belief to a project team, and who tell their own people directly why this matters, in their own words. The change management evidence on this is blunt, and it is bluntest for change that stretches across several functions at once, which is exactly what running every department's services is.

This is why the accountability numbers from the opening are not a flaw in the method. Informed on 40% of tasks and accountable on 1% is what real sponsorship looks like inside a delivery plan, because the sponsor's accountable work never lands in your backlog. It happens in their calendar, in the peer conversations, the town halls and the moments they spend their own credibility on your behalf. You cannot assign that work, you can only earn it, and keep earning it.

Scale needs a home that no single function owns

Past three or four departments, expansion outgrows governance run from inside IT.

The first departmental deployment can be governed as an IT project with guests, but the fourth cannot, because by then there are process owners in three functions, service decisions that cut across departmental budgets, and a platform team caught between customers with equal standing and unequal demands. The organisations that manage this well build a centre of excellence that deliberately sits outside IT while including IT staff, led at a senior level, with stakeholders drawn from the business units the platform now serves.

The ownership split underneath it matters more than the org chart. The business owns its processes and its service outcomes, including real authority over where investment goes, while the platform team owns the platform. And some services will never belong to a single department at all. Employee onboarding runs through HR, facilities and IT before a new joiner does a day's work, and a service like that must be defined by the people it serves, not by whichever function shouts loudest. Agreeing these boundaries early, while everyone still likes each other, is far cheaper than negotiating them mid-dispute.

Where this doesn't apply

If your chief executive has already mandated and funded an enterprise service model from the top, the sequencing here is the wrong way round for you, so start from governance and let earned sponsorship confirm the mandate rather than create it, though the adoption work in the middle of this essay still applies in full. And if the platform team are not yet trusted for IT's own services, none of this applies yet, because credibility at home is the entry ticket to every conversation away from it.

The bottom line

Run the expansion as a sponsorship campaign, not a delivery programme with extra scope. Name the two or three departments where a modest pilot could win in their language within a quarter, measure sponsorship in funding or seconded people rather than warm words, and build the cross-functional governing home before your deployment count makes it urgent, because by the time it is urgent you will be negotiating it in the middle of a dispute.

The mandate to run every department's services is decided by executives who never appear on your delivery plan.

P.S. Watch the difference between a sponsor's signature and a sponsor's calendar. The first tells you the argument went well. The second tells you whether the adoption will follow it.