The relationship between Design Thinking and Agile

When organizations first explore Design Thinking and Agile, there is often early confusion about how the two relate. Both look at customer problems through a customer lens, so it is natural to wonder whether they are simply two versions of the same thing.

They are not. One is concerned with defining the problem and the solution. The other is concerned with optimizing the value of that solution once it exists. Design Thinking is a powerful tool for discovering what constitutes value to a particular customer or segment, while Agile is a framework for delivering that value in a constantly iterative, and therefore more responsive, way.

Design Thinking

At its core, Design Thinking focuses on humans first. It is a solution-based methodology that begins by understanding human need, built on a foundation of curiosity rather than assumption. Design Thinking is not a linear process. It is flexible and fluid by nature, though most organizations adopt a structured, phased approach to help guide implementation:

1. Empathize
2. Define
3. Ideate
4. Prototype
5. Test

In practice, these phases overlap and repeat continuously, with forward momentum on problem-solving always in play. Design Thinking is particularly well suited to what are known as "wicked problems."

Wicked problems

In 1973, Horst Rittel and Melvin Webber, professors of design and urban planning at the University of California, Berkeley, coined the term "wicked problem" to describe issues that are abstract, difficult to define, and made up of multiple interconnected layers. Poverty, climate change, and terrorism are classic examples. Design Thinking is useful precisely because these problems have no fixed endpoint or single correct solution. It is a tool for continual problem-solving rather than one-off resolution.

Design Thinking in the workplace

In a workplace setting, Design Thinking applies its creative, solution-oriented approach to exploring and resolving organizational challenges. When paired with Agile, it allows for adaptability to change and for products and services that develop iteratively. Design Thinking puts people at the heart of what an organization is trying to create or solve for, while Agile brings a customer-value lens that keeps delivery grounded in what matters most. Together, they deliver both the right solution and the return on investment organizations are seeking.

Empathy as the foundation

One of the most important elements of Design Thinking is empathy. In a human-centered design process, empathy asks designers to set aside assumptions. It draws on ethnographic research to surface hidden needs that traditional focus-group research often misses.

Empathy is built by understanding customer needs through immersive, exploratory work; not simply observing from a distance, but engaging directly with the people experiencing the problem. This distinction between "designing for" and "designing with" matters. Some organizations lose sight of the value of research and inquiry during the immersive, exploratory phase, where the real work involves going out to speak with, spend time with, and observe people directly. It is easy to circumvent this step by assuming the answers are already known, but that mindset undermines the true value of a human-centered approach.

What to consider before you start

Design Thinking depends on an organizational culture that is open, trusting, and encouraging. Without that foundation, the methodology struggles to take root.

A seven-year study of fifty projects by Jeanne Liedtka, professor of business administration at the University of Virginia's Darden School of Business, found that <cite index="1-1">immersion in user experiences provides raw material for deeper insights, though finding patterns and making sense of the resulting mass of qualitative data is a significant challenge</cite>. This is precisely where Design Thinking earns its keep, and why experienced designers are essential to the process. Teaching Design Thinking broadly across an organization builds valuable awareness, but it does not replace the need for designers with deep expertise and experience. Ideally, designers should have a seat at the table from the outset.

The relationship between Design Thinking and Agile

Design Thinking and Agile are each part methodology, part philosophy, and both are underpinned by human-centered design. Yet they remain distinct in how they drive customer value. Design Thinking is powered by the ability to collaborate, draw in diverse perspectives, connect the "why" to the "what," and bring clarity to solving the right problems. Agile mindsets and principles pursue that same clarity and collaboration, but apply it to iterating toward the highest-value solutions once the problem is understood.

Treating Design Thinking and Agile as simply two complementary methodologies risks missing the deeper synergy between them. Each brings its strengths to different stages of the value creation process, and together they form a far stronger approach than either delivers alone.

Design Thinking excels at exploring opportunities and problems through divergent thinking and a genuine focus on empathizing with the human user. Agile complements this by providing a mindset and framework for building the right things through iterative action. Used together, they eliminate unnecessary process, inspire creativity, and strip out assumption and bias. Design Thinking identifies the problem and possible solutions, including ones the customer may not have articulated. Agile becomes the engine that delivers the solution, allowing teams to test and learn at pace in a collaborative, cross-functional way.

In short: use Agile to incrementally build the solution that Design Thinking has identified.

Where AI fits in

As organizations mature their use of Design Thinking and Agile, artificial intelligence is becoming a practical addition to both practices, without changing the fundamentals of either. In the empathize and define phases, AI tools can help synthesize large volumes of qualitative research, such as interview transcripts and ethnographic notes, surfacing patterns that would otherwise take a research team considerably longer to identify. This does not replace the immersive, human work of sitting with customers and observing their experience; it simply reduces the friction of making sense of what was learned.

On the Agile side, AI can support faster synthesis of retrospective feedback, assist with backlog grooming by flagging duplicate or related items, and help teams maintain momentum between ceremonies through asynchronous summaries. Used well, AI acts as an amplifier of good Agile and Design Thinking discipline rather than a substitute for it. The quality of outcomes still depends on the rigor of the underlying process and the judgment of the people running it.

Getting the balance right

Knowing which methodology to lean on, and when, can be nuanced. ADAPTOVATE has extensive experience working with complex problems across organizations and designing the right operating model to achieve the outcomes that matter, across sectors including mining, energy, health, financial services, and government. Organizations looking to bring Design Thinking and Agile together, supported by the right AI-enabled tools, are well positioned to unlock the value both approaches offer.