Design
Thinking
Fundamentals

A human-centred approach to complex problems

Design Thinking is a problem-solving methodology that prioritises understanding the people who experience a problem before attempting to solve it. It is human-centred (solutions are designed for real people in real contexts), collaborative (diverse perspectives are used intentionally), and experimental (ideas are tested quickly with real users, not debated in meeting rooms).

The critical shift is sequencing. Design Thinking delays solution generation until the problem is deeply understood, because the most elegant solution to the wrong problem is still the wrong solution.

The five stages of Design Thinking

Design Thinking is typically taught as five stages. These are not strictly sequential; real practice involves constant iteration, moving back and forth as new information emerges. But they provide a clear map of the process.

Empathise: seeing the world through someone else's eyes

Empathy in Design Thinking isn't sympathy. It's a rigorous effort to understand how someone else experiences their world. It requires setting aside your own assumptions and genuinely entering the user's context. Three methods drive most empathy work.

Define: the problem statement as a design brief

The Define stage transforms empathy research into a clear, actionable problem statement. This is harder than it sounds: raw research is messy, and finding the real problem beneath the stated one requires synthesis and judgment.

The most common format is the "How Might We" (HMW) question, a frame that's specific enough to give direction, open enough to allow creative solutions:

A good problem statement keeps the team anchored throughout ideation and prototyping. When a proposed solution doesn't address it, you have a principled reason to redirect, not just an opinion.

Ideate: quantity first, quality later

Ideation is the divergent phase: the goal is to generate as many possible solutions as possible before evaluating any of them. The common mistake is to evaluate ideas as they emerge, which kills creative risk-taking before it starts.

Two principles govern good ideation sessions:

After generating ideas, the team converges: dot voting, impact/effort matrices, and explicit criteria aligned with the problem statement are used to select which ideas are worth prototyping. Two or three ideas typically move forward.

Prototype and test: make it real, learn fast

Prototyping is the act of making an idea tangible enough to test. The key principle: build to think, not to present. A prototype is a learning tool, not a deliverable. The cheaper and faster it is to build, the more failures you can afford, and failures in prototyping are wins, because they're cheap.

Testing is observation, not validation. You're not presenting your idea hoping for approval. You're watching what users do with it and asking neutral questions. "What were you expecting to happen?" and "What would you do next?" reveal more than "Did you like it?"

Design Thinking, Agile, and Lean: how they fit together

These three methodologies are often mentioned in the same breath and sometimes confused. They're complementary, not competing:

In practice, strong product teams use all three: Design Thinking to discover and define, Agile to build and iterate, and Lean thinking to test whether the whole thing makes business sense. The boundaries are blurry by design.

The discipline of staying curious longer

Design Thinking's most important contribution isn't a framework or a set of tools. It's a discipline of staying in the problem space longer than feels comfortable. The natural instinct is to move quickly to solutions. Design Thinking trains teams to resist that instinct until the problem is truly understood.

This pays off compoundingly. Teams that invest in the Empathise and Define stages fail less often in prototyping. Teams that invest in prototyping fail less often in development. Development failures are exponentially more expensive than prototype failures. Every hour in a user interview is worth ten hours of avoided rework.