What is design thinking in UX?

The five stages most people use

The version taught most widely, including at Stanford's d.school, has five stages: empathize, define, ideate, prototype and test. You will see other versions with different names or a different number of steps, and that is fine. The shape is what matters.

• Empathize: learn about the people involved through interviews, observation and immersion.
• Define: boil what you learned down to a clear problem statement.
• Ideate: generate many possible solutions without judging them yet.
• Prototype: build quick, rough versions of the most promising ideas.
• Test: put them in front of real users and see what happens.

The stages are not a straight line. Testing often sends you back to defining or ideating, and that loop is the point.

Why it appeals to teams

It gives a mixed group of designers, engineers, marketers and managers a shared way to talk. Everyone knows which phase you are in, so "let's stop critiquing and generate more ideas" has a legitimate place in the meeting.

It also pushes against a very common failure: building the thing someone in the room imagined, rather than the thing a user needs. By forcing early contact with real people, it reduces expensive surprises later.

And it treats ideas as cheap, which makes it easier to throw away the ones that do not work. A paper prototype takes an afternoon. Nobody gets attached to it.

Design thinking is not the same as UX design

This confusion is common. Design thinking is a general approach to problem solving that people use for services, policies, workshops and business models as well as screens. UX design is a discipline with its own methods and craft, such as interaction design, research and interface design.

UX designers often use design thinking as a framework, but doing a workshop with sticky notes does not make a product usable. The detail work after the workshop is where good UX gets built.

Where it gets criticized, fairly

Honest practitioners admit the criticism has some truth. Done as a one-day workshop with no follow-up, design thinking can become theater: lots of colorful notes, no change in the product.

The tidy five-step diagram can also make real work look neater than it is. Projects rarely move cleanly from one box to the next, and research with real people takes longer than a workshop slot allows.

Another complaint is that it can be used as a label to sell consulting. The antidote is to judge it by what it produces: did you learn something true about users, and did it change a decision?

When to use it and when not to

It shines when the problem is fuzzy, such as "why do new customers drop off?" or "what should our service look like?". It is less useful for well-defined tasks, like fixing a known bug or tweaking a form, where you already know what the answer needs to do.