How Product Discovery Frameworks Like Design Thinking have Evolved

Matt Hicks

4 months ago

Product discovery refers to the critical upfront work of identifying and validating customer needs, problems, and potential solutions before diving into building a product. While there are many discovery frameworks, design thinking has emerged as one of the most popular.

First championed by IDEO and Stanford’s d.school, design thinking brings together principles like empathy, collaboration, and rapid prototyping to deeply understand users and generate innovative new product ideas. Design thinking has shaped how many organizations approach human-centric problem-solving and product development.

In this post, I’ll provide a brief history of design thinking and how it reimagined product discovery. I’ll then explore how design thinking has evolved over the past decade, with new variations, more focus on execution, and integration with agile development principles. Understanding how design thinking has adapted provides valuable context for product teams looking to leverage discovery frameworks.

Brief History of Design Thinking

The origins of design thinking trace back to prominent design firms like IDEO in the 1990s as well as Stanford University’s Institute of Design (d.school) founded in 2005. Design thinking aims to apply human-focused design principles to tackle complex business and social problems.

Four key principles characterize classic design thinking:

Empathy – Deeply understanding user needs and emotions through observation, engagement, and interviewing.
Collaboration – Bringing together diverse teams and perspectives to generate creative ideas. Utilizing group brainstorming and co-creation.
Experimentation – Quickly building prototypes and concepts to learn through hands-on testing vs just theorizing. FAIL often stands for “First Attempt In Learning.”
Optimism – Approaching problems with the fundamental belief that we can create impactful change.

Unlike analytical problem-solving, design thinking starts with people first. It relies on qualitative empathy rather than just data analysis. The process moves from inspirational divergent thinking to pragmatic convergent thinking.

Traditional design thinking frameworks consist of 5 core steps:

Empathize – Observe and engage with users to understand their needs.
Define – Synthesize insights into the core problems to address.
Ideate – Brainstorm a wide range of creative solutions.
Prototype – Build early concepts and experiential models to test hypotheses.
Test – Gather user feedback on prototypes to refine solutions.

This human-centric approach to product innovation has been hugely influential. However, as design thinking has expanded in adoption, its models have continued to adapt and evolve.

Expansion Beyond Digital Products

In the early days, design thinking was most commonly applied to digital products and software because of its roots in the tech space. However, as the approach spread, it was adapted for a much wider range of products and services.

For physical products, design thinking integrates 3D modeling and printing to build prototypes users can interact with. For service design, journey mapping and experience prototyping bring customer experiences to life.

This expansion has also put more focus on the holistic end-to-end customer journey. While digital teams previously focused mainly on apps and websites, design thinking today examines the full omnichannel ecosystem.

For example, in healthcare design thinking might explore patient experiences spanning multiple touchpoints:

Researching conditions online
Scheduling appointments
Interactions with doctors & nurses during visits
Managing prescriptions and insurance
Receiving follow-up care

This emphasis on complete user journeys beyond isolated products gives a broader perspective. Design thinking has proven effective across nearly any industry from consumer packaged goods to enterprise software and financial services. The frameworks flex to address varied user needs and business requirements.

Evolving Models and Variations

As design thinking grew in popularity during the 2000s and 2010s, many different models emerged. While rooted in the same core principles, adaptations added new dimensions.

Notable variations include

Stanford d.school Model: One of the most foundational models organized around understanding, observing, defining points of view, ideating, prototyping, and testing. Emphasis on rapidly cycling through steps.

IBM Design Thinking: Adds three phases before and after the core methodology – unmask needs, learn about users, and evaluate solutions. Focuses on tying to business outcomes.

SAP Design Thinking: Consists of 6 key steps – understand, observe, synthesize, ideate, prototype, validate. Very user research heavy.

IDEO Model: Outlines phases of inspiration, ideation, and implementation. More focused on innovation culture versus rigid processes.

Harvard Business School: Combines two models – understand, define, ideate, prototype, test, and empathy, define, ideate, prototype, test. Adds emphasis on empathy.

While steps may vary, all models aim to:

Deeply understand users (empathy)
Reframe the right problems to solve (define)
Explore many possible solutions (ideate)
Build quick experiments to test concepts (prototype)
Gather user feedback to refine (test)

The evolution shows just how flexible and adaptive design thinking frameworks can be. Teams can customize their approach while adhering to core principles.

Growing Focus on Implementation

A common criticism of design thinking has been that it provides high-level guidance but lacks concrete details on how to execute and implement solutions. As a result, newer models have more emphasis on turning insights into real-world outcomes.

Some ways design thinking has expanded implementation focus:

Detailed guidance on building an innovation team, skills, and culture
Incorporating experimentation and feedback loops post-discovery
Tools to quantify user insights and turn them into requirements
Planning the end-to-end innovation process from brief to launch
Building capabilities to sustain iteration after initial MVP
Measuring success through customer-centric rather than financial metrics
Tying to agile development methods to scale what works

Essentially, practitioners realized design thinking cannot end when the initial discovery phase completes. Turning insights into products requires detailed planning, execution, and collaboration across teams.

Leading design thinking consulting firms have focused on providing this bridging framework. They recognize that customer-obsessed cultures take time to build. Design thinking today covers the full lifecycle from upfront discovery through ongoing improvement.

Integrating with Agile and Lean

As design thinking has evolved, one of the biggest trends has been integrating it with agile and lean methodologies.

Initially, design thinking was positioned earlier in the innovation cycle for understanding users and identifying opportunities. Agile development came after to deliver working software through sprints.

However, newer hybrid models aim to connect the benefits of discovery with continuous delivery and improvement:

Discovery identifies the problem and solution hypothesis
Agile development tests and builds the minimum viable solution
Metrics are collected to validate learning
New iterations of discovery and development improve the product

Similarly, design thinking and lean startup principles have combined around the “build – measure – learn” loop:

Design thinking helps ideate potential solutions
Lean startup proposes to build an MVP version
Usage metrics provide learning on what resonates with users
Additional discovery and development continue the iteration

Together these approaches enable product teams to cycle rapidly between designing, testing with users, building, and gathering feedback.

Key is that design thinking is no longer a siloed upfront activity. Teams conduct micro-discovery sprints throughout development to keep honing the product experience. This end-to-end innovation lifecycle delivers great results.

The evolution shows how flexible and malleable design thinking is. Product teams can customize it to their needs rather than following a rigid playbook.

Key Takeaways on Evolving Nature

Product Discovery Frameworks and Design Thinking has clearly come a long way from its origins in software and digital product design. Some key takeaways on its evolution:

Applicable across many product domains: Product Discovery Frameworks have been adapted beyond digital to services, physical products, and full customer experiences.
New variations and steps: Many models have emerged with slight differences in steps and emphasis while retaining core principles.
Focus on implementation: Design thinking now includes more guidance on exactly how to build, launch, and scale innovative solutions.
Integration with agile: New hybrid processes connect upfront discovery with agile development to enable continuous deployment and learning.
Continuous innovation: Discovery sprints allow ongoing refinement versus just an initial upfront phase. The process never ends.
Customizable: Teams can tailor design thinking to their needs rather than follow a prescribed formula. It’s flexible.
Full lifecycle: Design thinking now covers the full journey from early problem identification all the way through to launching and improving products.

The evolution shows the underlying methodology is sound. By adapting to new contexts and combining complementary frameworks, design thinking remains highly relevant.

When leveraged effectively, design thinking paired with agile development can drive real transformational change rather than just incremental improvements. Product teams should view it as an ever-evolving and customizable toolkit.

Product Discovery Frameworks: Conclusion

In summary, design thinking has evolved substantially from its origins while retaining the same human-centric core. Product teams should feel empowered to shape it to their unique needs and combine it with lean and agile approaches.

Done right, design thinking unlocks creativity, innovation and growth. But it takes practice and sustained commitment. Evolving models provide more comprehensive guidance across the product lifecycle.

The future of design thinking is bright. As long as we keep the customer at the center, adapt frameworks as needed, and focus on real outcomes, design thinking will continue enabling teams to deliver products customers love.