I’ve spent twenty years in the trenches of programme rescue consulting. I’ve seen $200M portfolios evaporate and $5M migrations grind to a halt.
If you’re a CIO or a Head of Transformation reading this, you’ve likely felt that cold dread when a project starts to "drift." You look at your dashboard, and everything is green. You sit in your Steering Committee, and everyone is nodding. Yet, you know: deep down: that you aren’t going to hit the go-live date.
Why? Because in most enterprise transformations, nobody actually owns the outcome.
We have plenty of people who own "activities." We have people who own "workstreams." We have vendors who own "deliverables." But when the ship hits the iceberg, you find out that accountability has been so diluted across committees and tiers that there is no one left at the wheel.
If you want to save your transformation, you need to make one decision today: Appoint a single person who owns the delivery outcome. Not the status. Not the slides. The outcome.
The Accountability Gap: Why 70% of Transformations Fail
By now, the statistics are common knowledge. Depending on which 2026 study you read, between 70% and 88% of digital transformations fail to meet their original ambitions.
But here is the statistic that should keep you up at night: 84% of those failures are leadership-driven. It’s not a "tech problem." It’s not that the cloud was too complex or the AI wasn’t ready. It’s that the leadership structure was designed for reporting, not for execution.
In the standard enterprise model, responsibility is split three ways, and none of them work:
- The Steering Committee (The "Too High" Tier): They meet once a month. They look at high-level summaries. They are too far removed from the ground to see the watermelon status (green on the outside, red on the inside) until it’s too late.
- The Delivery Team (The "Too Tactical" Tier): They are focused on the next sprint or the next Jira ticket. They can’t see the strategic forest for the technical trees. If a cross-functional blocker appears, they don't have the authority to break it.
- The Vendors (The "Margin" Tier): Your big-name consulting partners are great at producing slide decks. But their primary accountability is to their own quarterly margin, not your business case. If the project stalls, they just sell you more "change requests."
This is what I call the "Empty Chair" in IT delivery. Everyone is present, but no one is truly accountable for the end-to-end success.
The Fix: A Single Accountable Delivery Lead
When I go in for a delivery diagnostic, the first thing I look for is the "One Throat to Choke."
Most organizations tell me they have a "Programme Director." When I dig deeper, that person is usually a high-level administrator. They consolidate reports. They manage the budget spreadsheet. They facilitate meetings.
That is not a Delivery Lead.
A Delivery Lead is a practitioner-grade operator who has the scars from previous failures. They don't just report status; they make decisions.
Delivery Lead vs. Programme Manager: The Critical Distinction
In my world, there is a massive difference between these two roles. If you confuse them, you’re in trouble.
| Feature | Traditional Programme Manager | Strategic Delivery Lead |
|---|---|---|
| Primary Goal | Following the plan (Scope/Schedule/Budget) | Achieving the Business Outcome |
| Communication | Reports status from workstreams | Challenges workstreams on validity |
| Authority | Escalates issues to the SteerCo | Resolves issues before they reach SteerCo |
| Mindset | "Did we do what the contract said?" | "Will this actually work in production?" |
| Governance | Process-oriented | Execution-oriented |
A Program Manager asks: "Is the slide deck ready for Thursday?"
A Delivery Lead asks: "Why has the data migration stalled, and which three people do I need to get in a room to fix it now?"
Giving the Lead the "Right to Win"
If you appoint a Delivery Lead but don't give them decision rights, you’ve just added another layer of bureaucracy. For a delivery governance consulting model to work, your Lead needs three things:
1. The Right to Challenge Vendors
Your vendors will hate this. A true Delivery Lead knows when a vendor is "land-and-expanding" or when they are hiding behind a vague Statement of Work. The Lead must have the authority to halt payments or pivot the vendor’s focus without waiting for a month-long procurement review.
2. The Right to Reallocate Resources
Transformations are fluid. You might find out in Month 3 that your bottleneck isn't the backend code, but the security audit. A Delivery Lead must be able to move people and budget to the point of greatest friction immediately.
3. The Right to Speak Truth to Power
This is the most important one. If your Delivery Lead is afraid to tell the CIO that the Q4 deadline is a fantasy, they are useless. You aren't paying them to be liked; you are paying them to ensure the programme doesn't hit a wall.
The Execution-First Mindset
At Dark Consultancy, we don't believe in "slide-deck consulting." When we step into a programme rescue, we don't start with a three-month strategy phase. We start by identifying who owns the outcome.
If that person doesn't exist, we fill the gap.
We look for the "failing points" in your enterprise technology execution. Usually, it’s a lack of alignment between what the business thinks they are buying and what the engineering team is actually building.
Stop "Managing" and Start "Delivering"
If your transformation is currently in that "drifting" phase: where meetings are long but progress is short: it's time to stop managing the bureaucracy and start focusing on the outcome.
Ask yourself: If this project fails tomorrow, who is the one person whose job is on the line? If the answer is "the committee," you have already failed.
You need a single point of accountability. You need someone who is as invested in the outcome as you are.
Actionable Next Steps for CIOs:
- Audit your governance: Does your Program Director have the authority to override a vendor's technical lead? If not, why?
- Kill the "Status-Only" meeting: Replace your next SteerCo with an "Obstacle Removal" session. If there are no obstacles to remove, the meeting is over in 5 minutes.
- Check for the Watermelon: Ask for a demo of a core feature, not a slide deck about it. If they can't show it, the status is red, no matter what the dashboard says.
FAQ: Ownership and Accountability in Transformation
1. Can the CIO be the single accountable person?
No. The CIO is accountable to the Board, but they cannot be in the weeds of a specific $50M transformation daily. You need a dedicated Lead who reports to you, but who "lives" in the project.
2. Is this just a "Scrum Master" for the whole program?
Absolutely not. A Scrum Master facilitates a team's process. A Delivery Lead owns the business outcome, manages the budget, handles vendor politics, and makes strategic trade-offs.
3. What if our internal culture is "consensus-based"?
Consensus is the enemy of delivery. You can have consensus on the strategy, but you need a "benevolent dictator" for the execution.
4. How do I know if I have a "Program Manager" or a "Delivery Lead"?
Ask them: "If we miss the deadline, what was the primary cause, and why didn't you stop it?" A Program Manager will give you a list of external factors. A Delivery Lead will tell you where they made a calculated risk that didn't pay off.
5. How does this work in the Public Sector?
In the public sector, accountability is often even more fragmented. The fix is the same: you need a Senior Responsible Owner (SRO) paired with a high-calibre Delivery Lead who understands regulated environments.
About the Author
Kunal Patel : CEO & Founder, Dark Consultancy
Kunal Patel founded Dark Consultancy after two decades leading technology and transformation programmes across the public sector, financial services, defence, and energy industries. He has directly managed programme recovery engagements for government agencies, development finance institutions, and regulated enterprises across the US, Middle East, South Asia, and Southeast Asia : ranging from $5M platform migrations to $200M+ enterprise transformation portfolios. Kunal is a recognised practitioner in delivery governance for regulated environments and holds PMP and PRINCE2 Practitioner certifications. He leads every new client engagement personally and remains accountable throughout the programme lifecycle. Connect with Kunal on LinkedIn
Are you tired of "Watermelon Status" reports and drifting deadlines?
Don't let your transformation become another failure statistic. Book a 30-minute Discovery Call with Kunal to identify the gaps in your delivery governance and put your programme back on the path to success.