How a struggling pizza chain rebuilt itself as a technology company — and why the lesson matters more to legacy operators than to consumer brands.
In the late 2000s, Domino's Pizza was a mid-sized quick-service pizza chain with a brand promise most consumers no longer believed. Sales were flat, share was under pressure, and the operating model was still organised the way a pizza company had been organised for decades — franchised stores, phone orders, paper coupons, and a national marketing engine.
The publicly-documented problem was not that Domino's had bad technology. It was that the enterprise operating model was structurally incompatible with how consumer buying was moving. Ordering, delivery logistics, franchisee operations, marketing attribution and product feedback all lived in separate systems and separate reporting lines. Business press coverage from the period consistently frames the pre-turnaround state as an operator whose weakness was not tooling but coordination.
Under Patrick Doyle, who became CEO in 2010, and continued under his successors, Domino's reframed its own identity — publicly describing itself as a technology company that happens to sell pizza. The change was operating-model deep, not marketing-deep. Digital ordering became the primary interface. Store operations, franchisee tooling, delivery logistics and customer data were rebuilt around a single technology spine. The AnyWare programme allowed ordering across a wide range of channels. Investment in delivery, tracking and store-level analytics was funded as core capability rather than IT overhead.
Business press and Domino's own investor communications have widely documented digital ordering rising to the majority of sales in the years following the transformation, and a step-change in shareholder value across the 2010s. **JETTIFI ANALYSIS:** the durable outcome, distinct from the stock story, is that Domino's Pizza continues to be described as a technology company — a self-identity change that most legacy operators find harder than any specific technology project.
The most instructive part of the case is not the digital-first ordering interface. It is that Domino's chose to be a technology company. The operating model, hiring, capital allocation, franchisee incentives, executive scorecard, and public identity all realigned around that single decision. Everything else — the AnyWare channel investments, the store-level analytics, the delivery tracking — follows from that operating-model choice. A different leader, with the same technology budget, could have shipped ordering apps and remained a pizza company with an ordering app.
The reengineering lesson is that identity is an operating-model decision. If the leadership team decides the enterprise is a technology company, the operating model has to be reengineered to make that decision true — capital, incentives, hiring, decision rights, executive scorecard. If leadership will not make that identity decision, buying more technology will not compensate.
For a legacy operator — a distribution business, a family-owned manufacturer, a mid-market services firm — the practical implication is not that every business should call itself a technology company. It is that leaders should ask whether their existing identity is compatible with the operating model that digital execution requires. If the identity is 'we are a pizza company that uses digital tools', the operating model will keep resisting the transformation. If the identity is 'we are a technology-enabled operator of this business', the operating model naturally reengineers around it.
**JETTIFI RECOMMENDATION:** approach a case like this by starting at the operating-model layer, not the technology layer. Frame the diagnostic as: what identity is this leadership team willing to make binding? Then reengineer the operating model to make that identity true — capital allocation, decision rights, executive scorecard, hiring pattern — and only then commit to the technology decisions. Jettifi's delivery model, senior core plus specialists, is designed for exactly this class of engagement: the client does not need to hire an army of engineers to make the transformation stick.
Discuss your operating-model constraint
Talk to Jettifi →For the underlying working paper, read The Digital Reengineering pillar. For the executive edition, read the Guide. Site name: Jettifi.