Design thinking

What it means

Design thinking is an approach to problem solving that starts with the person the problem is being solved for, not with technology or the company’s internal view. It moves in steps: understand the user, define the problem, come up with several solutions, build a simple prototype and test it with real people.

The steps repeat in cycles rather than in a straight line. If a test shows that a solution does not work, the team goes back to understanding the problem. The aim is to find out quickly and cheaply what fails before investing in developing the whole product.

The approach is close to the MVP and agile management: it also relies on short iterations and feedback. Design thinking focuses more on the stage before development, on finding the right problem and value proposition.

How it works in practice

It is not used only for products. It works just as well for improving internal processes: for example, when looking into why clients send documents late, talking to them often reveals that the problem is not laziness but an impractical way of handing them over.

Useful tools include a customer journey map, user interviews and simple paper or clickable prototypes. The outcome is not a long report but tested findings on what people need and what gets in their way.

When introducing a new system, such as a portal for submitting documents, design thinking helps avoid expensive software nobody uses. A few interviews and a prototype tested on five clients cost a fraction of a failed project.

What to watch out for

A common mistake is running design thinking as a sticky-note workshop without real users. If the team replaces “empathy” with its own assumptions about customers, the result is the same mistakes, only better documented.

The second risk is getting stuck in endless research. The approach should lead to decisions and testing, not another round of workshops. A clear deadline and budget for each iteration keep the project grounded.