agile3
Product Management

Design Thinking

A human-centred approach to solving problems: understand people deeply, then prototype and test ideas fast.

2 min read · Practitioner

In 30 seconds

  • Start from people's needs, not from a solution.
  • Five stages: empathize, define, ideate, prototype, test.
  • Pairs naturally with agile delivery.

The five stages

  1. Empathize: observe and interview real users
  2. Define: frame the core problem clearly
  3. Ideate: generate many possible solutions
  4. Prototype: build quick, cheap versions
  5. Test: learn from users and loop back

This five-stage model is associated with Stanford's d.school and the design firm IDEO.

Fitting with agile

Design thinking helps decide what to build; agile helps build it well and adapt. Many teams run design thinking in product discovery alongside delivery sprints.

Tips for starting

  • Talk to at least five real users before defining the problem
  • Prototype in hours, not weeks: paper and clickable mockups count
  • Bring developers into research, not just designers

Myth vs reality

Myth · Design thinking is only for designers.
Reality · It works best with mixed teams.
Myth · The stages run once, in order.
Reality · Teams loop back often as they learn.
Myth · It's just brainstorming.
Reality · Research and testing are the core; ideation is one step.

FAQ

How long does a design thinking cycle take?

From a few days in a design sprint to several weeks.

What's a design sprint?

A five-day, structured version popularized by Google Ventures.

Does it replace user stories?

No; insights feed stories in the backlog.