Ask most digital leaders what's slowing their programme down, and they'll give you an honest answer. Resourcing constraints. Stakeholder alignment. Data quality. A backlog that's longer than the team can realistically service.
What they're less likely to name, not because they're unaware of it, but because it's harder to point to, is the operating model itself.
The operating model is the invisible architecture of your digital programme. It's the answer to questions like:
-
who owns what,
-
how decisions get made,
-
how work moves from idea to delivery,
-
how your agency and internal teams interact,
-
how performance gets reviewed,
-
and how priorities get set when they conflict.
It's not the strategy. It's not the technology. It's the structural plumbing that connects the two.
When it works, you barely notice it. When it doesn't, you feel it everywhere - in the friction, in the delays, in the recurring conversations about accountability that never quite get resolved.
The cost that doesn't show up on a spreadsheet
Operating model problems are expensive in ways that are difficult to measure precisely, which is exactly why they persist. The cost isn't a line on a budget. It's diffuse, accumulated, and mostly invisible.
It looks like this.
A feature that should take two weeks takes six, because three teams need to sign off and nobody owns the decision. A data insight surfaces that should change what gets prioritised but by the time it reaches the right person, the backlog has already been set for the quarter. A content team that could be using platform capabilities they've been licensed for years isn't, because nobody ever connected the training to the workflow. An agency that does excellent work against the brief it's given, but never challenges the brief itself because the relationship isn't structured to support that.
None of these things feel catastrophic in isolation. But they compound.
Over twelve months, an operating model that creates consistent friction doesn't just slow things down, it shapes the culture of the programme. Teams learn to work around the friction rather than through it. Workarounds become habits. Habits become the de facto way of working. And the gap between what the programme could deliver and what it does deliver quietly widens.
Three patterns we see most often
Unclear ownership at the point of decision. In most enterprise digital programmes, there are more stakeholders than decision-makers. Marketing, IT, product, compliance, the agency, the platform vendor - all with legitimate interests, none with clear primacy. When ownership is ambiguous, decisions either get made too slowly, get made by whoever shouts loudest, or don't get made at all. Each of those outcomes has a cost.
Agency relationships structured for delivery, not challenge. The default agency model in enterprise digital is transactional: the client defines the work, the agency delivers it. That model has its place. But it means the agency's value is capped at the quality of the brief it receives. The highest-performing digital partnerships we see are structured differently. The agency brings ideas, challenges assumptions, and shares accountability for outcomes, not just delivery. Most don't operate that way. Not because the agency isn't capable of it, but because the relationship hasn't been designed for it.
Performance review disconnected from prioritisation. Many digital teams have reporting. Fewer have a clear, consistent process that runs from performance data to backlog decision. When review and prioritisation operate separately, as they do in most organisations, insight gets generated that doesn't change what gets worked on. The dashboard exists. The decisions don't follow.
Why it's hard to fix from the inside
There's an obvious challenge with diagnosing operating model problems from within: the people inside the model are operating within its constraints every day.
The friction feels normal because it's always been there. The workarounds feel efficient because they're the fastest path to getting something done. The gaps in accountability are managed through personal relationships that work until the person moves on or the relationship breaks down.
This is why operating model issues so often get misidentified.
The symptoms like slow delivery, poor data adoption, inconsistent quality get attributed to headcount, or the platform, or the agency, when the root cause is structural. And structural problems don't get fixed by hiring another person or switching tools.
They get fixed by being named clearly, mapped honestly, and redesigned with an understanding of how work actually moves through the organisation, not how it's supposed to.
What a functioning operating model actually looks like
It doesn't have to be complex. In fact, complexity is usually the enemy. The highest-performing digital operating models we work within tend to share a few characteristics.
-
Roles are explicit and understood by everyone who touches the programme - not just the digital team.
-
Decision rights are defined at each stage of the workflow, so the right people are making the right calls without everything escalating to a single bottleneck.
-
The agency relationship is structured around outcomes, not outputs, with a regular cadence that includes commercial challenge and strategic input not just delivery updates.
-
And performance review is connected directly to prioritisation, so insight reliably changes what gets worked on.
None of that requires a restructure. It requires clarity, deliberate design, and typically, someone willing to name the gaps that everyone privately knows exist but nobody has formally addressed.
The question worth asking
If someone asked you today to describe exactly how a new digital initiative moves from idea to live in your organisation - who owns each stage, who makes each decision, what happens when priorities conflict - how confident would you be in the answer?
If the honest answer is "it depends" or "it varies" or "it's complicated", that's the operating model talking. And it's worth listening to.
At Mando Group, defining and improving digital operating models is one of the core things we do as part of every client engagement. If you'd like to understand where your programme's operating model is creating friction - and what to do about it, let's talk about out our Optimisation Services
