- Atlas
- Business, Management & Finance
- Digital Strategy
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
- IT as Competitive Weapon 1985-2000
- Productivity paradox 1990-Present
- Strategic Alignment 1993-Present
- E-Business and Disintermediation 1995-2005
- Business Model Innovation 1998-Present
- Strategy as Practice 2000-Present
- Platform and Two-Sided Market Strategy 2002-Present
- IT Commoditization Debate 2003-2012
- Digital Capability Building 2005-Present
- Data-Driven Strategy and Digital Operating Model 2010-Present
- Lean startup 2011-Present
- Algorithmic accountability 2015-Present
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
- Two-sided market, Wikipedia
- 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.
- 1985-2000
IT as Competitive Weapon
Can information technology create durable competitive advantage?
- 1990-Present
Productivity paradox
Why does heavy IT spending yield weak productivity gains?
- 1993-Present
- 1995-2005
E-Business and Disintermediation
How will the internet change where value is created?
- 1998-Present
- 2000-Present
Strategy as Practice
How is strategy actually done in everyday practice?
- 2002-Present
Platform and Two-Sided Market Strategy
How do firms win by connecting multiple groups of users?
- 2003-2012
IT Commoditization Debate
Can standardized IT still differentiate a firm?
- 2005-Present
Digital Capability Building
What capabilities must a firm build to compete digitally?
- 2010-Present
Data-Driven Strategy and Digital Operating Model
How should a firm organize around data and software?
- 2011-Present
- 2015-Present
Algorithmic accountability
Who is responsible when algorithms make consequential decisions?
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 Commoditization Debate reacted against IT as Competitive Weapon
Carr's 'IT Doesn't Matter' attacked the competitive-weapon thesis head-on, arguing that ubiquitous standardized IT could no longer differentiate. The rebuttals forced the field to distinguish commodity layers from the organizational arrangements built around them.
Carried by Nicholas Carr.
Business Model Innovation grew out of E-Business and Disintermediation
The business model concept grew directly out of e-business analysis: mapping which activities the internet made cheaper or newly possible led to treating the value-creation and value-capture logic itself as the strategic unit. Magretta's 2002 piece codified the concept that e-business work had produced.
Carried by Joan Magretta; N. Venkatraman.
Productivity paradox reacted against IT as Competitive Weapon
The productivity paradox arose as a direct challenge to claims that IT spending automatically yielded competitive advantage. Brynjolfsson and others pointed to weak measured productivity despite heavy investment, forcing the field to ask where the advantage actually came from.
Carried by Robert Solow; Erik Brynjolfsson.
Digital Capability Building influenced by Productivity paradox
The complementarity finding—that IT pays off only when paired with organizational change, skills and redesigned processes—became the core premise of digital capability building. Later work generalized the complementarity argument from single processes to firm-wide capabilities.
Carried by Erik Brynjolfsson; Lorin Hitt.
Data-Driven Strategy and Digital Operating Model influenced by Productivity paradox
Data-driven strategy and the digital operating model inherited the complementarity insight and applied it at the level of the whole operating model, bundling agile teams, analytics and cloud infrastructure as the organizational complements to data technology.
Carried by Erik Brynjolfsson.
Algorithmic accountability influenced by Data-Driven Strategy and Digital Operating Model
As data-driven strategy made algorithms central to decisions, the question of who is accountable for algorithmic outcomes arose directly from that operating model. Algorithmic accountability took the data-and-algorithm apparatus and asked about its governance and harms.
IT Commoditization Debate influenced by Productivity paradox
The productivity paradox's finding that returns depended on complements rather than the technology itself fed the commoditization debate's distinction between commodity components and the organizational arrangements around them.
Carried by Nicholas Carr.
Data-Driven Strategy and Digital Operating Model influenced by Strategic Alignment
The alignment question—how technology choices fit with business intent—was carried into digital operating model thinking, where the fit is pursued through product teams and rapid decision cycles rather than annual plans.
Carried by N. Venkatraman.
Platform and Two-Sided Market Strategy influenced by Business Model Innovation
The business-model lens's focus on how a firm creates and captures value carried into platform strategy, where the model is defined by which side is subsidized and how complementors are governed.
Carried by Annabelle Gawer.
Lean startup influenced by Business Model Innovation
Lean startup took the business-model lens's demand for testable value logic and turned it into a method: build-measure-learn cycles and validated learning replaced narrative business plans with experiments.
Carried by Eric Ries.
Data-Driven Strategy and Digital Operating Model influenced by Strategy as Practice
Strategy-as-practice's attention to how strategy is actually done—through tools, meetings and routines—shaped digital operating model thinking about agile teams, dashboards and decision cycles as the practice of strategy.
Carried by Richard Whittington; Paula Jarzabkowski.
Algorithmic accountability influenced by Platform and Two-Sided Market Strategy
Platform governance work on rules, openness and control of interfaces fed algorithmic accountability, which extended the governance question to the algorithms that allocate visibility and opportunity on platforms.
Lean startup rival of Data-Driven Strategy and Digital Operating Model
Lean startup and data-driven operating model thinking competed in the 2010s over how digital firms should learn and decide, one emphasizing rapid experimentation from small teams and the other firm-wide analytics and operating-model redesign.
Carried by Eric Ries.
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.
IT as Competitive Weapon influenced by Porter's Competitive Strategy in Marketing Strategy
Porter's five-forces and value-chain analysis supplied the vocabulary and analytic frame that the IT-as-competitive-weapon literature applied to information systems. Writers such as Michael Hammer and later Warren McFarlan and the Harvard group explicitly recast Porter's competitive forces for IT investment.
Carried by Michael E. Porter; Competitive Strategy (1980).
E-Business and Disintermediation influenced by Electronic Markets and Hierarchies in Electronic Commerce
Malone, Yates and Benjamin's electronic markets and hierarchies argument, that IT lowers coordination costs and shifts activity toward markets, is the direct source of the e-business disintermediation thesis. The later literature applied their market-hierarchy shift to web commerce.
Carried by Thomas W. Malone; JoAnne Yates; Robert I. Benjamin.
Platform and Two-Sided Market Strategy influenced Platform-Mediated Entry in Foreign Market Entry
Platform and two-sided market strategy supplied the core concepts of network effects, multi-sided pricing and platform governance that platform-mediated entry applies to entry decisions. The later framework is largely that strategy literature turned toward the question of how firms enter platform markets.
Platform and Two-Sided Market Strategy influenced Platform and Ecosystem Strategy in Information Systems
Platform and two-sided market strategy research supplied the pricing, subsidy and multi-homing concepts central to platform strategy. The framework extends this work to broader ecosystem competition.
Lean startup grew out of Customer development in Venture Creation
Customer development, Steve Blank's method of getting out of the building to test hypotheses with customers, is the direct precursor from which Ries's lean startup was refined.
Carried by Steve Blank; The Four Steps to the Epiphany (2005).
IT as Competitive Weapon influenced Strategic Alignment Model in It Governance
The idea of IT as a competitive weapon framed the strategic question the Strategic Alignment Model answered by mapping business and IT domains. Henderson and Venkatraman built their model to explain how IT strategy could deliver that competitive value.
Carried by John C. Henderson; N. Venkatraman.
IT as Competitive Weapon influenced Platform and Ecosystem Strategy in Information Systems
The IT-as-competitive-weapon literature argued that information technology confers strategic advantage. Platform strategy research inherited this strategic framing of IT and extended it to platform competition.
IT as Competitive Weapon influenced Strategic Alignment and IT Business Value in Information Systems
The IT-as-competitive-weapon debate of the mid-1980s, framed by Porter and Millar and by McFarlan, set the question of how IT creates business value that strategic alignment research took up and operationalised.
Carried by Michael E. Porter; F. Warren McFarlan.
IT as Competitive Weapon influenced IT Decision Rights and Governance Archetypes in It Governance
The IT-as-competitive-weapon literature of the 1980s and 1990s framed IT as a strategic asset whose value depended on managerial control, a premise Weill and Ross built on when they argued that governance determines whether IT investments pay off. Their decision-rights framework is a direct response to the question of how firms capture strategic value from IT.
Carried by Peter Weill; Jeanne W. Ross; IT Governance (2004).
Productivity paradox influenced by Technology and work in Work And Labor
Research on technology and work, including labour-process and skill-change studies, supplied the questions about how IT changes productivity and work organisation that the productivity-paradox debate took up. The paradox literature drew on this body of work to explain why firm-level IT investment did not show up in aggregate output.
Productivity paradox influenced by Skill-Biased Technical Change in Human Capital And Skill Formation
Skill-biased technical change gave the productivity-paradox debate a mechanism: IT complements skilled labour, so gains appear only where skills and organisation adjust. Economists explaining the paradox's disappearance drew directly on this literature.
Strategic Alignment influenced by Strategy and Structure in Management
Chandler's strategy-and-structure thesis, that structure follows strategy, supplied the fit logic that strategic alignment transferred to the pairing of business and IT strategy. Henderson and Venkatraman's model is explicitly a fit-between-strategies argument in that tradition.
Carried by Alfred D. Chandler; Strategy and Structure (1962).

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 StrategyRelated fields
Fields its ideas are linked to
- Platform Strategy 7 links
- It Governance 4 links
- Information Systems 3 links
- Venture Creation 2 links
- Strategic Management 2 links
- Marketing Strategy 2 links
- Digital Lending 1 link
- Financial Technology 1 link
- Material Culture And Folklife 1 link
- Electronic Commerce 1 link
- Sociotechnical Systems 1 link
- Foreign Market Entry 1 link
More in Information Systems
- Business Analytics
- Decision Support Systems
- Electronic Commerce
- Enterprise Architecture
- Enterprise Systems
- Information Systems
- It Governance
- Platform Strategy
- Sociotechnical Systems
- Systems Analysis And Design
See where Digital Strategy sits on the Map of Human Knowledge