A Brief Introduction to Design Thinking

Unlocking Innovation in New Product Development

By Carlos Uribe, Inspired by Michael G. Luchs’ Chapter in “Design Thinking Introduction”

In today’s fast-evolving business landscape, innovation isn’t just a competitive advantage—it’s a necessity. Companies across industries are turning to design thinking as a powerful approach to tackle complex challenges, especially in new product development (NPD) and innovation. But what exactly is design thinking? Is it just a buzzword, or does it offer real value?

Drawing from Michael G. Luchs’ insightful chapter in A Brief Introduction to Design Thinking, this blog post unpacks the core concepts, framework, and mindset behind design thinking—offering practical guidance for teams looking to innovate with purpose and empathy.

What Is Design Thinking?

At its heart, design thinking is a creative, systematic, and collaborative problem-solving approach. It means approaching challenges the way a designer would: with curiosity, empathy, and a willingness to experiment.

Unlike traditional linear processes like the Stage-Gate™ model, where development follows a rigid sequence and prototyping happens late in the cycle, design thinking embraces nonlinearity and iteration. It encourages teams to quickly generate ideas, build simple prototypes, gather feedback, and refine solutions—early and often.

This makes design thinking particularly effective when:

• The problem is unclear or poorly defined.
• You’re aiming for breakthrough innovations—not just incremental improvements.
• Customer needs are uncertain or latent (i.e., needs customers can’t easily articulate).
  

For example, in emerging markets like wearable biometric devices, where user behaviors and expectations are still forming, design thinking helps uncover hidden opportunities that traditional market research might miss.

—

When Should You Use Design Thinking?

While design thinking shines in ambiguous or high-potential innovation spaces, it’s not always the right fit for every project.

Best suited for:

• Creating new markets
• Developing radical innovations
• Exploring unmet or undiscovered customer needs
• Business model design (as explored in Chapters 18 and 19)
  

Less ideal for:

• Incremental improvements (e.g., increasing fuel efficiency in engines)
• Well-defined problems with clear solutions
  

That said, even in traditional NPD projects, elements of design thinking—like empathy-building or rapid prototyping—can enhance outcomes.

One key benefit? It avoids the “big bet” trap—investing heavily in a single solution too early. Instead, design thinking promotes “little bets” (Sims, 2013): low-risk experiments to test ideas, gather insights, and converge on high-potential concepts efficiently.

Think of design thinking as a clarifying lens for the “fuzzy front end” of product development—helping teams explore, learn, and define the right problem before diving into full-scale development.

A Simple Framework for Design Thinking

To make sense of the many tools and methods associated with design thinking, Luchs proposes a clear, four-mode framework organized into two major phases: Identify and Solve.

This visual (Figure 1.1) shows the four modes:

• Discover → Define → Create → Evaluate
  

Let’s walk through each mode.

—

Phase 1: Identify – Finding the Right Problem

Most teams jump straight into solving problems. But design thinking emphasizes: Are you solving the right problem?

1. Discover Mode

The goal? Gain deep customer insights by immersing yourself in their world.

Instead of asking, “How can we improve our product?” ask, “What are our customers really struggling with?”

This mode relies on qualitative research methods to build empathy:

• Ethnographic observation
• In-depth interviews
• Journey mapping
• Empathy maps and personas (covered in Chapters 3, 4, and 7)
  

Crucially, data collection and synthesis happen iteratively. You don’t wait until the end to analyze. You constantly translate observations into insights—refining your understanding as you go.

2. Define Mode

Now, distill those insights into clear problem statements.

A strong problem statement includes:

• Who the customer is
• What unmet need they have
• Why it matters (the insight)
  

For example:

“A busy parent of teenagers needs a way to reconcile and integrate the dynamic schedules of all family members because the lack of reliable, up-to-date information leads to missed activities and unnecessary stress.”

This reframing turns vague frustrations into actionable challenges. Teams then use techniques like multivoting to prioritize which problems to tackle first.

Phase 2: Solve – Creating and Testing Solutions

3. Create Mode

Now it’s time to brainstorm and prototype.

Two core activities:

1. Idea Generation – Use techniques like brainstorming, mind mapping, or SCAMPER (Chapters 5 and 6) to explore possibilities.
2. Prototyping – Build low-resolution prototypes: rough models, storyboards, or role-plays that simulate the user experience.
   

These aren’t polished products—they’re tools for learning. A paper mockup of an app, a cardboard model of a device, or even a role-played service interaction can spark rich feedback.

And remember: prototyping isn’t the final step—it’s part of the ideation process. You might cycle through several versions internally before showing them to users.

4. Evaluate Mode

Now, test your prototypes with real users.

But don’t just ask, “Do you like this?” Instead, observe how people interact with the prototype. Watch for surprises, confusion, or delight.

Then, synthesize the feedback—just like in the Discover phase. Look for:

• New insights
• Confirmation (or contradiction) of assumptions
• Opportunities to refine or pivot
  

Importantly, this isn’t the end. Evaluation feeds back into earlier modes. You might return to Discover if new customer behaviors emerge, or go back to Create with an improved concept.

Design Thinking Is Not Linear—It’s Iterative

While the framework is presented in sequence, design thinking is inherently non-linear. Think of the four modes as spaces to move between, not steps to check off.

Teams might:

• Jump from Evaluate back to Define after user feedback
• Revisit Discover to explore a newly uncovered need
• Cycle through Create and Evaluate multiple times
  

This flexibility allows teams to learn quickly, fail early, and adapt—minimizing wasted resources and maximizing the chances of breakthrough success.

The Mindset of Design Thinking

Beyond tools and processes, design thinking is a mindset—a way of thinking and acting. Luchs highlights several key principles:

1. People-Centric
   Focus on human needs, not just products or technology. Let customer insights drive solutions.
   
2. Cross-Disciplinary & Collaborative
   Build diverse teams—engineers, marketers, anthropologists, designers. Invite external voices (customers, experts) when needed.
   
3. Holistic & Integrative
   See the big picture. Connect seemingly unrelated ideas. Understand how parts interact within a system.
   
4. Flexible & Comfortable with Ambiguity
   Embrace uncertainty. Be ready to pivot. There’s no fixed roadmap—only learning and adaptation.
   
5. Multimodal Communication
   Think with your hands. Sketch, build, act it out. You don’t need artistic skill—just the willingness to express ideas visually and physically.
   
6. Growth Mindset
   View failure as learning. Test boldly. Iterate fearlessly.
   

—

Design thinking and its phases

Here’s a clear, concise table summarizing all 5 core phases of Design Thinking (based on the d.school framework), including key goals, activities, purpose, and examples:

Design Thinking Phases Overview

Phase	Goal	Key Activities	Purpose	Example
1. Empathize	Understand users deeply	• User interviews • Observation • Immersion in user context • Shadowing	Set aside assumptions; gain genuine insights into user needs, emotions, and pain points	Watching nurses struggle with clunky hospital software during night shifts.
2. Define	Frame the right problem	• Synthesize research data • Identify patterns • Craft a POV statement	Turn insights into a human-centered problem statement (actionable & specific)	“Overwhelmed ER nurses need a way to quickly log critical patient vitals during emergencies to reduce errors and save time.”
3. Ideate	Generate diverse solutions	• Brainstorming • Worst-possible idea • Mind mapping • Sketching	Explore quantity over quality; encourage wild ideas without judgment	Generating 50+ solutions: voice commands, wearable scanners, color-coded alerts.
4. Prototype	Make ideas tangible for testing	• Low-fidelity mockups (paper, digital wireframes) • Role-playing • Storyboards	Fail fast, learn faster; test concepts cheaply before heavy investment	Building a paper prototype of a new app interface to simulate data entry.
5. Test	Validate solutions with real users	• User testing sessions • Feedback interviews • Iterative refinement	Gather insights to refine the solution (or redefine the problem!)	Nurses test the paper prototype; reveal they need one-handed operation due to holding medical tools.

Critical Notes (Included for Accuracy):

• Non-Linear & Iterative: Arrows flow → but teams often loop back (e.g., testing may reveal flawed assumptions → return to Empathize or Define).
• Human-Centered: Every phase prioritizes real user needs over technical/business constraints.
• Collaboration: Requires diverse teams (designers, engineers, end-users, stakeholders).
• No “Final” Phase: Testing often leads to new iterations → continuous improvement.
• Beyond 5 Phases: Some models add “Implement” (for scaling solutions), but core innovation happens in these 5.
  

Why This Structure Works:

• Empathize → Define: Ensures you solve the actual problem (not just symptoms).
• Ideate → Prototype → Test: Turns abstract ideas into validated solutions through rapid learning.
• Cycling Back: If testing fails, you don’t restart—you refine based on evidence (e.g., redefine the problem after user feedback).
  

Real-World Insight: 87% of design-driven companies (like Apple, Airbnb) iterate through these phases 3-5x before launching a solution (Source: Design Management Institute).

Final Thoughts: Design Thinking as a Launchpad for Innovation

Design thinking isn’t a magic formula—it’s a disciplined approach to innovation that balances creativity with structure. It helps teams:

• Start with empathy, not assumptions
• Define the right problem, not just solve the obvious one
• Prototype early, learn fast, and iterate often
• Stay flexible, while moving toward a viable solution
  

As Luchs notes, design thinking often precedes traditional Stage-Gate processes. It clarifies the path forward so that once development begins, it’s grounded in real customer value.

Whether you’re launching a new product, reimagining a service, or exploring a new business model, design thinking offers a proven path to innovation that’s human-centered, collaborative, and impactful.

Inspired by Michael G. Luchs’ chapter in “A Brief Introduction to Design Thinking.” For deeper dives into tools, case studies, and implementation strategies, explore the full book—your roadmap to mastering innovation in the 21st century.

“Design thinking is not about design. It’s about using the designer’s sensibility to match people’s needs with what is technologically feasible and what a viable business strategy can convert into customer value and market opportunity.”
— Tim Brown, IDEO (paraphrased in spirit)

Let’s start designing not just products—but better experiences.