What is design thinking, really?

This is Part 2 of Design Matters, a series about what design actually is, why it belongs at the centre of strategic decisions, and what changes for organizations when it gets there.

If you've spent any time in business circles over the last decade, you've heard the term. Design thinking. It appears in strategic plans, workshop agendas, and innovation frameworks. It gets taught in MBA programs and referenced in boardroom presentations. It has, in short, become one of those phrases that means so many things it risks meaning nothing at all.

Which is a shame. Because underneath the jargon, design thinking describes something genuinely useful: a way of approaching problems that most organizations could benefit from, and that most designers practice intuitively without necessarily calling it anything.

So let's strip it back.

It starts with the wrong question

Most problem-solving starts with a solution. Someone identifies a pain point, proposes a fix, and the organization mobilizes to execute it. This is efficient. It is also, frequently, how organizations end up solving the wrong problem beautifully.

Design thinking starts differently. It starts by questioning whether the problem as stated is actually the problem worth solving. Before a single solution is proposed, design thinking asks: what is actually happening here? Who is experiencing it? What do they need, not what do they say they need, but what does their behaviour, their frustration, their work-around tell us about what they actually need?

This is the empathy phase, and it's more rigorous than it sounds. It's not about being nice or human-centred in a vague, feel-good way. It's about gathering real signal before committing resources to a direction. It's about resisting the gravitational pull of the obvious solution long enough to make sure it's the right one.

The discipline of not knowing

One of the hardest things design thinking asks of experienced professionals is to sit with uncertainty. To hold a problem open a little longer than is comfortable. To resist the instinct and the organizational pressure to move to answers before the question is fully understood.

This runs counter to how most workplaces reward people. Decisiveness is valued. Speed is valued. Coming to a meeting with a proposal is valued. Coming to a meeting with better questions is often misread as unpreparedness.

But the questions are the work. A designer who asks "who is this actually for?" before opening a single piece of software is doing something more valuable than one who produces fifty concepts without ever interrogating the brief. The thinking that happens before the making shapes everything that follows.

Making ideas visible

Once the problem is better understood, design thinking moves into iteration; this is where the process looks most different from conventional strategic planning. Rather than developing a complete, polished solution and presenting it for approval, design thinking works in rough drafts. Sketches. Prototypes. Minimum viable versions of an idea that can be put in front of real people before significant resources are committed.

This is not about cutting corners. It's about learning faster. A rough prototype that fails in week two costs a fraction of a refined solution that fails at launch. The goal is to make the idea visible and testable as quickly as possible and to move from abstract to concrete, where real feedback becomes possible.

For communications and design work, this looks like presenting rough layout directions before finalising anything. Testing a message with a small audience before committing to a campaign. Asking clients to react to something imperfect rather than waiting to reveal something finished. The conversation that happens around an imperfect draft is almost always more useful than the one that happens around a polished final.

Why this matters for organizations that aren't design firms

Design thinking isn't a proprietary method. It's a set of habits like inquiry before assumption, iteration before commitment, and audience before self that improve decision-making in any discipline.

The organizations I've seen communicate most effectively aren't necessarily the ones with the biggest budgets or the most sophisticated tools. They're the ones that ask good questions early, stay close to the people they're trying to reach, and treat communications as a thinking process rather than a production process.

The shift from production to thinking is what design thinking actually means in practice. Not post-it notes on a whiteboard. Not a two-day workshop. A fundamental reorientation toward the problem before the solution.

It sounds simple. Most powerful things do.

Design Matters continues with Part 3: How Design Earns a Seat at the Strategy Table.