The most effective digital transformation strategies are neither all-monolithic nor all-incremental: they are portfolios. IT leaders interviewed by Mary K. Pratt for CIO increasingly argue that CIOs must be able to deliver both capital "T" transformations — major resets such as an ERP rollout — and the smaller, iterative changes that accumulate into large-scale transformation over time. The real leadership challenge is not choosing one philosophy but deciding, initiative by initiative, which approach a given project demands. This article offers a decision framework for making that call, built from expert commentary and research on agile transformation strategy.

Beyond 'Big T': Embracing Agile and Adaptive Digital Transformation

The debate over "Big T" transformation has shifted. One IT leader Pratt spoke with, who defines transformation as "those moments where we change our business model (i.e., how we do business) or our operating model (i.e., how we organize ourselves)," still sees a place for major change — an ERP rollout, he notes, is "an essential platform reset that allows an organization to fundamentally rethink its business processes, operating models, and customer interactions." But he is also, in his words, "a firm believer in a culture of continuous evolution, where smaller, more manageable transformations lead to big transformations over time."

The constraint is organizational capacity, not ambition. As he cautions, "organizations have a finite capacity for deep operational shifts," and running major transformations too often or simultaneously invites change fatigue that undermines scope, delivery, and long-term adoption. The practical conclusion: continuous evolution yields large-scale transformation over time while delivering benefits along the way, and leaders must be able to deliver both types deliberately rather than defaulting to either.

Core Principles of an Agile and Adaptive Digital Strategy

What does an agile strategy actually consist of? A 2025 peer-reviewed study by Maryam Bayat and colleagues, published in Frontiers, defines an Agile and Adaptive Digital Strategy as the planning and implementation of digital initiatives that is "highly flexible, customer-centric, and quick to evolve in line with changes in the market and technology" — involving scalable digital goals, ongoing revisions of the plan, and the leveraging of new technologies to create competitive edge. Although the study focused on SMEs, the principle generalizes: strategy is a living document, not an annual artifact.

Three operational shifts follow. First, iterative processes with rapid adjustments based on market dynamics replace fixed multi-year plans — the core of what framework guides describe as an agile transformation approach that creates a culture of continuous improvement. Second, leadership itself must change shape. As Pascal Bécotte argues in an analysis of the C-suite, emerging challenges "do not touch just one function or business line at a time," so solving them requires working horizontally across the company rather than vertically within a single segment. Third, governance must make "agile" more than a buzzword: BCG's transformation guidance stresses adopting an agile mindset, principles, and culture throughout the organization, and monitoring progress against clear, quantified goals from start to finish.

Digital Transformation Decision Framework

The framework below categorizes any digital initiative along three dimensions — strategic alignment, scope of change, and value versus feasibility — and routes it to one of two methodologies: a foundational platform reset or an iterative continuous evolution. The purpose is to prevent the most common failure mode: confusing technology deployment with business transformation.

Decision matrix: classifying and prioritizing digital initiatives
DimensionPoints toward a Foundational "Platform Reset"Points toward an Iterative "Continuous Evolution"
Strategic alignmentDirectly changes how the business operates or is organized — the business or operating model itselfSupports existing objectives such as customer experience or operational efficiency without altering the operating model
Scope of changeRequires overhauling legacy infrastructure and ways of working; isolated tool adoption cannot achieve the goalCan be broken into iterative building blocks that deliver value independently
Value vs. feasibilityHigh strategic value that justifies deep operational shift, given the organization's finite capacity for such shiftsHigh value-to-effort ratio in early increments; course-correction in real time preserves value as conditions change
Resulting methodologyRun rarely, one at a time, as a capital "T" program with executive sponsorshipRun continuously, as small bets with big payoffs that compound into large-scale transformation

The reasoning path is straightforward. If an initiative's goal can only be met by changing the operating foundation — as with an ERP rollout that forces a fundamental rethink of processes and customer interactions — it is a reset, and the organization must budget its scarce capacity for deep change accordingly. If the goal can be met through incremental delivery that learns from each iteration, it belongs in the continuous-evolution track, where breaking big visions into iterative building blocks, as the CIO-reported leader puts it, gives the organization "the ability to course-correct in real-time while using technology as a force multiplier for growth."

Applying the Framework: Categorizing Initiatives

In practice, the two categories are complements, not rivals. A platform reset establishes a new operational foundation; continuous evolution then builds on it. Scaled Agile's enterprise transformation guidance makes the same point from the strategy side: the main goal is to align the transformation strategy with the company's wider objectives, so that initiatives revolve around core business targets, with a vision that defines an actionable roadmap and key performance indicators to measure success.

The portfolio view also disciplines resets. Because organizations have a finite capacity for deep operational shifts, leaders should treat each reset as a scarce, executive-sponsored event — not a reflex response to every technology cycle. Everything else routes to the evolution track, where smaller, manageable transformations compound. The failure to make this distinction is visible in organizations that adopt technology for its own sake: as Scaled Agile observes, fragmented efforts disconnected from wider objectives "don't deliver meaningful results and waste resources without achieving a good ROI."

Prioritizing for Strategic Value and Feasibility

Once categorized, initiatives compete for resources on business value, not novelty. Executive guidance on the agile transformation loop is blunt on this point: organizations that outperform are "not necessarily the ones that adopt the most technology" but "the ones that build the capability to transform repeatedly, intelligently, and with purpose." Prioritization should therefore ask whether initiatives are being ranked by business value and feasibility, or by internal pressure and market hype.

Two practical rules follow. First, anchor every initiative to a strategic vision before evaluating tools — scanning for solutions that fit the strategy rather than reacting to hype. Second, test ideas rigorously before committing to scale, which is precisely what the iterative track is designed to enable. A framework adapted to the organization's own priorities, risks, demand, and capacity — as Planview's transformation guidance recommends — turns these rules into a repeatable decision process rather than a one-off exercise.

Self-Assessment: Diagnostic Questions for Leaders

Before applying the framework, executives can test the maturity of their current approach. The following diagnostic questions, drawn from executive guidance on turning strategy into measurable business value, target the most common failure points:

  • Is our digital transformation strategy clearly aligned with wider business objectives, or are we adopting technology in isolation?
  • Do our business and technology leaders collaborate as an aligned team, or do they operate in functional silos?
  • Are we selecting solutions based on strategic fit, or are we reacting to market trends without clear purpose?
  • Have we prioritized initiatives based on their business value and feasibility, or on internal pressures?
  • Are we testing ideas rigorously enough before committing to scale?

A "no" or "unsure" on any question marks a specific weakness: a vision gap, an alignment gap, a hype-driven selection process, a politicized portfolio, or insufficient experimentation. Each maps directly to a dimension of the decision framework above, so the diagnostic doubles as a prioritization of what to fix first.

Moving Forward: Cultivating Continuous Transformation

Leaders should adopt a hybrid approach to digital transformation, strategically balancing foundational "platform resets" with continuous, iterative "evolutions" based on a clear decision framework. The measurable indicator of success is a portfolio of digital initiatives that clearly differentiates between foundational and iterative projects, with each project explicitly linked to measurable business value and strategic objectives. Until that differentiation exists on paper, transformation remains a series of technology purchases; once it does, technology deployment starts to translate into measurable business transformation.

Sources