IDEO — the firm that popularized design thinking — shrank from 725 to 350 employees. Revenue collapsed from $300M to $100M.
https://www.ideo.com/
This is not a design industry story. This is a story about what happens when an entire profession confuses method with the eye.
And it's coming for engineers next.
What Killed IDEO
For two decades, IDEO was the gold standard of innovation consulting. They packaged design thinking into workshops, toolkits, and frameworks — and sold it to Fortune 500 companies worldwide.
The problem? Methods can be copied. And now, methods can be automated.
When every consulting firm, every MBA program, and eventually every AI tool could run a design thinking workshop, IDEO's value proposition evaporated. They had sold the package, not the perception.
Tim Brown, IDEO's longtime CEO, stepped down in 2023. The company that defined an era couldn't survive the consequences of its own success.
The Eye vs. The Method
Here's the distinction that matters — not just for designers, but for every knowledge worker:
The Method is the repeatable process. The framework. The toolkit. The workflow.
The Eye is the ability to look at a situation and see what others don't. To strip away surface-level noise and extract the underlying structure. To know what to build before anyone asks how to build it.
IDEO sold the method. The designers who survived the collapse were the ones who had the eye.
This maps directly to what's happening in engineering right now.
Why This Matters for Engineers
Consider what AI can already do in 2026:
- Write functional code from natural language descriptions
- Debug, refactor, and optimize existing codebases
- Generate entire applications from a single prompt
- Translate between programming languages
- Write tests, documentation, and deployment scripts
All of these are methods. They are the "how" of engineering.
What AI cannot do:
- Look at a business problem and identify the right technical architecture
- Judge which trade-offs matter for this specific context
- Recognize when a requirement is based on a false assumption
- See the second-order consequences of a design decision
- Know when not to build something
This is the eye. And it is the only thing that will not be automated.
The engineers who define themselves by the languages they know, the frameworks they use, or the tools they operate — they are IDEO. They have packaged their skills into a method, and that method is now being absorbed by AI at an accelerating rate.
The engineers who define themselves by their ability to see structure where others see chaos — they will thrive.
The IDEO Paradox: Value Goes Up, Revenue Goes Down
Here's the most counterintuitive finding from studying IDEO's collapse:
The value of design in business has never been higher. McKinsey's Design Index study showed that design-led companies outperformed the S&P 500 by 219% over a ten-year period.
Yet the firms that sold design as a service are dying.
Why? Because when a discipline becomes essential, it gets absorbed into the core of every organization. It stops being something you outsource. Design moved from being an external service (IDEO) to an internal capability (every product team now has designers).
The same thing is happening with AI engineering. When AI-assisted coding becomes table stakes — and it will — the value of "knowing how to code" as a standalone skill collapses. Not because coding becomes worthless, but because it becomes ubiquitous. Like literacy. Essential, but no longer differentiating.
What differentiates is the eye.
From Design Thinking to Thinking About Design
Nigel Cross, one of the most influential design researchers, spent decades studying how expert designers actually think. His conclusion: great designers don't follow a process. They see differently.
They look at a problem and immediately perceive structure — constraints, affordances, relationships — that novices simply cannot see. This perception isn't learned through workshops. It's developed through years of crossing boundaries between disciplines, failing in real projects, and building a mental library of structural patterns.
Donald Schön called this "reflection-in-action" — the ability to think and adapt while doing, not just before or after. Kees Dorst described it as "frame creation" — the ability to redefine the problem itself, not just solve the problem as given.
These are not methods. They cannot be packaged. They cannot be automated.
They are the eye.
What You Can Do
If you're an engineer reading this, here's the uncomfortable question:
Can you describe your value without referencing a specific technology, language, or framework?
If your answer starts with "I'm a React developer" or "I specialize in Kubernetes" or "I build data pipelines" — you are describing a method.
If your answer starts with "I look at complex business problems and find the simplest technical structure that solves them" — you are describing the eye.
The transition from method to eye is not a weekend workshop. It requires:
- Crossing boundaries. Work at the intersection of business, technology, and creativity — not in the silo of one discipline.
- Engaging with first-order sources. Read the original research, not the summary. Understand why an architecture works, not just how to implement it.
- Building judgment through failure. The eye is sharpened by encountering problems where the method breaks down.
- Thinking in structures, not features. Train yourself to see the underlying architecture of every problem, every market, every organization.
The Book (Free, Open-Source)
I wrote a 6-chapter book exploring this structural shift in depth:
"The Redesign of Design Strategy — Why Design and Business Are the Same Cognitive Process, and What Remains After AI Takes Execution"
It covers the rise and fall of design firms, the academic research on how experts actually think (Cross, Schön, Dorst), the specific mechanisms through which AI is compressing workflows, and what "the eye" looks like in practice.
The book is published under CC BY 4.0 — completely free, open-source, and available in both English and Japanese.
📖 GitHub: Leading-AI-IO/design-strategy-in-the-ai-era
The question is not whether AI will take your job. The question is whether you have the eye — or just the method.
About the author: Satoshi Yamauchi is an AI Strategist and Business Designer at Sun Asterisk, and the founder of Leading AI. He has published 8 open-source books on AI strategy, business design, and the future of knowledge work under the Leading-AI-IO GitHub organization. His Palantir Ontology analysis ranks #1 on Google globally.
Top comments (0)