The Giant's Small Computer
This note reveals the outcome. Participants should decide the case first, on their own devices, before the discussion.
- Who it was
- IBM, 1980
- The question
- How do you build a personal computer quickly enough to matter, without giving away the future?
- What they chose
- Assemble it from outside suppliers' parts, publish the technical design, and license an operating system from a small software firm.
- Judgement
- Mixed Sound process
- Session length
- 60 minutes, for 4 to 40 participants
Learning objectives
- Weigh speed to market against long-term control of a standard.
- Identify which parts of an open design are scarce and specific, and therefore where value will settle.
- Understand how an organisation built for one business struggles to move at another's pace.
Session plan
- Read the situation, what is known and unknown, and the voices in the room. No discussion yet.
- Each participant chooses an option on the case page, states a confidence and writes a one-line pre-mortem: if this choice fails, the most likely reason is…
- Debate by option. Ask each group to name which component of the machine it would insist on owning, and why.
- Reveal the outcome.
- Map the value chain of the personal computer after launch: who captured value, and why? Distinguish the decision to use outside parts from the decision to license them non-exclusively.
- Transfer: participants identify the scarce, specific part of their own product or platform.
The case page records each participant’s choice, confidence and pre-mortem in their own browser, and scores the confidence once the outcome is revealed. Nothing is sent anywhere, so it can be used in any classroom.
Questions before the reveal
- What does the company lose if it takes three years to build a machine its usual way?
- If you assemble from outside parts, which supplier becomes most powerful, and how could you prevent it?
- Is waiting for the market to mature a strategy or a delay?
Questions after the reveal
- The machine set the industry standard. Why is the outcome judged mixed rather than a success?
- Was the mistake openness itself, or the terms of the licences for the processor and the operating system?
- What would a version of the decision that kept the speed but more of the value have looked like?
The key facts on one page
- The machine launched in 1981 and became the industry's standard design.
- Its open design and non-exclusive licences let clone makers and the processor and operating-system suppliers capture most long-term value.
- The company sold its personal computer business in 2005.
Where discussions go wrong
- Concluding that openness was a mistake. Openness won the market; the loss came from who controlled the scarce parts.
- Ignoring the speed constraint. The closed option might have produced a better machine too late to matter.
The forces at work
- Speed versus control: Buying parts from the market was far faster than building them, and the cost of dependence on suppliers seemed small when the market was small. The supplier relationships later turned out to be where the value concentrated.
- Irreversibility hidden in openness: Publishing the design and accepting a non-exclusive software licence were hard to reverse. Once the standard spread, attempts to take back control met resistance from the very ecosystem that openness had created.
- An organisation built for something else: A small, separate team was set up away from headquarters precisely so it could act unlike the rest of the company. Its product reflected that independence, for good and ill.
- Path dependence: Once software and add-ons were written for the design, the standard locked in, independent of who made the machine.
Openness can win a market; whoever controls the scarce, specific parts of an open standard keeps the value.
Pairs well with: The strategy question “Should we open our platform to outsiders?” and the pattern Compatibility becomes gravity.
Where this comes from
Sources
- IBM, “The IBM PC's debut,” IBM History.
- Paul Carroll, Big Blues. The Unmaking of IBM (Crown, 1993).
- Paul Freiberger and Michael Swaine, Fire in the Valley, 2nd ed. (McGraw-Hill, 2000).
- James Chposky and Ted Leonsis, Blue Magic. The People, Power and Politics Behind the IBM Personal Computer (Facts on File, 1988).
Teaching note by Shrikant Kumar. Free to use in classrooms and workshops with attribution.
Shrikant Kumar. “Teaching note: The Giant's Small Computer.” Decide case teaching note, Telos. https://shrikantk.com/decide/the-giants-small-computer/teaching/