What in B2C is a ritual of sticky notes is, in industry, the fastest method for getting actionable qualitative insight. Analytics tells you what is happening. The customer journey map tells you why. And it says so in a week, not in six months.
Design Thinking is a way of thinking applied to product development. It is not a step-by-step methodology or a toolkit: it is a change of question. Instead of starting from “what technical solution do I build?”, it starts from “what real problem am I solving, and for whom?”.
The approach was formalised in universities and innovation consultancies in the early 2000s, but the principles are older: ethnographic research, rapid prototyping, iteration with the user at the centre. What the formalisation contributed was ordering those principles into a repeatable process.
The usual misunderstanding is reducing Design Thinking to its visible rituals: sticky notes on the wall, colourful maps, workshops with biscuits. That is the shell. What changes the outcome is the mental frame: not assuming you already understand the user, not settling for the first solution, not confusing having an idea with understanding a problem.
In industrial products, where cycles are long and investments large, starting from a misunderstood problem is the most expensive error in the whole chain. Industrialisation already eats time and money, as we saw in the TRL INNsight. Multiplying that cost by building the wrong product is the worst possible combination.
Quantitative analytics is necessary but not sufficient. Data tells you what qué is happening: conversion rates, units sold, churn. It rarely tells you why. And it almost never tells you what would have happened if you had built something different.
Design thinking does not reject data: it complements it with three dimensions analytics alone does not capture. Context: what real situation the user is in. Friction: where they stumble, what frustrates them. Motivation: what they are trying to achieve, not what they say they want. Without those three dimensions, data produces decisions that are technically correct and commercially irrelevant.
For an industrial team used to OEE, quality ratios and cost analysis — all quantitative and measurable — bringing in the qualitative is not giving up rigour. It is adding a different kind of rigour: understanding the user in their context. Both are necessary.
There is an expensive myth: that qualitative insight requires months of ethnographic research before you can decide. It is exactly the other way round. Applied properly, Design Thinking in industrial products is the fastest method for getting actionable signals. One day’s session with the team and three calls to existing customers gives more judgement than a quarter of internal committees arguing about what the customer “probably” wants.
The method: decide with the information available, act at small scale, validate with a real customer, pivot if it does not work. This is not lean startup. It is industrial discipline applied to product development. Depth and rigour come afterwards, on top of what has already been validated. Speed is what separates teams that reach the market on time from teams that arrive two years late.
The Design Thinking field has produced dozens of formalised tools over the last two decades. There is first-rate literature and well-established open catalogues. Far from being a chaotic list, each tool answers a specific question.
One tool you were probably expecting is missing: the Business Model Canvas. I have left it out deliberately. The Business Model Canvas is the most used canvas in innovation and also the most misread: everybody has filled one in during a two-hour session, almost nobody has worked one with real data until it tells a coherent story. It deserves its own dedicated piece, not a passing paragraph.
From this ecosystem we go deep on one: the customer journey map. For three reasons: it forces you to understand the user in their real temporal context, it applies directly to industrial B2B, and it produces a deliverable a management committee understands with no prior training.
If the underlying thesis is speed, it has to land somewhere. These three formats are designed for teams that do not have three months of prior research. Each produces an actionable deliverable within days. They are the starting point; depth comes afterwards, on top of what has been validated.
A 4-6 hour session with product, sales, support and engineering. In parallel, three calls to existing customers with five pre-agreed questions. By the end of the day you have a first map with the critical points identified.
Five conversations of 30-45 minutes with real users — users, not buyers. Open questions about context and friction, not about your product. Five well-run interviews surface patterns no spreadsheet detects. Two hours of synthesis on Friday.
A two-hour meeting with the team. Materials: support tickets from the last 90 days, sales conversations, NPS if you have it. Fill in the empathy map with real quotes, not assumptions. Identify the three information gaps you are missing in order to decide.
Three formats, three timescales, one principle: speed of learning over initial completeness. The team that decides on Friday with an imperfect CJM and pivots on Tuesday reaches the market before the team that spends three months designing the perfect research. Both get it wrong: the difference is that one finds out three months earlier.
We are not going to tell you to wait three months for perfect research. We are going to tell you what you can run this week — the format, the team, the timing. Depth comes afterwards, on top of what has already been validated.
This tool gives you a steer. One well-prepared CJM session is worth more than three badly prepared ones.