# Design Thinking Process

> A way to solve problems that starts with people. The five modes of design thinking, quick sketches, and why good design comes in rounds.

**Course:** [Design Principles](https://learn.benibix.com/learn/design-foundations)  
**Time:** 11 min

**After this lesson you can:**

- Name the five modes of design thinking
- Sketch many ideas before picking one
- Plan a design in rounds

## What design thinking is, and its five modes

Design thinking is a way to solve problems that starts with people, not with the answer. A well known version from a US university has five modes: empathize, define, ideate, prototype and test. Teams loop through them more than once. Each loop teaches them something the last one missed.

Empathize means learning about the people you design for. You watch them, talk to them and try their task yourself. Define means writing down the real problem in one sentence. Ideate means coming up with many ideas, good and bad, before judging any.

Prototype means making a cheap, rough version of an idea. Test means putting it in front of real people and watching what happens. What you learn sends you back to an earlier mode. That loop is the whole point, and it is called design iteration.

Human-centered design is the wider idea behind all this. It says: build for what real people need, and check with them at every step. It sounds obvious. Yet many products are built from what the team guessed, and tested only after they ship.

A thumbnail sketch is the fastest tool in the kit. It is a tiny, rough drawing of a layout, often no bigger than a stamp. Because each one takes a minute, you can try 20 before lunch. The first idea is rarely the best one, and thumbnails make the second cheap.

Rounds matter because nobody gets it right the first time. A design that goes through three rounds of make, test and change is almost always better than one polished once. Each round should be small, so a mistake costs a day, not a month.

People often treat the five modes as a straight line, done once in order. That misses the point. Testing a prototype on Friday may show the problem was defined wrong on Monday. Going back is not failure. It is the process working.

![Five boxes in a row, empathize, define, ideate, prototype and test, joined by arrows, with a curved arrow running from test back to empathize and define.](https://learn.benibix.com/diagrams/design-thinking.svg)

### Example: A library redesigns its book drop

A library's book drop kept jamming. The team watched 30 people return books and saw most push big books in sideways.

They drew 15 thumbnails, built 2 cardboard versions, and tested each for a week. The second, with a wider slot and a picture of a book, cut jams by more than half.

**Words in this lesson:** [Design Thinking](https://learn.benibix.com/term/design/design-thinking), [Human-Centered Design](https://learn.benibix.com/term/design/human-centered-design), [Thumbnail Sketch](https://learn.benibix.com/term/design/thumbnail-sketch), [Design Iteration](https://learn.benibix.com/term/design/design-iteration)

**Question:** What should happen when a test shows the problem was defined wrong?

**Answer:** Go back and define the problem again. Design thinking is a loop, not a line. Going back to an earlier mode is the process doing its job, and it is cheaper than shipping the wrong thing.

---

Source: https://learn.benibix.com/learn/design-foundations/design-thinking-process
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
