Why Most Digital Transformations Fail at Scoping The Domain Strategy Alternative

The transformation paradox facing business leaders has never been more acute. Organizations invest billions in digital and AI initiatives, yet failure rates remain stubbornly high. Research consistently shows that 70% of digital transformations fail to achieve their objectives, wasting resources and eroding organizational confidence. The culprit, according to McKinsey consultants Eric Lamarre, Kate Smaje, and Rodney Zemmel, is not technology or talent, but something more fundamental: scope.

In their recent article excerpted from Rewired: The McKinsey Guide to Outcompeting in Digital and AI, the authors present a compelling argument that most organizations doom their transformations from the start by choosing the wrong “bite size.” Too small, and the effort generates activity without impact. Too large, and complexity overwhelms execution capacity. Their prescribed solution is a domain-based approach that focuses organizational energy on 2–5 carefully selected business domains that are substantial enough to matter yet contained enough to succeed.

This framework deserves serious examination, both for its practical insights and its limitations. While the domain approach offers valuable structure for transformation planning, business leaders should understand its underlying assumptions, recognize where it applies most effectively, and know when alternative approaches might serve better.

The Scope Problem Is Real but Not New

The authors identify a genuine pathology in transformation efforts. Organizations routinely make one of three scope mistakes: starting with incremental pilot projects that never scale, attempting to transform everything simultaneously, or spreading resources across disconnected initiatives that lack coherence. Each pattern produces predictable failure.

The incremental approach feels safe. Leaders launch pilot projects in low-stakes areas, hoping to build momentum and learn before tackling core operations. A bank might digitize account opening for one customer segment. A manufacturer might deploy predictive maintenance on a single production line. These pilots often succeed technically but fail strategically because they do not change anything that fundamentally matters to customers or competitors. They become resume-building exercises rather than business transformation.

The opposite extreme proves equally problematic. Some organizations, often under pressure from boards or activist investors, announce comprehensive transformations touching every function and geography simultaneously. These efforts typically founder on complexity, resource constraints, and change fatigue. Employees face competing priorities, conflicting directives, and constant reorganization. The sheer coordination overhead consumes energy that should drive actual change.

Most commonly, organizations fall into what might be called “transformation drift.” Without clear focus, different functions and business units launch their own digital initiatives. Marketing pursues customer data platforms. Operations explores IoT sensors. Finance implements robotic process automation. Each initiative has merit individually, but collectively they lack strategic coherence. The organization generates activity and spends money without achieving competitive advantage.

The domain-based approach aims to navigate between these extremes by identifying business domains that are large enough to create material value but small enough to transform without being overwhelmed by dependencies. A domain represents a cohesive set of related activities, whether organized by workflow (procure-to-pay), journey (customer onboarding), or function (supply chain). The authors recommend companies identify 10–15 total domains, then select 2–5 for initial transformation based on value potential and feasibility.

The Framework’s Practical Strengths

Several elements of this approach deserve recognition for solving real problems. First, the framework forces explicit prioritization. Rather than letting transformation efforts proliferate organically, leadership must make hard choices about where to focus. The value-feasibility matrix provides structure for these discussions, moving beyond political considerations toward more objective assessment.

The emphasis on customer experience as “first among equals” among value considerations reflects important strategic reality. Research by Bain & Company and others consistently shows that companies leading in customer experience grow revenue 4–8% above market average. Digital technologies enable customer experience improvements impossible with legacy approaches, from personalization at scale to frictionless omnichannel interactions. Prioritizing domains with high customer experience impact aligns transformation with competitive advantage.

The feasibility assessment addresses practical execution concerns often overlooked in transformation planning. Strong executive sponsorship, data readiness, technology infrastructure, and change management capacity all significantly influence success probability. The authors rightly note that legacy technology, while requiring attention, should not become an excuse for inaction. As they observe, “Legacy mindsets are a bigger challenge than legacy technology.” This insight cuts through common organizational rationalization.

The framework also encourages realistic timeframes. Expecting meaningful results within 6–36 months creates urgency while acknowledging that real transformation takes time. This timeline counters both the pilot program trap (where initiatives never progress beyond proof-of-concept) and the indefinite transformation (where change becomes a permanent state rather than achieving a new steady state).

The Sanofi example illustrates these principles effectively. Dr. Pius Hornstein describes how ruthless prioritization, investing more in fewer chosen domains, and faster agile build cycles with user involvement produced more relevant and impactful solutions than previous fragmented efforts. His observation about leadership obstacles resonates: traditional siloed power structures actively resist the collaboration that digital transformation requires.

Critical Gaps and Questionable Assumptions

Despite these strengths, the domain approach rests on assumptions that deserve scrutiny. The most significant concerns involve organizational context, interdependencies, and what might be called the paradox of constraint.

The prescribed formula of 10–15 domains per business unit and 2–5 initial transformation targets implies a level of organizational standardization that may not reflect reality. A 50-person fintech startup and a 200,000-person industrial conglomerate face fundamentally different transformation challenges. The domain framework applies most naturally to established corporations with relatively stable business models and clear functional boundaries. High-growth companies, platform businesses, or organizations undergoing fundamental business model change may find domain boundaries artificial.

Consider Netflix’s transformation from DVD rental to streaming to content production. Each shift required reimagining the entire business model, not optimizing within defined domains. Similarly, Microsoft’s pivot to cloud computing under Satya Nadella involved rethinking every product, sales motion, and customer relationship simultaneously. These transformations succeeded not by careful domain scoping but by comprehensive strategic redirection.

The emphasis on self-contained domains with minimal dependencies sounds appealing but may be unrealistic. In practice, the highest-value opportunities often lie precisely at the intersections between traditional domains. Customer experience improvements typically require coordinating marketing, sales, service, and operations. Supply chain optimization depends on integrating procurement, logistics, manufacturing, and finance. Trying to isolate these as separate domains may miss the integration benefits that create real competitive advantage.

Research from MIT’s Center for Information Systems Research suggests that digital leaders often succeed by building integrated digital platforms that span traditional domain boundaries rather than by optimizing within domains. Companies like USAA, DBS Bank, and Ping An Insurance transformed by creating technology platforms that enable rapid innovation across multiple customer journeys simultaneously. Their approach suggests that in some contexts, investing in foundational digital capabilities matters more than domain-specific transformation.

The 80% success rate claimed for re-anchoring scope around well-defined domains deserves closer examination. This statistic comes from McKinsey’s own consulting engagements, creating potential selection bias. Organizations that hire McKinsey likely share certain characteristics: sufficient resources for external consulting, relatively mature management practices, and traditional organizational structures. The approach may work well for this population while being less applicable to other contexts.

The Measurement Challenge

The framework emphasizes measuring impact and generating measurable value, which is appropriate. However, the article provides limited guidance on a critical question: how to measure value that manifests over different timeframes or in hard-to-quantify ways.

Customer experience improvements, for instance, may increase retention and enable premium pricing, but these benefits often accrue gradually. Financial metrics like customer lifetime value require years to observe fully. Meanwhile, transformation costs hit immediately. This timing mismatch creates pressure to focus on domains with quickly measurable financial impact (typically cost reduction) rather than those building strategic capabilities (like customer experience or innovation capacity).

The speed-to-value criterion of 6–36 months may inadvertently bias domain selection toward operational efficiency plays rather than growth or business model innovation. Automating claims processing produces measurable savings within months. Building a digital ecosystem platform that enables new revenue streams may take years to show full returns. Both might be strategically important, but the framework’s emphasis on relatively quick returns could lead organizations to underinvest in transformational capabilities.

Alternative Frameworks and Complementary Approaches

Several alternative transformation frameworks deserve consideration alongside the domain approach. Each offers different insights about scope and prioritization.

The capabilities-based approach, advocated by researchers like Jeanne Ross and Cynthia Beath at MIT, focuses on building foundational digital capabilities (operational backbone and digital services platform) that enable innovation across multiple domains. Rather than optimizing specific workflows, this approach invests in shared technology platforms, data infrastructure, and operating models that reduce the cost and time required for subsequent domain transformations. The initial investment is higher and timeframe longer, but the approach may enable faster, more extensive subsequent change.

The jobs-to-be-done framework, popularized by Clayton Christensen, suggests scoping transformation around the fundamental jobs customers hire products to perform rather than around internal organizational domains. This customer-outside-in view might lead to different domain definitions that cut across traditional boundaries. A bank might define domains around customer jobs (saving for retirement, buying a home, managing daily finances) rather than products or processes.

The ecosystem approach recognizes that competitive advantage increasingly comes from orchestrating value networks rather than optimizing internal operations. Companies like Apple, Amazon, and Alibaba succeed by enabling third-party innovation on their platforms. Transformation scope in this model focuses on the platforms, APIs, and partnership models that enable ecosystem participation rather than on internal domain optimization.

Each framework has validity in different contexts. The domain approach suits established companies with relatively stable business models seeking operational improvement and customer experience enhancement. The capabilities approach fits organizations facing ongoing disruption requiring continuous adaptation. The jobs-to-be-done framework applies when customer needs are evolving faster than traditional product categories. The ecosystem approach makes sense for platform businesses or companies seeking to build platforms.

Implementation Realities and Organizational Politics

Beyond conceptual frameworks, transformation scope decisions involve organizational politics that frameworks tend to underemphasize. Domain selection inevitably creates winners and losers in terms of attention, resources, and career opportunities. Functions whose domains get selected for transformation receive investment and visibility. Those whose domains are deprioritized feel marginalized.

The article acknowledges this reality briefly in noting that some executives use competing priorities as reasons to delay transformation. However, the political dynamics run deeper. Domain transformation often requires reallocating budgets, changing reporting relationships, and redistributing power. The feasibility criterion of “strong executive sponsorship” sounds straightforward but may mask fundamental conflicts about organizational control.

Companies that successfully navigate these dynamics typically invest significant senior leadership time in building consensus around transformation priorities. The domain selection process itself becomes a vehicle for organizational alignment, forcing executives to debate strategy openly and commit to shared priorities. Treating domain selection as a purely analytical exercise risks generating formally correct frameworks that lack political viability.

The Culture Question

The article mentions change management and adoption challenges but gives them less emphasis than technical considerations like data readiness and technology infrastructure. This prioritization may reflect consultant bias toward tangible, technical factors over softer cultural elements. However, research consistently shows that cultural factors predict transformation success more reliably than technical capabilities.

Organizations with cultures emphasizing experimentation, customer focus, and cross-functional collaboration succeed at transformation regardless of starting technical position. Those with hierarchical, risk-averse, siloed cultures struggle even with excellent technology. The domain approach helps manage technical complexity but does not inherently address cultural barriers.

In fact, the domain structure might reinforce siloed thinking if not carefully managed. Assigning domains to specific executives could strengthen functional boundaries rather than breaking them down. The authors note this risk in quoting Sanofi’s Dr. Hornstein about the need for more open, collaborative leadership. However, the framework provides limited guidance on how to build this collaboration beyond noting synergies between domains.

Successful transformation increasingly requires what organizational scholars call “ambidextrous leadership”: the ability to run existing operations efficiently while simultaneously building new capabilities. The domain approach addresses the efficiency side well, providing structure for operational transformation within defined boundaries. It offers less guidance on the exploration side—how to build entirely new capabilities and business models that may not fit existing domain definitions.

Practical Recommendations for Business Leaders

Given both the strengths and limitations of the domain approach, what should business leaders actually do? Several principles emerge:

• Use the domain framework as a starting point, not a straitjacket. The value-feasibility prioritization provides useful structure for transformation planning. However, adapt domain definitions to your specific context rather than applying formulas mechanically. A 15-domain standard may be too many for smaller companies or too few for diversified conglomerates.
• Pay equal attention to integration and boundaries. While defining clear domain boundaries helps manage complexity, ensure mechanisms exist for coordinating across domains. Cross-domain integration often creates disproportionate value. Consider establishing integration teams or platform capabilities that enable domain orchestration.
• Balance quick wins with capability building. The 6–36 month timeframe for demonstrable value makes sense for maintaining momentum and funding transformation. However, also invest in foundational capabilities (data platforms, API infrastructure, agile operating models) that may take longer to show returns but enable faster subsequent change.
• Test domain scope empirically. Rather than debating exact boundaries analytically, run discovery sprints in candidate domains to understand actual dependencies, data availability, and value potential. Use these findings to refine domain definitions and transformation sequencing.
• Make domain selection a strategic dialogue, not just an analytical exercise. Use the prioritization process to surface strategic disagreements, build executive alignment, and secure genuine commitment. The process matters as much as the output.
• Recognize that transformation scope evolves. Initial domain selection should not be permanent. As you learn from early domains and as markets evolve, be prepared to adjust priorities, redefine boundaries, or add domains to the transformation pipeline.
• Invest disproportionately in change leadership for selected domains. Once domains are chosen, commit fully to their transformation. Half-measures produce neither quick wins nor capability building. The article rightly warns against spreading resources too thinly, but this warning applies within transformation efforts as much as to initial scope setting.

Looking Forward

The domain-based approach to transformation scope represents a meaningful contribution to transformation practice. It provides structured methodology where organizations often rely on intuition or politics. The emphasis on meaningful value, measurable impact, and realistic feasibility addresses real causes of transformation failure.

However, business leaders should view this framework as one tool among several rather than as a universal prescription. The most appropriate transformation scope depends on strategic context, competitive dynamics, organizational capabilities, and business model.

Companies facing existential threats may need comprehensive transformation despite the risks. Those with stable positions may benefit from focused domain improvements. Platform businesses may need to emphasize ecosystem orchestration over internal domain optimization. High-growth companies may find domain boundaries too constraining.

The transformation landscape itself continues to shift. Generative AI, in particular, may change optimal transformation scope. Unlike previous waves of digital technology that typically required domain-specific implementation, large language models offer horizontal capabilities applicable across multiple domains simultaneously. This may argue for broader initial scope than the 2–5 domain recommendation, or for focusing first on enabling capabilities rather than specific domains.

Ultimately, the question is not whether to use domains but how to think rigorously about transformation scope given your specific circumstances. The domain framework provides valuable structure for this thinking. Successful leaders will adapt its principles while maintaining its discipline: focus on what matters, commit fully to chosen priorities, measure relentlessly, and adjust based on what you learn.

The authors quote Jonathan Kozol’s aphorism: “Pick battles big enough to matter and small enough to win.” This wisdom captures the scope challenge elegantly. The domain framework helps identify these battles. Whether it provides sufficient guidance for winning them depends on how thoughtfully leaders adapt it to their circumstances while maintaining its core insight that transformation requires choosing the right bite size, neither too small to matter nor too large to swallow.