🧠 What Is Design Thinking
Design Thinking isn’t a rigid methodology. It’s a approach to solving problems that puts people at the center of every decision. It grew out of the work of IDEO, a design consultancy founded by David Kelley, and was formalized by Tim Brown as a discipline that uses a designer’s sensibility and methods to meet people’s needs with what is technologically feasible and commercially sustainable.
📖 Tim Brown’s Definition
"Design thinking is a human-centered approach to innovation that draws from the designer's toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success."
Tim Brown, IDEO CEO, in “Change by Design” (2009)
Stanford d.school (Hasso Plattner Institute of Design) turned Design Thinking into an academic discipline in the 2000s, creating the 5-step model that became a global reference. The key point: unlike linear engineering processes, DT is iterative and nonlinear. You can (and should) return to earlier stages when you discover something new.
📊 Adoption Data
- 85% of Fortune 500 companies use some form of Design Thinking (Forrester, 2023)
- 6x higher return on investment in projects that use DT vs. traditional approaches (McKinsey Design Index)
- 71% of teams report improved collaboration after adopting DT (IBM Enterprise Design Thinking)
- $20M+ in annual savings reported by IBM with its Enterprise Design Thinking framework
Desirability
What do people want?
Feasibility
Is it technically possible?
Sustainability
Is it financially viable?
Innovation
The intersection of all 3
🔄 The 5 Stages of Design Thinking
The Stanford d.school model organizes Design Thinking into 5 steps that form an iterative process. The “double diamond” format (diverge-converge twice) captures the essence: first broaden your understanding of the problem, then focus on defining the right one; then explore possible solutions, and finally converge on the best one.
Empathize
Immerse yourself in the user's world
Observe, interview, and experience the user’s journey. It’s not about asking “what do you want?” but about understanding real behaviors, pain points, and motivations. Tools: in-depth interviews, shadowing, usage diaries, empathy maps.
Define
Synthesize insights into a clear point of view
Turn empathy data into a “Point of View” (POV) and “How Might We” statements. The quality of the problem definition determines the quality of the solutions. Tools: personas, user journey, POV statement, HMW questions.
Ideate
Generate volume before filtering
Diverge radically: quantity over quality. Defer judgment, seek wild ideas, and build on other people’s ideas. Tools: structured brainstorming, Crazy 8s, SCAMPER, forced analogies, brainwriting 6-3-5.
Prototype
Make it tangible so you can test it
Build quickly, cheaply, and imperfectly. The prototype isn’t the product: it’s a question made tangible. The sooner and more cheaply you fail, the more you learn. Tools: paper prototype, storyboard, role-play, wireframe, physical model, low-fidelity digital prototype.
Test
Validate with real users
Put the prototype in the user’s hands and observe. Don’t defend the idea: listen. The goal isn’t to "approve" the prototype, but to learn what works and what needs to change. Each test can take you back to any previous step.
🛠️ Practical Tools for Each Stage
Each Design Thinking stage has specific tools. You don’t need to use them all in every project. The important thing is choose the right tool for the right moment. Here are the most widely used and proven ones in corporate settings.
👁️ Empathy Map
A board divided into 4 quadrants that organizes what you learned about the user:
Think and Feel
Concerns, aspirations, fears. What really matters?
Sees
Environment, friends, market. What does your surroundings offer?
Listen
Influences, media, peers. Who influences decisions?
Talk and Do
Public behavior, attitude. Observable actions.
👤 Persona
A semi-fictional representation of the ideal user based on real research data. A persona has a name, photo, demographic data, goals, frustrations, and a "summary statement." The key: a persona isn't fantasy. It's a synthesis of interviews and observations.
💡 Practical Tip
Limit yourself to 2-3 personas per project. More than that dilutes the focus. If every decision serves every persona, no persona is truly guiding the design.
❓ How Might We (HMW)
"How might we...?" questions that reframe the problem as an opportunity. The wording matters: too broad ("How might we improve people's lives?") leads to vague answers. Too narrow ("How might we add a blue button?") limits creativity.
// Too broad:
"How might we improve the customer experience?"
// Calibrated:
"How might we reduce customer anxiety while they wait between placing an order and receiving it?"
// Too narrow:
"How might we send a confirmation text message?"
⚡ Crazy 8s
Fold an A4 sheet into 8 quadrants. Set a timer for 8 minutes. Draw 8 different solutions (1 per minute). The time pressure forces your brain out of its comfort zone and into exploring radical alternatives. It works best in a group: each participant generates 8 ideas, then the team votes on the best ones.
⚖️ When to Use and When Not to Use
Design Thinking isn’t a silver bullet. It works extremely well for certain types of problems and can be a waste of time for others. Knowing when to apply and just as important as knowing how.
✓ Use Design Thinking When
- ✓ The problem is ambiguous or poorly defined
- ✓ You don't know who the real user is or what they need
- ✓ Existing solutions don’t work, and no one knows why
- ✓ Needs radical innovation, not incremental
- ✓ Multidisciplinary teams need a common language
✗ Don’t Use Design Thinking When
- ✗ The problem is technical and well-defined (bug, system failure)
- ✗ There is extreme urgency (hours, not days)
- ✗ The solution is already known and validated (optimize, don’t reinvent)
- ✗ Regulatory constraints eliminate solution spaces
- ✗ Leadership wants “innovation theater” with no intention of changing
⚠️ Common Trap
"Design Thinking Theatre": workshops with colorful sticky notes that generate excitement but zero implementation. If there's no commitment to test and iterate after the ideation session, you're putting on a show, not doing Design Thinking. The value is in iteration, not the sticky note.
🛒 Case Study: IDEO and the Shopping Cart Challenge
In 1999, ABC Nightline challenged IDEO to redesign the shopping cart in just 5 days. The episode became the most famous Design Thinking case in history and is still studied at business schools around the world.
Day 1: Field empathy
Observation and immersion
The team of designers, engineers, and specialists visits supermarkets. They observe shoppers, employees, and children. They discover that 22,000 children get injured each year in shopping carts; no one knows where they left their cart in the parking lot; the wheels get stuck; cart theft costs millions.
Day 2: Full divergence
Ideation in multidisciplinary groups
Brainstorm with clear rules: build on others’ ideas, defer judgment, aim for volume. “One conversation at a time” rule. Teams focused on topics: child safety, storage, checkout, navigation. Hundreds of ideas generated.
Days 3–4: Rapid prototyping
From a drawing to a physical object
Democratic voting on the best ideas. Building functional prototypes with simple materials. Constant iteration: "if you can’t build it in an hour, simplify it." A real physical cart prototype with removable baskets, a built-in scanner, and anti-tip design.
Day 5: Presentation and test
Functional prototype in 5 days
Final cart: a modular structure with removable baskets (each person takes one, shops, and returns it to the frame), a scanner for self-checkout price lookups, and a design without a fixed child seat (making it impossible to carry a child in a dangerous position). It wasn’t perfect. It was a vehicle for learning.
💡 Main Lesson
The final result wasn’t the point. IDEO demonstrated that a multidisciplinary team using Design Thinking can arrive at radically different solutions in days, not months. The methodology is the product. The shopping cart is a byproduct.
🏢 Design Thinking in Corporate Practice
Applying DT in companies is different from an academic workshop. In a corporate environment, you deal with internal politics, budgets, hierarchy, and inertia. Here’s how to adapt without losing the essence.
🏗️ IBM Enterprise Design Thinking
IBM adapted Design Thinking for enterprise scale with 3 additions to the classic model:
- • Hills: User-focused statements of intent (“Who + What + Wow”). They align large teams around a measurable outcome.
- • Playbacks: Regular alignment with stakeholders. It’s not “manager approval”—it’s synchronizing understanding. It prevents surprises.
- • Sponsor Users: Real users who actively participate in development. They aren’t “passive interviewees”—they’re co-creators with a voice in the process.
📋 Design Thinking Sprint for Corporate
Week 1
Empathy + Definition. Interviews with 5-8 users. Synthesis into personas and HMW.
Week 2
Ideation + Prototyping. Crazy 8s with the team. Low-fidelity prototype.
Week 3
Test + iteration. Validation with 5 users. Adjustments and a pivot/move-forward decision.
✓ Success Factors
- ✓ Executive sponsorship (someone with the power to implement)
- ✓ Multidisciplinary team (not just designers)
- ✓ Dedicated physical/virtual space
- ✓ Direct access to real users
✗ Frequent Mistakes
- ✗ A 1-day workshop with no follow-up (theater)
- ✗ Skip empathy and go straight to ideation
- ✗ A “perfect” prototype that no one dares to criticize
- ✗ Use DT to validate a decision that has already been made
📋 Module Summary
Next Module:
2.2 - Lean Startup: from concept to MVP with Eric Ries