Design thinking is a method for solving business problems that starts not with a ready-made solution, but with a deep understanding of real user needs. Instead of designing a product “from the desk”, the team tests assumptions with fast prototypes and adjusts direction based on how people actually respond, before investing in a full rollout.
Quick Overview
What you’ll learn from this article:
- How design thinking differs from a classic product design process
- The five-stage process: empathise, define, ideate, prototype, test
- How to run a one-day design thinking workshop for a team
- Mistakes to avoid so the method doesn’t end at brainstorming without follow-through
Who this article is for: product team leads, process managers looking for a method to tackle difficult, ill-defined business problems, and facilitators of internal workshops.
Reading time: 6 minutes
Design thinking: a workshop for solving business problems
Stanford d.school describes design thinking as an iterative process in which a team works to understand the user, questions its assumptions, and reframes the problem to uncover solutions that aren’t visible on the first pass. The key difference from a classic design process: design thinking deliberately delays choosing the “right” solution until the team has tested a few competing ideas with real users. This works especially well where the problem itself is poorly defined — the team knows “something isn’t working” but doesn’t yet know exactly what, or why.
The five stages of the design thinking process
| Stage | Goal | Typical tool |
|---|---|---|
| Empathise | Understand real user needs and frustrations | In-depth interviews, on-site observation |
| Define | Frame a specific, narrow problem to solve | Point-of-view statement, problem map |
| Ideate | Generate a wide range of possible solutions | Brainstorming, “How Might We” technique |
| Prototype | Build a fast, cheap model of a solution | Paper mock-up, clickable prototype |
| Test | Check how real users respond to the prototype | Usability tests, post-test interviews |
The stages aren’t strictly linear — the team regularly returns to earlier steps when testing a prototype reveals the problem was framed incorrectly. That iterative loop is the core of the method, not a deviation from it.
How to run a design thinking workshop step by step
- Bring together a cross-functional team — people from different functions (product, sales, customer support, engineering) each bring a different view of the same problem, reducing the blind spots any single discipline has.
- Start from real user data, not the team’s own assumptions — even three or four short interviews conducted a week before the workshop dramatically improve the quality of the discussion.
- Set aside dedicated time just for defining the problem — teams that jump to ideation too quickly usually end up solving the wrong problem very efficiently.
- Prototype cheaper and faster than instinct suggests — a paper mock-up ready in 20 minutes yields more useful feedback than a week spent polishing a prototype nobody has seen yet.
- Schedule a test with real users before the workshop ends, even if it’s just three conversations — skip this step and the workshop ends at the idea stage rather than an evidence-based decision.
The most common mistake in a first implementation is treating design thinking as a one-off creative session that nobody revisits afterwards. A workshop with no process owner and no planned next step (who tests the prototype, with whom, by when) ends up with a list of interesting ideas that never reach implementation — exactly what design thinking was meant to prevent.
A second common mistake is inviting only decision-makers to the workshop, without the teams that work closest to the problem day to day — customer support, technical support, front-line sales. They usually have the most precise picture of where user frustration actually shows up, and leaving them out of the empathise stage tends to produce a solution to the problem leadership assumes exists, rather than the one that actually does. It’s also worth remembering that design thinking doesn’t replace quantitative data analysis — it complements it. Interviews and observation add depth and context that metrics alone don’t show, but the decision on how far to scale a rollout should still rest on hard data collected once the first prototype tests are done.
Read Also
Develop Your Skills
Want to deepen your skills in process optimisation and business problem-solving methods? Check out our training led by experienced EITT instructors.
➡️ APQP/PPAP: Product and Process Quality Planning — EITT training ➡️ Digitalization in Project and Process Management: Optimization Using Lean and Six Sigma — EITT training
Frequently Asked Questions (FAQ)
How does design thinking differ from a regular brainstorm?
A brainstorm is a single ideation technique, usually without an earlier user-research stage and without testing solutions afterwards. Design thinking is a full process — it starts with empathy and studying real needs, and ends with testing a prototype on real users, so the chosen solution rests on evidence rather than the team’s creativity alone.
How long does a typical design thinking workshop take?
The format can range from a one-day workshop focused on a single, narrowly defined problem to a multi-week process with several rounds of prototype testing. For a first encounter with the method, a one-day session covering all five stages in a condensed form, ending with a real test, works well.
Does design thinking only work for digital product design?
No — the method originated in product design, but works just as well for designing internal processes, services, or customer experience in any industry. The key condition is a real user whose needs can be studied, regardless of whether the end result is an app, a procedure, or a service.
How do you avoid a workshop ending as a list of ideas with no follow-through?
Before the workshop starts, assign a person accountable for next steps and schedule a specific date for testing the prototype with real users — before the session even ends. A workshop with no planned follow-up almost always stops at the stage of inspiring ideas that are never verified or implemented.