Digital Transformation Strategy: Why Most Programs Stall

Digital transformation strategy is the plan that determines how an organisation uses technology, data, and changed ways of working to improve commercial performance. Done well, it connects technology investment directly to revenue, margin, or customer outcomes. Done poorly, it produces a technology estate that costs more than it delivers and a workforce that has learned to work around the tools rather than with them.

Most programs stall not because the technology is wrong but because the strategy was never commercially grounded in the first place. The platform gets bought, the consultants get paid, the launch gets announced, and then the real business carries on largely unchanged.

Why Digital Transformation Has a Credibility Problem

I have sat in enough boardrooms to know that “digital transformation” has become one of those phrases that means everything and nothing simultaneously. It gets used to describe a CRM implementation, a website rebuild, an AI pilot, a full operating model overhaul, and anything in between. When a term covers that much ground, it stops being useful as a strategic concept.

The credibility problem compounds because most transformation programs are announced with significant fanfare and quietly wound down or redefined before they deliver the outcomes on the original business case. The people who led them move on. The metrics get restated. The organisation absorbs the cost and calls it learning.

I am not cynical about transformation itself. Technology has genuinely changed what is possible in marketing, in operations, in customer experience, and in commercial decision-making. What I am sceptical about is the industry that has grown up around selling transformation as a product rather than enabling it as a capability. There is a material difference between an organisation that has genuinely changed how it operates and one that has bought a new set of tools and updated its job titles.

If you want to think more broadly about how transformation connects to commercial growth, the Go-To-Market and Growth Strategy hub covers the surrounding disciplines that transformation programs are supposed to serve.

What Makes a Transformation Strategy Commercially Grounded

The organisations that execute transformation well share one characteristic: they start with a specific commercial problem and work backwards to the technology, rather than starting with a technology purchase and working forwards to a justification.

When I was running an agency and we were growing the team from around 20 people to close to 100, the operational strain became real quite quickly. Reporting was manual, client data lived in spreadsheets, and the time our people spent assembling information rather than using it was a genuine drag on margin. The transformation we went through was not glamorous. It was a series of decisions about which tools would reduce that friction, followed by the harder work of actually changing how people operated. No consultant came in and handed us a roadmap. We identified the constraint, found the solution that addressed it, and then did the unglamorous work of making it stick.

That experience shaped how I think about transformation strategy. The questions that matter are not “what technology should we adopt?” They are: where is commercial performance constrained right now, what is the root cause of that constraint, and is technology the right solution or are we reaching for a tool because it feels more decisive than addressing the underlying process or people issue?

BCG’s work on commercial transformation makes a useful point about the relationship between go-to-market strategy and operational change. The organisations that grow through transformation do so because the technology serves a clearly articulated commercial direction, not because the technology is inherently superior.

The Five Failure Modes That Derail Transformation Programs

Having watched transformation programs succeed and fail across a range of industries and organisation sizes, the failure patterns are remarkably consistent. They are not primarily technology failures. They are strategy and leadership failures that get attributed to technology after the fact.

1. The Business Case Is Built Around the Tool, Not the Outcome

When the business case for a transformation program is structured around the capabilities of a specific platform rather than the commercial outcome the organisation needs to achieve, the program is already in trouble. The technology vendor’s sales deck becomes the strategy document. The capabilities that were impressive in the demo become the objectives. The actual commercial problem the organisation faces gets reframed to fit the solution that has already been chosen.

This happens because procurement timelines and vendor relationships often move faster than strategic clarity. By the time someone asks “but what problem are we actually solving?”, the contract is close to being signed and the question feels obstructive rather than useful.

2. Change Management Is Treated as a Communications Exercise

The most consistent failure mode I have seen is treating change management as a series of internal communications rather than a sustained programme of behavioural change. You can send the all-hands email, run the launch event, and post the intranet update. None of that changes how people actually do their jobs on a Tuesday afternoon when they are under pressure and the new system is slower than the old spreadsheet they have used for three years.

Genuine change management is about incentives, capability building, and leadership behaviour. If senior leaders visibly continue to use the old processes, the transformation stops at their level and everyone below them watches carefully. The technology adoption curve in most organisations is not shaped by enthusiasm for the new system. It is shaped by whether the people with the most influence in the room are seen to be using it.

3. The Measurement Framework Is Built After Implementation

If you cannot articulate what success looks like before the program begins, you will not be able to measure it honestly after it ends. The organisations that build their measurement framework retrospectively are the ones that end up reporting on activity metrics (system adoption rates, training completions, modules deployed) rather than commercial outcomes (revenue per customer, cost to serve, conversion rates, margin).

Activity metrics are not meaningless, but they are not what transformation is for. A CRM that 90% of the sales team uses but that has not improved pipeline quality or close rates has not transformed the commercial function. It has just added a reporting layer.

4. The Program Has a Go-Live Date But No Steady-State Operating Model

Transformation programs structured as projects with a defined end date tend to underdeliver because they conflate implementation with transformation. Going live on a new platform is not the same as operating differently. The real transformation happens in the months after go-live, when the organisation is working through the gap between how the system was designed to be used and how people are actually using it.

The organisations that get this right treat go-live as the beginning of the transformation, not the end of it. They resource accordingly, maintain programme governance beyond implementation, and treat the post-launch period as the most commercially critical phase rather than the wind-down.

5. The IT and Commercial Functions Are Not Genuinely Aligned

Technology-led transformation programs that are owned by IT and presented to commercial functions tend to produce technically competent implementations that nobody in the revenue-generating parts of the business actually uses in the way they were intended. Commercial-led programs that ignore the technical constraints of the organisation’s existing architecture tend to produce expensive integrations that never quite work as promised.

The alignment that matters is not a joint steering committee that meets monthly. It is a shared understanding of the commercial problem being solved and a genuine joint accountability for whether the technology delivers against it. That requires both functions to be willing to compromise on their preferred ways of working, which is harder than it sounds when both have legitimate competing priorities.

How to Structure a Digital Transformation Strategy That Holds

A transformation strategy that holds under commercial scrutiny has six components. They are not sequential steps so much as interdependent elements that need to be developed with enough coherence that they reinforce rather than contradict each other.

A Clearly Defined Commercial Problem

The starting point is a specific, quantified commercial problem. Not “we need to be more digital” or “our customer experience needs to improve” but something with enough precision to be testable. Revenue per customer is declining at a rate that threatens the three-year plan. The cost to serve a customer in the mid-market segment is making that segment structurally unprofitable. The sales cycle is 40% longer than the industry benchmark and the data suggests it is an information flow problem rather than a relationship problem.

The more specific the problem definition, the more clearly you can evaluate whether a proposed technology solution actually addresses it. Vague problem definitions produce vague solutions and make it impossible to hold anyone accountable for commercial outcomes.

A Technology Architecture That Serves the Problem

Once the commercial problem is defined, the technology architecture question becomes much more tractable. You are not choosing between platforms based on feature comparisons. You are evaluating which configuration of technology best addresses the specific constraint you have identified, within the integration constraints of your existing systems and the capability constraints of your team.

Early in my career, I asked a managing director for budget to build a new website. The answer was no. Rather than accepting that the problem could not be solved, I taught myself to code and built it myself. That experience was formative in how I think about technology: the tool is in service of the outcome, and the question is always whether you have the right solution for the specific problem, not whether you have the most sophisticated or the most widely adopted platform in the market.

The Vidyard analysis of why go-to-market execution feels harder makes a useful observation about technology proliferation: adding more tools to a go-to-market stack does not automatically improve commercial performance. In many cases it increases complexity without improving output. The discipline is in choosing less rather than more, and ensuring that what you choose is genuinely integrated rather than loosely connected.

A Data Strategy That Precedes the Technology Decision

Most transformation programs underinvest in data strategy relative to technology selection. The technology gets chosen, implemented, and then the organisation discovers that the data feeding it is inconsistent, incomplete, or structured in ways that prevent the system from producing the outputs it was supposed to deliver.

Data strategy in the context of transformation means three things: understanding what data you currently have and how reliable it is, defining what data you need to make the commercial decisions the transformation is supposed to enable, and establishing the governance processes that will keep data quality at a level where the technology can actually use it. None of this is glamorous. All of it is foundational.

A Change Programme With Commercial Accountability

The change programme needs to be owned by someone with commercial accountability, not delegated to an internal communications team or an external change management consultancy working to a project brief. The person responsible for transformation outcomes needs to be the same person who is accountable for the commercial results the transformation is supposed to produce.

This is a structural point as much as a leadership one. When transformation accountability and commercial accountability sit in different parts of the organisation, the transformation program optimises for its own metrics rather than for the business outcome it was funded to deliver.

A Measurement Framework Built Before Implementation

Define the metrics that will determine whether the transformation has worked before the program begins. Establish baselines. Agree on the timeline over which commercial impact is expected to materialise, and be honest about the fact that some transformation investments take longer to produce commercial returns than the organisation’s planning cycle would prefer.

The measurement framework also needs to include leading indicators, not just lagging commercial outcomes. If the transformation is supposed to improve conversion rates six months after go-live, what are the early signals in the first 90 days that suggest the program is on track? Identifying those leading indicators in advance means you can course-correct before the commercial impact window has passed.

Tools like Hotjar’s feedback mechanisms are useful here for customer-facing transformation programs. Understanding how customer behaviour actually changes after you deploy a new experience, rather than assuming the design intent translated into the intended outcome, is the difference between measuring transformation and measuring deployment.

A Governance Model That Survives Leadership Changes

One of the most underappreciated risks in long-horizon transformation programs is leadership turnover. The executive sponsor who championed the program moves on. The new leader has different priorities, or a different view of the technology, or simply wants to put their own mark on the agenda. The program loses momentum, the governance structures atrophy, and the organisation ends up with a half-completed transformation and a technology investment that is neither fully embedded nor easily reversed.

Building governance structures that are strong enough to survive individual leadership changes is not about bureaucracy. It is about ensuring the commercial logic of the transformation is documented clearly enough that a new leader can understand why the program was initiated and what it was designed to achieve, rather than having to take it on faith from people who were there at the start.

Where Marketing Sits in the Transformation Picture

Marketing functions are simultaneously among the most active adopters of new technology and among the most inconsistent at translating that technology investment into measurable commercial outcomes. The marketing technology stack has expanded significantly over the past decade, and in many organisations the proliferation of tools has created as many problems as it has solved.

The specific challenge for marketing in a transformation context is that the outputs of marketing technology are often proximate metrics (impressions, clicks, engagement, leads) rather than the commercial outcomes the organisation actually cares about (revenue, margin, customer lifetime value). When the transformation program is evaluated against proximate metrics, it looks successful. When it is evaluated against commercial outcomes, the picture is often more complicated.

I have judged the Effie Awards, which are specifically designed to evaluate marketing effectiveness rather than marketing craft. The entries that stand out are consistently the ones where the marketing team had a clear commercial brief, built a strategy around it, and can demonstrate a credible connection between their activity and a commercial result. That clarity is rarer than it should be, and the absence of it is often masked by sophisticated-looking analytics that measure activity rather than outcome.

The Vidyard Future Revenue Report highlights an important tension in go-to-market teams: there is significant untapped pipeline potential in most organisations, but capturing it requires better integration between marketing technology and sales processes, not simply more technology in either function. That integration is a transformation challenge, not a technology selection challenge.

BCG’s work on aligning marketing and commercial strategy makes a similar point about the relationship between brand investment and commercial transformation. The organisations that get the most from transformation are the ones where marketing, sales, and operations are genuinely aligned around a commercial strategy, rather than each function pursuing its own technology agenda.

The Speed Question: How Fast Should Transformation Move

There is a persistent tension in transformation strategy between the pressure to move quickly and the reality that sustainable change takes time. Both sides of this tension have legitimate points. Moving too slowly means the competitive environment changes faster than the organisation, and the transformation program ends up solving for a problem that no longer exists in the same form. Moving too quickly means the organisation cannot absorb the change, adoption suffers, and the technology investment fails to deliver its intended outcomes.

The resolution is not a formula. It is a judgment call that depends on the specific commercial urgency, the organisation’s demonstrated capacity for change, and the complexity of the technology being deployed. What I would push back on is the assumption that faster is always better. The organisations I have seen rush transformation programs have consistently underestimated the cost of poor adoption and overestimated the speed at which commercial outcomes follow technology deployment.

When I was at lastminute.com, we launched a paid search campaign for a music festival and saw six figures of revenue within roughly a day from a campaign that was not particularly complex. That experience taught me something important about the relationship between speed and commercial impact: speed matters enormously when the commercial opportunity is time-sensitive and the execution is genuinely ready. It matters much less when the organisation is not yet capable of using the technology it is deploying. Rushing a transformation program to meet an arbitrary deadline is the equivalent of launching a campaign before the landing page works.

Transformation in Smaller Organisations: Different Constraints, Same Principles

Most of the published thinking on digital transformation is written for large enterprises with significant technology budgets, dedicated transformation teams, and the luxury of extended implementation timelines. Smaller organisations face a different set of constraints: tighter budgets, smaller teams, less tolerance for the productivity dip that typically accompanies major technology change, and a more direct relationship between the transformation program and the day-to-day running of the business.

The principles are the same. Start with the commercial problem. Choose technology that addresses it specifically. Build measurement frameworks before you implement. Treat change management as a sustained programme rather than a communications exercise. But the execution looks different in a 50-person business than in a 5,000-person one.

In smaller organisations, the most important transformation decisions are often about what not to do. The temptation to adopt every tool that promises to solve a problem is particularly acute when the organisation does not have a dedicated technology function to evaluate options critically. The discipline of saying “this tool solves a real problem we have right now” rather than “this tool solves a problem we might have eventually” is the difference between a technology stack that serves the business and one that the business serves.

If you are working through how transformation strategy connects to your broader commercial approach, the articles in the Go-To-Market and Growth Strategy hub cover the adjacent disciplines in more depth, including go-to-market planning, ICP development, and commercial measurement.

The Role of AI in Transformation Strategy Right Now

It would be unusual to write about digital transformation strategy in 2026 without addressing AI, so here is a grounded view rather than a breathless one.

AI is genuinely useful in specific, well-defined applications: content generation at scale, customer data analysis, personalisation at a level of granularity that was not previously cost-effective, and certain categories of process automation. These are real capabilities with real commercial value in the right context.

What AI is not is a transformation strategy. The organisations that are treating AI adoption as the entirety of their transformation agenda are making the same mistake that organisations made with earlier waves of technology: confusing the adoption of a capability with the transformation of how the business operates. AI deployed on top of broken processes produces faster broken processes. AI integrated into a commercially coherent operating model can produce genuine competitive advantage.

The questions worth asking about AI in a transformation context are the same questions worth asking about any technology: what specific commercial problem does this address, what does success look like and how will we measure it, and what needs to change about how we operate for this technology to deliver its potential? The answers to those questions determine whether an AI investment is commercially grounded or commercially theatrical.

For customer-facing applications, getting genuine feedback on how AI-driven experiences land with real customers is worth building into the measurement framework early. Understanding whether a new experience is actually improving outcomes for customers, rather than assuming it is, is the kind of honest approximation that user feedback tools can support when they are used with genuine curiosity rather than as a validation exercise.

What Good Transformation Leadership Looks Like

The leadership behaviours that correlate with successful transformation are not the ones that get celebrated in the trade press. They are quieter and more commercially disciplined than the transformation narratives that tend to get written up as case studies.

Good transformation leadership starts with intellectual honesty about the current state. Not the diplomatic version of the current state that gets presented in the board deck, but the actual state: where are we genuinely losing commercial performance, what are the real constraints, and what are we not doing well that we need to do better? That honesty is uncomfortable, and it requires enough psychological safety in the leadership team that people can name problems without it being read as an attack on whoever owns that area.

It also requires the patience to build capability rather than just buy it. Technology purchases are faster and more visible than capability development. They produce better slides and more impressive announcements. But the organisations that sustain transformation outcomes over time are the ones that have invested in building the internal capability to use, adapt, and evolve their technology stack, rather than depending on external vendors and consultants to do it for them.

Running agencies through growth and through difficult periods taught me that the difference between organisations that improve and organisations that stall is rarely about resources. It is almost always about whether the leadership has the clarity and the honesty to identify what is actually constraining performance and the discipline to address it systematically rather than reactively.

Transformation is not different. The organisations that execute it well are the ones where the leadership is genuinely curious about what is not working, genuinely committed to addressing it, and genuinely willing to be held accountable for whether the program delivers what it promised.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions