How should executives plan and fund a digital transformation?
share of digital transformation efforts that fail to meet their objectives, per McKinsey Transformation practice. The three-year-programme model is the failure mode.
only 30% of digital transformations meet or exceed target value; 26% deliver limited value with no lasting change, per BCG “Flipping the Odds of Digital Transformation Success” (70 BCG projects + 800+ executives).
deployment frequency advantage of elite DevOps teams over low performers; elite teams also have 127× faster lead times and 8× lower change-failure rates, per the DORA Accelerate State of DevOps 2024.
Plan a digital transformation as a series of small, separately funded steps instead of one multi-year programme. Each quarter, fund one workflow that crosses two functions, give it a single accountable owner, and release the next quarter’s money once the result is visible. A three-year plan assumes that markets, customer expectations and the technology stack will hold still for three years. They rarely do, and in our view that explains a good part of the failure rates McKinsey and BCG report above.
If you lead a product or engineering team and need the delivery practice behind these quarterly steps, how modern product teams ship covers that side.
For an executive, the real change is in how money and governance work. Organisations no longer modernise one channel at a time. They are rethinking how information moves, how teams make decisions, how products reach customers and how value is delivered across a connected system. Technology is one part of that. Budget cycles, ownership and incentives decide whether the change lasts.
If a senior leader cannot describe the next twelve months of transformation as “five small architectural moves we will rehearse and ship”, the programme is probably going to slip. Three-year roadmaps look impressive in slides and underdeliver in practice.
How do the fastest-transforming companies operate?
The fastest-moving organisations build repeatable change into the way they operate instead of launching ever larger programmes. They simplify architecture, improve data visibility, modernise workflows in smaller steps and give teams enough clarity to make good local decisions without waiting for a large central rewrite. For the people approving budgets, that means many small changes with clear owners rather than one big bet.
Cloud platforms, AI-assisted operations, automation layers and better internal tooling all feed this model, but none of them creates value on its own. Each pays off only when it comes with redesigned processes and an owner who answers for the result. If generative AI is part of your plan, how leaders roll out generative AI covers where it pays back and where it stalls.
The fastest companies modernise in smaller, repeatable steps. The slowest run rewrites the size of a startup.
Vadim Leviev · Levievs
Tools change only when habits change
One of the most common reasons transformation stalls is that systems change while behaviour does not. A new platform may launch, but decision-making stays slow. A new dashboard appears, but teams still rely on fragmented spreadsheets. A better workflow exists, but incentives still reward the old one. Lasting transformation requires changes in habits, governance, and collaboration patterns.
Five questions to answer before you “roll out” a new tool
- What habit is this replacing? If you cannot name it, the tool will fail.
- Who has to change incentive to make the new path easy? Tell them before the launch.
- What governance attaches to the new tool? Who owns it operationally?
- What does the first ninety days of use look like, day-by-day?
- What is the off-ramp if the tool does not pay back?
That is why effective transformation leaders spend as much time on adoption and governance as on architecture. Choosing the tool is only the visible part of the work, and usually the easiest.
What effective transformation leaders do differently
The most effective leaders set a clear direction, break the work into stages small enough to fund one at a time, and keep outcomes visible to the people paying for them. They track customer impact, team speed and decision quality, and treat implementation milestones as a secondary signal. When an organisation works like this for long enough, change stops being a special event with a launch date and becomes part of normal operations.
of large transformation programmes miss their original objectives, in line with the McKinsey Transformation practice figure.
per funded step. In our own reviews, programmes run in these rolling windows reached their goals more often than single-launch programmes.
the rollout every quarter. The best leaders we know set time aside for this, separately from choosing the tool.
One day on-site. We watch a planning meeting and write a punch list.
You will get a one-page diagnosis and three concrete next moves we would make this quarter, ordered by impact-to-effort.
What does a first-year transformation roadmap look like?
For an executive starting from scratch, the first year we recommend is small and unglamorous, and each quarter is funded on its own. Quarter one: pick one workflow that crosses two functions and is causing visible pain. Modernise it end to end (tooling, data, governance, ownership). Quarter two: fund the next one and carry over the lessons from the first. Quarter three: review the operating model itself, not just the tools. Quarter four: replace the slowest internal hand-off, even if it has no software in it.
There is no need to announce any of this as a transformation. Approve each quarter on the evidence of the one before and keep the cycle going. Our Technology Strategy Consulting work follows the same quarterly structure; when the platform itself has to change, the engineering runs as a separate engagement. For a platform-level example of small steps instead of a rebuild, see our WordPress performance checklist.
Fund transformation one quarter and one workflow at a time, with a named owner and governance agreed before launch. Change habits and incentives along with the tools, and review each quarter’s result before funding the next. In our experience, a rolling quarterly plan delivers more than a three-year roadmap.
On the consulting side of the same discipline: SMB consulting models compared. And before you sign with any external partner: a 12-point tech vendor due diligence checklist.
Frequently asked questions
Why do most transformation programmes miss their goals?
Because the tools change while habits stay the same. Buying the platform is the easy part. Redesigning the work around it (incentives, governance, hand-offs) is where most of the change happens, and it needs executive time as well as budget.
How should executives fund and pace a transformation?
In ninety-day rolling windows. Fund one cross-functional workflow, have it modernised end to end and shipped, review what the team learned, then fund the next. Three-year programmes look impressive on paper and consistently miss their objectives.
Where should AI fit into transformation?
As an automation layer on workflows you already understand and control. AI will not fix a workflow nobody can describe: it speeds up whatever process it is given, including a bad one.
How should leadership measure transformation progress?
By customer impact, team speed and decision quality rather than milestone count. Counting tickets closed is the common trap. A better question for the leadership team each quarter: “are we making faster, better-evidenced decisions than last quarter?”
