Domino's decided to build its own ordering software
In its annual report for 2010, Domino's described a decision that sounded like an IT matter: "In 2010, we made the strategic decision to develop our own online ordering platform" 1. At the time, it said, "nearly 25% of our domestic stores' sales originate online" 1. A year later the figure was "almost one-third" 2.
Fifteen years on, the company reported that "in the U.S., Domino's generated more than 85% of U.S. retail sales in 2025 from digital channels" 3, a measure it now defines a little more broadly than the old online share. The same report does not describe technology as support for the strategy. It says: "Technological innovation is vital to our brand and our long-term success, and technology is critical to competing in the global pizza and broader QSR industries" 3.
Domino's still sells pizza. But somewhere in those years, how it takes an order stopped being a back-office question and became part of what the company competes on. A decision that started in the technology plan ended up shaping the corporate one.
A technology strategy that only follows the business plan is a budget. One that also tells the business what has become possible is a strategy.
Most companies run technology strategy in one direction
The usual sequence goes like this. The executive team sets the corporate strategy. Business units translate it into plans. Then the technology function is asked what systems those plans need, how much they will cost and when they can be ready. Technology strategy, in this telling, is a functional strategy, one level down from the business, like the finance or people strategy; see corporate vs. business unit vs. functional strategy.
That sequence is right most of the time. A technology team that sets its own direction without regard to the business builds elegant systems nobody needed. But it has a blind spot: it asks technology to serve the strategy, and never asks whether technology has changed what the strategy could be.
John Henderson and N. Venkatraman made the point in a paper that still shapes how the field thinks about it. Their model of strategic alignment rests on "two building blocks: strategic fit and functional integration" 4: the fit between a company's choices about its market and its internal arrangements, and the integration between the business and the technology function. Crucially, they described alignment running both ways. In two of their four perspectives the business strategy drives technology; in the other two, which they called competitive potential and service level, it is the information technology strategy that leads 4.
Following: how technology strategy should flow from the corporate strategy
When technology is in its supporting role, the work is a cascade of four translations. Each one should be written down, because each is where the plan most often drifts.
- From strategic choices to the capabilities they needIf the strategy is to win mid-sized customers on speed of service, the capability is fast onboarding and support, not "a new CRM". Name the capability in business words first.
- From capabilities to what technology must doFor each capability, say what the systems must make possible: self-service setup in a day, a single view of the customer for every support agent. These are the technology requirements, still free of product names.
- From requirements to the portfolioNow decide what to build, buy, keep, replace or retire. This is where most technology plans start, which is why so many of them read as shopping lists.
- From the portfolio to the moneySplit the budget between running what exists and changing it, and show what the change budget buys against each strategic choice. If a strategic priority has no money against it, the plan has dropped it without saying so.
Done well, the cascade lets a board trace every large technology investment back to a choice in the corporate strategy, and see which strategic choices have no technology behind them yet.
Leading: when technology strategy should push back
The other direction is harder, because it asks a function to question the plan it was hired to serve. Three situations call for it.
- When technology changes what customers can be offered. Ordering a pizza on a phone, paying by the minute, getting an answer in seconds: when the technology makes a new kind of offer possible, the corporate strategy should hear about it before competitors make it standard.
- When technology changes the cost of doing something. A task that took a team of ten may take two. That can change which markets are worth serving and which products pay, which is a corporate question, not an IT one. Much of today's debate about AI is this question; Stratrix tracks how companies are answering it in AI Business Models and the calls in Stratrix Stance.
- When the existing systems constrain the strategy. Sometimes the most important thing technology can tell the business is no: the plan assumes a speed or a data set the current systems cannot deliver without years of work. That is a strategic fact, and it belongs in the strategy conversation, not in a project status report a year later.
The practical fix is a step in the planning calendar. Before the corporate choices are fixed, the technology leader brings a short paper: what has become possible since last year, what it would let us do, and what our current systems would stop us from doing. Then the corporate strategy is written with that paper on the table. See the annual planning cycle for where the step fits.
Five questions for the CEO and the CIO
- Which of our strategic choices depends most on technology?Name it. If the answer is "none", either the strategy is unusually old-fashioned or nobody has looked.
- What has technology made possible since we last set the strategy?Ask for three things, each with what it would let a customer do or what it would cost less to do.
- Where do our current systems limit the strategy?The plan should say which strategic choices are slowed or blocked by existing systems, and what it would take to remove the block.
- How much of the technology budget runs what exists, and how much changes it?If nearly all of it keeps the lights on, the technology strategy is mostly about the lights. Say so, and decide whether that is the right split.
- Who decides when the two strategies conflict?Name the forum and the person. A conflict with no owner is settled by whoever controls the budget, which is rarely the best judge.
What a good technology strategy contains
| Part | What it says | The test |
|---|---|---|
| The strategic link | Which corporate choices it serves, and how | Every major investment traces to a choice |
| What has become possible | Technology shifts that could change the corporate strategy | At least one idea the business had not asked for |
| Constraints | Where existing systems limit the strategy | Named systems, named limits, a cost to fix |
| The portfolio | Build, buy, keep, replace, retire | Decisions, not a list of projects |
| The money | Run versus change, and change by strategic choice | No priority without funding, no funding without a priority |
| Governance | Who decides, when the strategies conflict | A named forum and a decision date |
The IT strategic plan template turns this into a document you can fill in, starting with the budget most plans leave out: the cost of running what you already have.
Questions
- What is a technology strategy?
- A technology strategy sets out how a company will use technology to carry out its corporate strategy: the capabilities it needs, the systems to build, buy or retire, and how the money is split between running what exists and changing it. A good one also tells the business what technology has made possible.
- How should IT strategy align with business strategy?
- In both directions. Technology strategy should follow from the corporate strategy, translating its choices into capabilities, requirements and investments. It should also inform the corporate strategy, by bringing new possibilities and current constraints to the table before the corporate choices are fixed.
- What is the difference between IT strategy and digital strategy?
- IT strategy usually covers the systems and infrastructure a company runs on. Digital strategy usually covers how technology changes what the company offers customers and how it reaches them. In practice they overlap, and the distinction matters less than making sure both connect to the corporate strategy.
- What is the strategic alignment model?
- A model from John Henderson and N. Venkatraman that describes alignment between business and technology through strategic fit, between external choices and internal arrangements, and functional integration, between the business and technology domains. It includes perspectives in which business strategy drives technology and others in which technology strategy leads.
Sources
- Domino's Pizza, Inc. (2011). Annual report on Form 10-K for the fiscal year ended January 2, 2011. US Securities and Exchange Commission.
- Domino's Pizza, Inc. (2012). Annual report on Form 10-K for the fiscal year ended January 1, 2012. US Securities and Exchange Commission.
- Domino's Pizza, Inc. (2026). Annual report on Form 10-K for the fiscal year ended December 28, 2025. US Securities and Exchange Commission.
- Henderson, J. C. and Venkatraman, N. (1993). Strategic alignment: Leveraging information technology for transforming organizations. IBM Systems Journal 32(1); reprinted in IBM Systems Journal 38(2&3), 1999.
Tools to try
- Business model canvas builderFramework: Business Model Canvas
- Change readiness checkFramework: Kotter's 8-Step Change Model
- Ansoff move finderFramework: Ansoff Matrix
- Five Forces scorerFramework: Porter's Five Forces
- SMART goal builderFramework: SMART Goals
- SWOT builderFramework: SWOT Analysis
More from Stratrix
“What did the decision you did not take actually cost?”
One decision per pack: the framework, a working model, the sourced cases and the board material.
See the pack — $499 →Test a decision, free
Set a live decision against the companies that made it before you.
AcquisitionsThe Distance TestDivestituresThe Divestiture TestDiversificationThe Diversification TestMake or buyThe Make-or-Buy TestStratrix Team
Every Casebook, three Strategy Packs a seat each year and Ask Stratrix, for teams that face these decisions all year.
$1,999 a year · $499 a seatWhat is included →Weekly email
Stratonomics, every Tuesday
One data story every Tuesday: what happened, what it means, and the figures you can quote. Free.