Digital Strategy

Digital strategy is the practice of deciding how an organization will use information technology to win—not merely to run its back office, but to change what it sells, how it reaches customers, and how it organizes work.

12 frameworks, from 1985 to today · Information Systems · Business, Management & Finance

still a working view ended · each leads to its entry below

Overview

Digital strategy is the practice of deciding how an organization will use information technology to win—not merely to run its back office, but to change what it sells, how it reaches customers, and how it organizes work. The field sits inside information systems but leans toward the boardroom: its central question is why some firms turn computing into advantage while others spend heavily and gain little. That question has been asked in different vocabularies since the 1980s, and the answers have shifted as technology moved from the data center to the web to the platform to the algorithm. What follows traces those shifts.

Strategic Alignment: Making IT Serve the Business Plan

Through the 1970s and early 1980s, corporate computing was mostly administrative—payroll, accounting, inventory. The strategic question was framed by the MIT researchers John Henderson and N. Venkatraman, whose "strategic alignment model" (published in 1993) argued that a firm's IT choices and its business strategy must fit together, and that fit could be pursued from either direction: let strategy drive IT, or let IT capabilities reshape strategy. The idea was influential because it gave managers a vocabulary for a real frustration—systems built to specifications that no longer matched what the business was trying to do.

Alignment thinking treated IT as a support function to be fitted to a plan. Its limitation became obvious as soon as computing started creating markets rather than serving them.

IT as a Competitive Weapon

In 1985, Michael Porter and Victor Millar published "How Information Gives You Competitive Advantage" in the Harvard Business Review, arguing that information technology was reshaping the structure of industries and could be used to build cost or differentiation advantage. The same period produced celebrated cases: American Airlines' SABRE reservation system, which gave the airline a distribution edge and later became a business in its own right, and American Hospital Supply's electronic ordering terminals, which tied hospital customers to the supplier. The message was that IT could be a weapon, not a utility.

The claim drew a sharp rebuttal. In 1988, the economists Paul Strassmann and, separately, Warren McFarlan's critics pointed out that advantages built on IT were easily copied; a rival could buy the same hardware. The debate crystallized a tension the field has never fully resolved: if everyone can buy the technology, where does durable advantage come from?

The Productivity Paradox and Complementarity

That tension sharpened when the economist Robert Solow remarked in 1987 that "you can see the computer age everywhere but in the productivity statistics." The "productivity paradox"—heavy IT spending with weak measured productivity gains—became a defining puzzle of the 1990s. Erik Brynjolfsson's work (from the early 1990s onward) reframed it: the returns were real but delayed and uneven, and they depended on complementary investments—new work practices, worker skills, and organizational redesign—not on the technology alone. His studies with Lorin Hitt and others found that firms pairing IT with decentralized decision-making and redesigned processes outperformed those that did not.

The complementarity idea mattered because it moved the field's attention from the machine to the system around it. It also set up the next question: if advantage comes from organizational fit, what happens when the technology itself becomes a commodity?

E-Business and the Dot-Com Era

The commercialization of the web in the mid-1990s produced a burst of strategic thinking about electronic commerce. Firms experimented with selling online, reconfiguring supply chains, and reaching customers directly. The period's emblematic claims were about disintermediation—cutting out middlemen—and about "born digital" entrants threatening incumbents. Much of the strategy literature of the late 1990s and early 2000s (including work by Venkatraman on "business configuration" and by others on e-business models) tried to map which activities the internet would make cheaper, which it would make newly possible, and where value would pool.

The dot-com crash of 2000–2001 disciplined the rhetoric. The lasting lesson was less about any single model than about the speed of experimentation the web allowed—and the cost of mistaking a technology shift for a guaranteed business.

Business Model Innovation

Out of the e-business years came the "business model" as a strategic unit of analysis: a description of how a firm creates and captures value—its customer proposition, its revenue logic, and its cost structure. The concept was popularized in the late 1990s and early 2000s (Joan Magretta's 2002 HBR piece "Why Business Models Matter" is a standard reference). Its strategic point was that technology could change the model itself, not just its efficiency: a firm might shift from selling products to selling subscriptions, from owning assets to orchestrating others'.

The business-model lens proved durable because it gave managers a way to talk about digital change without reducing it to a technology purchase. It also invited overreach—many "new models" were old models with a website—and the field gradually learned to demand evidence of unit economics rather than narrative.

IT Commoditization and the "IT Doesn't Matter" Debate

In 2003, Nicholas Carr's HBR article "IT Doesn't Matter" (expanded into a 2004 book) argued that as IT became ubiquitous, standardized, and cheap, it could no longer be a source of differentiation—it was becoming infrastructure, like electricity. The piece provoked a storm. Critics pointed to firms whose advantage clearly rested on distinctive systems, and to the difference between commodity components and the organizational arrangements built around them.

The debate's lasting contribution was to force precision. Some IT is commodity; the strategic question is which layers are, and where a firm can still build something rivals cannot easily copy. That question led directly to the platform era, where the answer often lay in networks and ecosystems rather than in any single firm's systems.

Platforms and Two-Sided Markets

From the early 2000s, a body of economics and strategy work explained businesses that create value by connecting two or more groups—buyers and sellers, developers and users, riders and drivers. The economists Jean-Charles Rochet and Jean Tirole formalized two-sided markets (their key papers appeared in the early 2000s), showing that pricing on one side often subsidizes participation on the other12. Strategy scholars, notably Annabelle Gawer and Michael Cusumano, studied platform leadership—how a firm like Intel or Microsoft sets the rules and technical direction for others who build on its core.

The practical insight was that network effects—where each new user makes the service more valuable to the next—could produce winner-take-most outcomes, and that the strategic levers were openness, governance of complementors, and control of the interface. This work reshaped how firms thought about competition: not just product versus product, but ecosystem versus ecosystem.

Strategy as Practice

Alongside these economics-driven strands, a more sociological view emerged in the 2000s. Strategy-as-practice, associated with scholars such as Richard Whittington and Paula Jarzabkowski, argued that strategy is not only a plan formulated at the top but something people do—in meetings, workshops, tools, and everyday routines. For digital strategy, this mattered because it drew attention to how technology choices get made in practice: who has a seat at the table, which tools shape the conversation, and how strategy documents and dashboards actually steer behavior.

The practice lens tempered the field's tendency to treat strategy as a purely analytical exercise. It also connected digital strategy to the broader information-systems concern with how systems are implemented and used, not just designed.

Data-Driven Strategy and the Digital Operating Model

By the 2010s, the falling cost of storage and computation, plus the spread of analytics, made data itself a strategic asset. Firms built "digital operating models"—organizational arrangements in which data, software, and rapid decision cycles are central rather than peripheral. The strategic claims were about speed and learning: firms that could measure, test, and adjust faster would outpace those that planned in annual cycles. The concept of the "digital operating model" (used by consultancies and scholars alike) bundled together agile teams, product management, cloud infrastructure, and analytics into a single picture of how a digital firm runs.

This strand inherited the complementarity insight—technology pays off when paired with organizational change—and applied it at the level of the whole operating model rather than a single process.

Digital Capability Building

A related line of work asked what capabilities a firm must build to compete digitally. Drawing on the resource-based view of the firm, scholars argued that advantage comes from bundles of skills, routines, and assets that are hard to imitate—not from any single system. The "dynamic capabilities" framework (developed by David Teece and others) was applied to digital contexts: firms need the ability to sense change, seize opportunities, and reconfigure resources. In practice, this meant investing in digital talent, data infrastructure, and the organizational muscle to change repeatedly.

The capability view gave the field a way to answer Carr: even if the technology is commodity, the capability to deploy it distinctively is not.

Lean Experimentation

The 2010s also brought a methodological shift: the idea that strategy under uncertainty should be run as a series of cheap experiments rather than a single big bet. The "lean startup" movement, popularized by Eric Ries's 2011 book, and the "build-measure-learn" loop gave managers a vocabulary for testing hypotheses about customers and business models quickly. In larger firms, this appeared as innovation labs, minimum viable products, and staged investment.

The approach's appeal was that it matched the pace of digital markets; its risk was that experimentation without discipline becomes drift. The field's ongoing work tries to specify when experimentation pays and how to connect small tests to strategic commitments.

Algorithmic Governance and Accountability

The most recent turn concerns what happens when strategy is executed by algorithms—pricing engines, recommendation systems, automated decision tools—and when those algorithms make consequential choices about people. Scholars and regulators have pressed questions of accountability: who is responsible when an automated system discriminates, misprices, or misallocates? The field has drawn on work in algorithmic accountability and governance, arguing that firms need mechanisms for oversight, explanation, and redress built into their digital strategies, not bolted on afterward.

This strand connects digital strategy back to the discipline's older concern with implementation and use: a strategy that runs through algorithms is only as good as the governance around them.

Where the Field Stands

Today digital strategy draws on all these strands at once. Alignment thinking persists in the language of "business-IT partnership"; the competitive-weapon debate survives in arguments about whether any firm can sustain advantage; complementarity is the default explanation for why technology investments disappoint; platform and ecosystem strategy dominates discussions of market structure; and the practice, capability, data, experimentation, and governance strands supply the operating vocabulary. The open questions are recognizable from the history: how to measure the returns on digital investment when the benefits are organizational and delayed; how to build capabilities that rivals cannot copy when the underlying technology is widely available; and how to keep human accountability intact as more strategic decisions are delegated to algorithms. The field's history is, in effect, a long argument about where advantage lives when the technology itself keeps becoming cheaper and more widespread—and that argument is not settled.

References

  1. Two-sided market, Wikipedia
  2. Network effect (Origins), Wikipedia

The frameworks of Digital Strategy

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1985-2000

    IT as Competitive Weapon

    Can information technology create durable competitive advantage?

    Fly to its tower in Nousfarer

  2. 1990-Present

    Productivity paradox

    Why does heavy IT spending yield weak productivity gains?

    Fly to its tower in Nousfarer

  3. 1993-Present

    Strategic Alignment

    How should IT choices fit with business strategy?

    Fly to its tower in Nousfarer

  4. 1995-2005

    E-Business and Disintermediation

    How will the internet change where value is created?

    Fly to its tower in Nousfarer

  5. 1998-Present

    Business Model Innovation

    How does a firm create and capture value?

    Fly to its tower in Nousfarer

  6. 2000-Present

    Strategy as Practice

    How is strategy actually done in everyday practice?

    Fly to its tower in Nousfarer

  7. 2002-Present

    Platform and Two-Sided Market Strategy

    How do firms win by connecting multiple groups of users?

    Fly to its tower in Nousfarer

  8. 2003-2012

    IT Commoditization Debate

    Can standardized IT still differentiate a firm?

    Fly to its tower in Nousfarer

  9. 2005-Present

    Digital Capability Building

    What capabilities must a firm build to compete digitally?

    Fly to its tower in Nousfarer

  10. 2010-Present

    Data-Driven Strategy and Digital Operating Model

    How should a firm organize around data and software?

    Fly to its tower in Nousfarer

  11. 2011-Present

    Lean startup

    How can new ventures learn what customers want fast?

    Fly to its tower in Nousfarer

  12. 2015-Present

    Algorithmic accountability

    Who is responsible when algorithms make consequential decisions?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

IT as Competitive WeaponProductivity paradoxStrategic AlignmentE-Business and DisintermediationBusiness Model InnovationStrategy as PracticePlatform and Two-Sided Market StrategyIT Commoditization DebateDigital Capability BuildingData-Driven Strategy and Digital Oper…Lean startupAlgorithmic accountability

Beyond the field

Where Digital Strategy's ideas came from in other fields, and what they led to there: the strongest 12 of 37 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Digital Strategy is a planet in Nousfarer

Its city has a tower for each of these 12 frameworks. Land, walk in, and climb one concept at a time.

Land on Digital Strategy

Related fields

Fields its ideas are linked to

More in Information Systems

See where Digital Strategy sits on the Map of Human Knowledge