Markets stopped being about what suppliers have to offer
There is a clear trend across the market for products and services: a focus on the customer’s needs. The customer is now the central character in business, in medicine, in public administration. The rule is set not by supply — what happens to be available — but by demand: what the customer actually wants or needs. That forces organisations to adjust both their offer and their way of working.
Convincing customers that they will gain a real benefit from a product or service has become the vital part. In that environment, organisations need methods that let them look at the world through the customer’s eyes, understand the need, and build something that genuinely satisfies it. Design thinking is one of those methods — and in our view the idea behind it is excellent.
The hard questions come next, and this page is about those. How do you use it effectively? What does it take to get the full value from design thinking inside an organisation? Is every process that involves a moment of attention to the customer a design thinking process? And how do you plan such processes so they actually work?
📌 Quick navigation
What design thinking is not
The quickest way to answer “is every customer-focused process a design thinking process?” is to be precise about what it excludes. Caring about customers is a value. Design thinking is a method, and a method has obligations.
| Often mistaken for it | Why it is not the same thing |
|---|---|
| Collecting customer feedback | Feedback tells you how people reacted to what you already built. Design thinking starts before that, by studying the need rather than the reaction to your answer to it. |
| A creative workshop with sticky notes | The artefacts are not the method. Without research evidence going in and prototype testing coming out, a workshop produces confident opinions faster, not better decisions. |
| Asking customers what they want | People describe solutions they can already imagine. The method observes what they do and infers the need behind it, which is usually different. |
| User interface design | Design thinking is a way of framing and solving problems. It is used on services, processes and policies as often as on screens. |
Four conditions that make it work
A real problem, not a chosen solution
If the outcome is decided before the work starts, the method becomes theatre. The most valuable thing design thinking produces is a changed understanding of the problem — and that requires being allowed to change it.
Direct contact with users
Second-hand descriptions of users, filtered through a department, lose exactly the detail the method depends on. Someone on the team has to have watched a real person struggle.
Permission to be wrong cheaply
Prototyping only works where a failed prototype counts as progress. In organisations where being wrong is expensive, teams stop testing and start defending.
A decision-maker in the room
Design thinking generates choices. If nobody present can commit to one, the process ends in a report and the organisation concludes the method does not work.
Where it fits, and where it does not
Design thinking earns its keep when the problem is genuinely unclear, when the people affected are reachable, and when there is room to change the answer. It is the wrong tool when the requirement is fixed by regulation, when the problem is purely technical with a known correct solution, or when the real constraint is capacity rather than understanding.
It also does not replace delivery. Design thinking decides what is worth building and why; agile approaches take it from there. The two are complementary, and organisations that treat them as competing usually end up doing neither properly.
How to start without a transformation programme
The common failure is to start too big: a company-wide initiative, a rebranded innovation department, and no change in how any particular decision gets made. The alternative is narrower and works better — take one real problem that matters, run it properly through the four stages of the Double Diamond, and let the result argue for the method.
What makes that first attempt succeed or fail is usually method rather than enthusiasm: knowing which research technique answers which question, how to write a problem statement that is neither a solution in disguise nor uselessly broad, and how to test a prototype without leading the user. That is the content of the Design Thinking Method Foundation course, and the reason the certification exists.
Frequently asked questions
Is design thinking only for product companies?
No. It is applied to services, internal processes, public administration and healthcare at least as often as to products. What it needs is a user whose need can be studied, not a product to sell.
Does it replace market research?
It changes the question. Market research measures preferences across a population; design thinking studies a smaller number of people in much more depth, to understand the need behind the preference. Most organisations need both.
How long does a design thinking process take?
It scales with the problem, not the method. A focused problem with reachable users can run in weeks; the model itself imposes no duration, only an order.
Who should be in the team?
People with different vantage points on the problem, and at least one person who can decide. Homogeneous teams diverge narrowly, which defeats the first half of the method.
Is there a certification?
Yes. Design Thinking Method Foundation covers the vocabulary, the model and the methods behind each stage, and the simulators let you check your readiness before booking.
Where should I read next?
The Double Diamond process page is the natural next step — it is where the method stops being a philosophy and becomes four stages with outputs.
Thinking about a first design thinking project? Tell us the problem and who it affects, and we will tell you honestly whether the method fits — and what it would take to run it properly. Get in touch.
