Design Thinking

Origin

The term was popularised by Tim Brown, long-time CEO of the design agency IDEO (Design Thinking, Harvard Business Review, June 2008), who described the working method of designers as a general innovation approach. It was institutionalised at Stanford University’s d.school and, in Europe, at the HPI School of Design Thinking at the Hasso Plattner Institute in Potsdam — both owed to the commitment of Hasso Plattner. The roots reach further back: to the design methodology of the 1960s and Herbert Simon’s understanding of design as a science.

Typical use

Design Thinking suits ill-defined problems in early phases: when it is unclear what the actual customer problem is, when existing offerings lose acceptance, or when a team needs to escape the inside view of its own product. The observation phase yields material similar to a Jobs to be Done analysis, only broader and less bound to theory. For the incremental optimisation of known products, by contrast, the effort is rarely justified.

Procedure

1. Build empathy

   The team observes and interviews users in their context — not in the focus group, but at the site of the problem. The search is for workarounds, frustrations and unspoken needs that would never surface in a survey.

2. Define the problem

   The observations are condensed into a point of view: which user needs what, and why? A good problem definition is narrow enough to focus ideas and open enough not to pre-empt solution paths.

3. Generate ideas

   Ideation first produces breadth — quantity before quality, judgement deferred — then selects against the problem definition. Interdisciplinary teams are not an accessory here but a precondition: the method lives on colliding perspectives.

4. Build prototypes

   Selected ideas are made tangible quickly and cheaply — a paper model, a click dummy, a role play. The prototype is a thinking tool, not a pre-product: it should answer a question, not impress.

5. Test and iterate

   Prototypes are put in front of real users; the feedback revises ideas and often the problem definition itself. The loop does not end with the workshop but with a robust solution — or with the well-founded decision to pose the problem differently.

Limits and typical mistakes

The greatest danger of Design Thinking is its popularity: as “innovation theatre” it becomes a stage set — a two-day workshop, colourful walls, a photo for the intranet, after which everyone returns to the line organisation. The method itself does not force implementation; without budget, mandate and a path from prototype to product, the results remain inconsequential. Second, the process diagram invites a mechanical ticking-off of phases, while the actual achievement — the quality of observation and problem definition — demands experience. Third, Design Thinking replaces neither strategy nor business model work: whether a user-centred solution is economically viable is only settled by validation, for instance with Lean Startup experiments.

Relation to the Innovator’s Dilemma