Nobody Owns the Middle: Closing the Accountability Gap in Enterprise Transformation Programmes

There's a particular moment in every troubled transformation programme that I've come to recognise. It doesn't arrive with a dramatic failure or a missed go-live date. It arrives quietly, usually around month four or five, in a steering committee meeting where everyone is nodding but nobody is deciding.

The strategy deck is polished. The delivery teams are busy. The PMO is dutifully reporting status. And yet, somewhere between the executive mandate and the sprint backlog, the programme has lost its spine. Decisions that should take hours take weeks. Blockers get escalated, acknowledged, and then recycled back down without resolution. Milestones are reported as green while the people closest to the work exchange knowing glances.

This isn't a people problem. It's a structural one. And in April 2026, as Nordic enterprises navigate the convergent pressures of AI adoption, EU AI Act compliance ahead of full enforcement in August, and operating model redesign, it's becoming the defining failure mode of enterprise transformation.

Nobody owns the middle. And until someone does, the programme is running on borrowed time.

The Accountability Vacuum Is Structural, Not Personal

Let me be precise about what I mean by "the middle." I'm not talking about middle management — though they're often the ones caught in the crossfire. I'm talking about the organisational layer where strategic intent must be translated into sequenced decisions, trade-offs, dependency management, and cross-functional coordination. The layer where someone needs to say: this is what we're actually doing next quarter, this is what we're not doing, and here's why.

In most enterprise transformation programmes, this layer is assumed to exist. It's implied by the org chart, gestured at in RACI matrices, and occasionally referenced in governance documents. But it's rarely owned by a single, named, empowered individual with the mandate to make binding decisions across workstreams.

Instead, you get a diffusion of partial ownership:

• The executive sponsor owns the vision and the budget, but doesn't — and shouldn't — operate at the level of cross-workstream sequencing and trade-off resolution.

• The delivery teams own their backlogs and their velocity, but lack the authority or visibility to resolve dependencies that span beyond their domain.

• The PMO owns the reporting, the governance cadence, and the risk register — but in most configurations, it owns none of the decisions.

This leaves a gap. Not a small one. A structural vacuum where the most consequential programme decisions — prioritisation trade-offs, scope arbitration, dependency resolution, resource conflicts — either go unmade or get made by default through inaction.

Eurostat data published in 2026 confirms that Denmark leads the EU in enterprise adoption of generative AI at 48.4%. Danish organisations are deploying fast. But deployment speed without governance maturity creates exactly this kind of accountability vacuum at scale. The programmes get bigger, the interdependencies multiply, and the unowned middle gets wider.

PMO vs. Transformation Office vs. Programme Director: The Dangerous Overlaps

Part of the problem is terminological confusion. Organisations use "PMO," "Transformation Office," and "Programme Director" almost interchangeably, as if naming a function is the same as mandating it. These are different roles with different ownership boundaries, and the failure to distinguish between them is where the gap opens.

The PMO — in its most common Nordic enterprise configuration — is a governance and reporting function. It maintains the programme plan, tracks milestones, manages risk and issue logs, and provides the steering committee with a consolidated view of progress. A well-run PMO is essential. But it is not, by design, an accountability owner. It reports on decisions; it doesn't make them. It surfaces blockers; it doesn't resolve them. When organisations expect the PMO to fill the middle, they're asking a function designed for transparency to perform the work of authority. This is a setup for what I call "governance theatre" — all the rituals of programme management, none of the actual steering. If you're building or reviewing your PMO and governance structures, this distinction is the first thing to get right.

The Transformation Office — increasingly common in larger Nordic enterprises — is a step closer. It typically has a broader mandate that includes change management, benefits realisation, and strategic alignment. But in practice, Transformation Offices tend to operate as an extension of the executive layer: they're good at maintaining strategic coherence and communicating the "why," but they often lack the operational depth to arbitrate between competing workstream demands on a Tuesday afternoon when two teams need the same integration resource.

The Programme Director — when the role exists and is properly mandated — is the closest thing to a middle owner. But here's the problem: in many Danish and Nordic enterprise programmes, the Programme Director role is either unfilled, filled by someone without cross-functional authority, or conflated with the PMO lead. The title exists on the org chart, but the mandate doesn't match the accountability.

The dangerous configuration — and I see it repeatedly — is when all three roles exist in some form, but none of them has explicit ownership of the translation layer. The PMO thinks the Programme Director is handling cross-workstream decisions. The Program Director thinks the Transformation Office is managing strategic trade-offs. The Transformation Office thinks the steering committee will resolve escalations. And the steering committee, meeting monthly, assumes everything below them is functioning.

Nobody owns the middle. Everyone assumes someone else does.

Three Warning Signs Your Transformation Has an Ownership Gap

The accountability vacuum doesn't announce itself. It manifests through patterns that are easy to rationalise individually but devastating in combination. After leading and recovering multiple programme and portfolio management engagements across Nordic enterprises, I've learned to watch for three specific signals.

1. Decision Paralysis at Mid-Programme

The first three months of a transformation are usually energetic. There's executive attention, fresh funding, and the optimism of a new mandate. Decisions flow because the decisions are easy — they're about setup, not trade-offs.

The real test comes at mid-programme, typically months four through eight, when the initial architecture meets reality. This is when you discover that two workstreams have incompatible data model assumptions. That the integration timeline assumes a platform readiness date that the vendor hasn't committed to. That the change management plan requires business process owners who haven't been identified, let alone engaged.

These are normal programme challenges. But in a programme with an ownership gap, they don't get resolved — they get discussed. You'll see the same items appearing on risk registers for consecutive reporting cycles, each time with a slightly updated mitigation narrative but no actual change in status. Decisions get deferred to the next steering committee, which defers them to a "working group," which meets once and produces a slide deck.

If your programme has more than three cross-workstream decisions that have been open for longer than two reporting cycles without resolution, you have an ownership gap.

2. Escalation Loops That Never Resolve

Healthy programmes have escalation paths. Unhealthy programmes have escalation loops — issues that travel up the governance chain, receive acknowledgement, and then travel back down without a binding decision.

The mechanism is subtle. An issue gets escalated from a delivery team to the PMO. The PMO includes it in the steering committee pack. The steering committee discusses it, agrees it's important, and asks the Programme Director to "work with the relevant stakeholders to find a solution." The Programme Director convenes a meeting with the stakeholders, who each explain why the issue isn't within their authority to resolve. The issue returns to the next steering committee pack, slightly reworded.

I've seen escalation loops that persist for entire programme phases. They're not caused by incompetent people — they're caused by a governance structure where no single role has the mandate to make a binding cross-functional decision below the steering committee level. The steering committee, meeting monthly or bi-weekly, cannot operate as the programme's real-time decision-making body. It wasn't designed to. But without a mandated middle owner, that's what it becomes by default — and it fails at it by design.

3. Milestone Theatre Masking Real Blockers

This is the most corrosive pattern, because it actively degrades the programme's ability to self-correct. Milestone theatre occurs when the reporting cadence and the governance incentives reward the appearance of progress over the reality of it.

In a programme with an ownership gap, delivery teams learn quickly that reporting a milestone as "at risk" triggers a cascade of attention they're not equipped to manage — because the governance structure above them can't actually resolve the underlying blocker. So they adapt. They redefine the milestone's completion criteria. They report partial delivery as full delivery. They shift scope between phases to keep the current phase looking green.

None of this is malicious. It's rational behaviour in a system where escalation doesn't produce resolution. Teams learn to manage the reporting rather than the reality, because managing the reality requires a level of cross-functional authority that doesn't exist in their governance structure.

If your steering committee pack has been consistently green for three or more cycles while the programme team's internal communications tell a different story, you're watching milestone theatre. And the root cause is almost certainly an unowned middle.

A Practical Accountability Model for the Middle Owner

Naming the problem is the easy part. Fixing it requires a concrete model for structuring middle ownership — one that can be implemented within existing Nordic enterprise governance norms without requiring a wholesale reorganisation.

Here's the model I've used successfully across multiple digital transformation programmes in Danish and Nordic contexts. It has four components.

1. Name the Role Explicitly

The middle owner needs a title, a mandate document, and a reporting line. I typically use "Programme Director" or "Transformation Lead," but the label matters less than the mandate. The mandate document should specify, in plain language:

• Decision authority: Which categories of decisions this role can make unilaterally, which require consultation, and which must be escalated. In practice, I define this as: any cross-workstream decision with a cost impact below a specified threshold and a timeline impact of less than four weeks can be made by the middle owner without steering committee approval.

• Escalation authority: The right to escalate directly to the executive sponsor, bypassing intermediate governance layers, when a decision requires executive authority.

• Arbitration authority: The explicit mandate to resolve conflicts between workstream leads when they cannot reach agreement. This is the authority most often missing and most often needed.

2. Position the Role in Governance, Not in Delivery

The middle owner must sit between the steering committee and the delivery teams — not within either. This is a governance role, not a delivery role. The middle owner doesn't manage sprints, write user stories, or own technical architecture. They own the translation of strategic intent into sequenced, resourced, dependency-managed delivery.

In practice, this means the middle owner:

• Attends steering committee meetings as a peer, not a reporter

• Chairs a weekly cross-workstream coordination forum with decision authority

• Has direct access to workstream leads without going through PMO channels

• Owns the integrated programme plan (not the PMO — the PMO maintains it, the middle owner owns it)

3. Protect the Role from Scope Drift

Middle owners are magnets for scope creep. Because they sit at the intersection of everything, they're the natural target for every problem that doesn't have an obvious home. Without protection, the role quickly becomes a catch-all — and loses its effectiveness.

Protection means:

• A defined scope boundary in the mandate document, listing what the role explicitly does not own (e.g., change management execution, technical architecture decisions, vendor management)

• PMO support for all reporting and administrative functions, so the middle owner's time is spent on decisions, not decks

• Executive sponsor backing that is visible and repeated — not just at appointment, but at every steering committee where the role's authority is tested

4. Build In a Review Cadence

The middle owner's mandate should be reviewed every 90 days. Transformation programmes evolve, and the decision landscape shifts as the programme moves from design to build to transition. The authorities that matter in month three are different from those that matter in month nine.

A quarterly mandate review — conducted between the middle owner and the executive sponsor — ensures the role stays calibrated to the programme's actual needs, and gives both parties a structured moment to address any authority gaps or conflicts that have emerged.

The Danish and Nordic Context: Why This Model Fits

Nordic enterprise governance culture has specific characteristics that make this model both necessary and viable.

On the necessity side: Danish and Nordic organisations tend toward consensus-driven decision-making. This is a genuine cultural strength in steady-state operations, but it becomes a liability in transformation programmes where speed and clarity of decision-making are critical. The accountability vacuum I've described is amplified in consensus cultures, because the default response to an unresolved cross-functional conflict is to seek alignment rather than to decide. A mandated middle owner gives the organisation permission to decide without full consensus — within defined boundaries — and that permission is often the single most valuable intervention in a stalled programme.

On the viability side: Nordic enterprises generally have mature governance cultures, strong PMO traditions, and a high degree of organisational literacy about roles and mandates. The infrastructure for this model already exists in most organisations. What's missing isn't the governance machinery — it's the explicit designation of who owns the middle.

Research from McKinsey's work on transformation execution consistently identifies accountability clarity as the primary differentiator between transformations that deliver value and those that don't. The pattern holds across geographies, but the fix needs to be locally adapted. In the Nordic context, the middle owner model works because it augments the existing governance culture rather than replacing it.

When to Bring In an Interim: The 90-Day Window

There's a specific moment in most transformation programmes when the ownership gap is most acute and most dangerous: the first 90 days after the programme moves from planning to execution.

This is when the programme transitions from a strategy-and-design exercise — typically well-owned by the executive layer — to a cross-functional delivery exercise that requires the middle layer to function. It's also when the organisation discovers whether its governance structure actually supports the kind of real-time, cross-workstream decision-making that delivery demands.

In many cases, the organisation doesn't have an internal candidate ready to step into the middle owner role at this critical juncture. The people with the right seniority are committed to BAU operations. The people with programme experience may lack the cross-functional authority. The people with authority may lack the programme craft.

This is where an interim programme director or interim CTO becomes not a luxury but a structural necessity. A fractional or interim appointment during this 90-day window serves three purposes:

1. Immediate accountability: Someone is named, mandated, and operational from day one of the execution phase, closing the gap before it opens.

2. Model establishment: The interim builds the governance cadences, decision frameworks, and cross-workstream coordination rhythms that the permanent middle owner will inherit.

3. Honest assessment: An external interim has no political debt within the organisation. They can name the real blockers, challenge milestone theatre, and make the uncomfortable arbitration calls that an internal appointee might defer.

The goal isn't permanent external dependency. It's a bridge appointment that establishes the middle owner model, proves its value, and creates the conditions for a successful internal handover. In my experience, 90 days is usually sufficient to establish the cadence — though complex programmes may need a longer runway.

The Cost of Leaving the Middle Unowned

Let me be direct about what's at stake. With the EU AI Act reaching full enforcement in August 2026, Danish enterprises — already leading Europe in AI adoption — face a concrete deadline that makes programme accountability a compliance issue, not just an efficiency issue. Transformation programmes that can't make timely cross-functional decisions about AI governance, data architecture, and process redesign won't just be slow. They'll be non-compliant.

Beyond compliance, the cost is measured in the currency that matters most: organisational trust. Every escalation loop that doesn't resolve, every milestone that's reported green while the team knows it's red, every cross-workstream conflict that festers because nobody has the mandate to decide — each of these erodes the organisation's belief that transformation is possible. And once that belief erodes, it's extraordinarily difficult to rebuild.

The fix isn't complicated. It's a named role, a clear mandate, a governance position, and executive backing. It's not a new framework or a new methodology. It's the oldest principle in organisational design: if something matters, someone must own it.

The middle matters. Name the owner.

*Jacob Poulsen advises Nordic enterprises on programme governance, digital transformation, and interim technology leadership. If your transformation programme is showing the warning signs described in this article, get in touch to discuss how to structure accountability before the programme goes off the rails.*