Design thinking is a way of making sure you build the right thing before you pay to build it. It gets talked about as a philosophy, but it’s more useful to treat it as a money-saving discipline.
Most products don’t fail because they were built badly. They fail because they were the wrong thing to build, and nobody found out until the budget was gone. Design thinking catches that early: you find out what people actually need, test it cheaply, and only then commit to development.
In practice, that means working through five steps. Each one ends with something you can show, and each one is a chance to stop before an expensive mistake gets built.
The five steps
- Empathize. Understand the people who will use the product, through interviews, observation and data rather than assumptions.
- Define. State the real problem in one sentence. Most failed products solve a problem nobody had.
- Ideate. Generate several ways to solve it, instead of committing to the first idea in the room.
- Prototype. Build the cheapest possible version that can be tested: sketches, wireframes or a clickable mockup.
- Test. Put it in front of real users, watch where they struggle, and go back a step or two.
It isn’t a straight line. Testing sends you back to define or ideate, and that loop is the point: each cycle is cheap, and each one removes a costly mistake.
What each step produces
| Step | You end up with |
|---|---|
| Empathize | Interview notes, observed behaviour, real quotes from users |
| Define | A written problem statement, personas, a user journey |
| Ideate | Several possible solutions, and a reason for choosing one |
| Prototype | Wireframes or a clickable prototype |
| Test | A list of what confused people, and the fixes |
Where the money is saved
Changing a prototype takes hours. Changing a built feature takes developer weeks, plus testing, plus the cost of everything else that didn’t get built meanwhile. Design thinking front-loads the cheap changes so the expensive ones never happen.
The second saving is focus. A defined problem kills the endless feature debates that stall teams, because there is a written standard to judge ideas against.
Design thinking and the Double Diamond
You’ll also hear about the Double Diamond: discover, define, develop, deliver. It’s the same idea framed differently, alternating between opening up (exploring broadly) and narrowing down (committing to one direction). I use both: design thinking for the steps, the Double Diamond to keep research and design from being rushed.
What it looks like on a real project
- Week 1: interviews with 5–8 users, plus a review of how the current product is used.
- Week 2: the problem written down, agreed with you, and mapped as a user journey.
- Week 3: a few directions explored, one chosen, wireframes made.
- Week 4: a clickable prototype tested with real users, and a revised design ready to build.
Four weeks before development starts sounds slow until you compare it with four months of building the wrong thing.
Common objections
- “We already know what our users want.” Sometimes true. Testing with five people is cheap enough to confirm it, and uncomfortable enough to be worth doing.
- “We don’t have time.” The time gets spent either way: before building, or afterwards in rework.
- “It’s just for big companies.” The opposite. Small teams have less margin for building the wrong thing.
Frequently asked questions
What is design thinking in simple terms?
A five-step way of solving problems: understand the people involved, define the real problem, come up with several solutions, build a cheap version, and test it with real users.
What are the five stages of design thinking?
Empathize, define, ideate, prototype and test. In practice you loop between them rather than going through them once.
Is design thinking only for designers?
No. It’s used for products, services and business processes. Designers use it most, but the method belongs to anyone solving a problem for other people.
How is design thinking different from the Double Diamond?
They describe the same approach at different levels. Design thinking names five steps; the Double Diamond shows the rhythm of exploring broadly, then narrowing down, twice.
Want this process applied to your product?
I use design thinking on every project, from research to developer handoff. See UI/UX design in Lebanon or in Dubai.
Email: [email protected]
Note: Sign up to my mailing list to receive useful articles like this one every once in a while.
