Design thinking is everywhere now — in business schools, corporate innovation labs, government agencies, even kindergartens. It started in one design firm in Palo Alto. IDEO’s design thinking history is the story of how a specific way of working became a global framework, and how much of that spread depended on decisions that had nothing to do with methodology at all.
1. Where IDEO Came From
IDEO was formed in 1991 through the merger of David Kelley Design, ID Two (Bill Moggridge’s firm), and Matrix Product Design. Kelley was a Stanford-trained engineer-designer. Moggridge had designed the Grid Compass, arguably the first laptop computer. The merger created a firm with genuine engineering depth alongside design capability, at exactly the moment Silicon Valley was beginning to need both in the same room.
The firm’s early work, designing Apple’s first mouse, medical devices, and consumer electronics, established a working methodology that was less about style and more about starting with people. What do users actually do? What problems do they have that they haven’t articulated themselves? What would they use if it existed but doesn’t yet? These became the foundational questions of what would eventually be named design thinking.
2. The ABC Shopping Cart: Design Thinking’s Public Debut
In 1999, ABC News Nightline gave IDEO five days to redesign a shopping cart from scratch, and filmed the entire process. The resulting episode remains one of the most-watched introductions to design methodology ever broadcast. The team observed shoppers, rapidly built physical prototypes, iterated visibly on camera, and produced a working redesign in five days. The process itself, observe, define, ideate, prototype, test, turned out to be more interesting to viewers than the cart.
This broadcast gave design thinking a mainstream audience for the first time. More importantly, it gave business leaders a visual model for how a design process actually worked, which is precisely what made it possible to sell design thinking as a business methodology rather than a purely creative discipline.
Observe — watch real users in their actual context, not a lab simulation of it.
Define — turn observations into a specific, actionable problem statement.
Ideate — generate volume before judging quality.
Prototype — build the smallest thing that can be tested.
Test — put it in front of real users and watch, again.
3. The d.school and the Spread to Business Education
David Kelley founded the Hasso Plattner Institute of Design at Stanford, known as the d.school, in 2004. By embedding design methodology inside one of the world’s most influential engineering and business universities, IDEO’s approach gained academic legitimacy and a direct channel into the pipeline of future business leaders. McKinsey, IDEO’s consulting counterpart in a different industry, began offering design thinking services of its own. Harvard Business Review published extensively on the topic. From there, the diffusion largely took care of itself.
Why an Engineering-Design Firm, Not a Business School, Started This
It’s worth noting that design thinking didn’t originate as an academic theory looking for practitioners — it originated as a working method inside a firm that had to ship real products under real constraints, and only later got formalized and taught. That order matters: the framework survived contact with business education specifically because it had already survived contact with manufacturing, budgets, and users.
💡 Pro tip — When introducing design thinking to a non-design team for the first time, start with the observe-and-define stages only, and stop there for the first project. Teams that jump straight to ideation and prototyping without first sitting with real user observation tend to reproduce their existing assumptions in a slightly different visual form, missing the entire point of the method.
4. Why the Methodology Spread So Far
Design thinking spread beyond design partly because it was genuinely useful outside design contexts, and partly because it was packaged in a form non-designers could learn without years of visual training. The five-step cycle is teachable in a workshop; the taste and craft that separate good design outcomes from mediocre ones are not, and that gap between the teachable process and the harder-to-teach judgment is a common source of frustration when organizations expect the framework alone to produce design-quality results.
The most common mistake organizations make today is adopting the vocabulary of design thinking, sprints, personas, empathy maps, without the underlying discipline of actually watching real users before deciding anything. The framework is only as good as the observation it’s built on.
Closing thoughts
Design thinking’s spread from one Palo Alto firm to a global vocabulary wasn’t accidental — it took a public demonstration, an academic home, and a genuinely teachable structure. What’s easy to forget, thirty years on, is that the structure was built to solve real product problems first, and taught only after it worked.
Design Daily Life · Notes on design, daily