Design thinking for teams: a practical guide

Design thinking is one of those terms that sounds like a methodology but often ends up being a mood board session. Here's how to make it actually useful.

What design thinking is (and isn't)

Design thinking is a structured approach to problem-solving that starts with the user, generates many possible solutions, and tests them quickly before committing to one. It is not brainstorming. It's not a creative exercise. It's a repeatable process with distinct phases, each with specific tools and outputs.

The five phases

• Empathise: Start with the person you're solving for. Interview real users. Observe actual behaviour. Resist jumping to solutions before you understand the problem.
• Define: Synthesise what you learned into a clear problem statement: 'How might we help [person] do [thing] so that [outcome]?'
• Ideate: Generate as many ideas as possible before evaluating any of them. Quantity first, quality second.
• Prototype: Build the simplest possible version of your best ideas. The goal is to make the idea testable — not impressive.
• Test: Put the prototype in front of real people. Don't explain it. Don't defend it. Watch where they get confused.

How to run this in a day

A one-day design thinking workshop can take a team through all five phases. The key is preparation: the empathy phase should be done before the day, not during it.

When it works and when it doesn't

Design thinking works well for problems that involve real users, ambiguous solutions, or entrenched thinking. It works less well for operational problems with clear constraints and a right answer.