Strategy vs Arithmetic
The distinction between strategy and arithmetic organizes Prahalad's entire engagement with corporate response to technological change. Arithmetic operates within fixed boundaries, taking existing work as given and asking how many people are required to execute it. Strategy operates at the boundary itself, asking what new work should be done that could not be done before. Every generation of technology improvement creates a moment when operational effectiveness appears to be the urgent priority while strategic positioning appears to be a luxury — and every generation, the organizations that prioritize operational effectiveness are displaced by those that prioritize strategic positioning, because efficiency gains are temporary while capability developments compound.
In the AI Story
The arithmetic is always right about the current paradigm and always wrong about the next one. Kodak optimized film production with extraordinary efficiency while digital photography rendered the optimization irrelevant. The efficient horse-and-buggy manufacturers were destroyed by organizations that recognized the automobile as a platform for capabilities the horse-based economy could not conceive. VisiCalc, the first spreadsheet, arrived in 1979, and accountants saw it the way weavers had seen the power loom — but fifteen years later, more people worked in accounting-related fields than before the spreadsheet existed, earning more, working on problems requiring judgment rather than computational stamina.
Prahalad pressed the distinction into specific institutional architecture. Operational effectiveness produces quarterly improvements; strategic positioning produces decades. The organizations that built durable competitive positions did so by asking what new core competencies the new technology enabled and what markets those competencies would open — not by asking how many people were needed to continue doing what was already being done.
Resource leverage — the creative discipline of getting the most from the least by developing new capabilities with existing resources — distinguishes the strategic response from the arithmetic one. The arithmetic path reduces the organization; the strategic path transforms it. Prahalad's line: the goal is not to be a smaller version of what you were, but to become something qualitatively different.
Origin
The distinction runs through Prahalad's work from the 1990 HBR article to the 2004 bottom-of-the-pyramid research, consistently applied to cases where organizations mistook efficiency for strategy and paid for the mistake with their futures.
Key Ideas
Fixed boundaries vs boundary itself. Arithmetic operates within given frames; strategy operates on the frames themselves.
Efficiency is temporary. Cost reductions compound briefly; capability developments compound durably.
The quarterly trap. Operational metrics reward what strategy cannot yet measure.
Capability expansion over workforce contraction. The strategic response uses productivity gains to develop new competencies.
Historical pattern. Every transition punishes organizations that optimize their way into obsolescence.
Appears in the Orange Pill Cycle
Further reading
- Porter, Michael. What Is Strategy? (Harvard Business Review, November 1996).
- Prahalad, C. K. & Hamel, Gary. Strategic Intent (Harvard Business Review, May-June 1989).
- Christensen, Clayton M. The Innovator's Dilemma (Harvard Business Review Press, 1997).