What is design thinking?
Design thinking is the way designers solve problems, written down so that everyone else can use it. The method usually runs in five stages: empathize with the people affected, define the problem precisely, ideate widely, prototype the most promising ideas cheaply, and test them with real people. Then it loops. The stages came out of Stanford's d.school and the consultancy IDEO in the 1990s and 2000s, and the approach has since been applied to products, services, organizations and campaigns, anywhere a team has a hard problem and a temptation to jump straight to the answer.
The core move is to delay the solution. Most teams start with a solution and look for evidence; design thinking starts with the person and lets the solution emerge from what they actually need. It treats ideas as cheap and prototypes as the real unit of progress, because a rough version in someone's hands teaches more than a polished one in a deck.
Why it matters
Why design thinking matters
Most expensive failures are solutions to the wrong problem. A brand builds the app nobody asked for, launches the campaign that answers a question nobody had, or redesigns the store around what the executive team likes rather than what the customer does. Design thinking is a defense against that. By putting observation before invention, it tends to surface the real problem, which is often smaller and stranger than the one in the brief.
It also changes the cost of being wrong. A team that prototypes and tests in a week finds out what fails for the price of a week; a team that plans and builds for a year finds out for the price of a year. For creative work, that discipline is what separates ideas that are interesting from ideas that work, and it is why the method has spread from product design into advertising, service design and strategy.
In practice
How design thinking works in practice
- 01
It begins with research that is closer to observation than to surveys: watching people use the product, talking to them in their own setting, listening for what they do rather than what they say. The team writes down what it learned and frames the problem as a question worth answering, usually in the form of "how might we". Then there is a deliberately wide generation of ideas, with judgment suspended, followed by a quick selection of the few worth building.
- 02
Prototyping is where the method earns its reputation. A paper sketch, a clickable mockup, a rough cut, a cardboard store, a script read aloud: whatever is fastest to make and realistic enough to react to. Those prototypes go in front of real people, the team watches what happens, and the next version is built from what broke. The whole loop can run in days when it is compressed into a design sprint, or over months for a product. The output is not a report; it is a tested thing and the confidence to build it properly.
At RIOT
Design thinking at RIOT
Krova, our production software, is the clearest case of the method in our own work: production software made by a production studio, which means the people with the problem and the people building the answer were the same people, and the tool was shaped in use rather than from a specification. AltSounds, our music video channel, and Muvvoo, our music video database, grew the same way, as products we wanted to exist, made and tested in use. Each one is a prototype that kept earning the next version.
Watch out
What people get wrong about design thinking
Treating it as a workshop. A day of sticky notes with no research before and no prototype after is design theater, and it has given the method a bad name in companies that tried it once. The value is in the loop, not the exercise.
The other mistake is assuming it replaces taste. Design thinking tells you what people need; it does not tell you what the answer should look like. The method produces a well-defined problem and a tested direction, and then someone with craft still has to make the thing good.
