Design Thinking Isn't the Point

Design thinking has been around long enough that the problem isn't awareness.

The problem is misapplication.

Most teams today aren't failing because they don't know the frameworks. They're failing because they're confusing process completion with proposition quality.

This isn't an article about how to "do design thinking properly."

It's about how experienced teams actually design products, services, and brands that survive contact with users, organisations, and markets.

And why most don't.

Reframing the Problem

When teams say they're "doing design thinking," they're usually doing one of three things:

• Running a linear process with high confidence
• Confusing design thinking with visual or brand design
• Performing workshops that feel productive but change very little

None of those are inherently wrong. They're just incomplete.

Design thinking isn't a linear process you pass through once. It's a way of thinking iteratively about problems and solutions together, with testing flowing throughout. Problems inspire solutions. Solutions reshape problems. Some solutions fail while the underlying problem remains very real.

And crucially: design thinking is not visual design.

Visual design is about representation, craft, and communication. Design thinking is a methodology for proposition development, taking end-user problems (consumer, employee, or B2B) and shaping solutions that are desirable, viable, and feasible.

Those three lenses matter. But they don't operate in a vacuum.

Before you even step into the double diamond, there's something most teams ignore.

Before the Double Diamond: Context Matters

The double diamond is the island.

Design thinking happens on the island.

But the island sits in the sea.

Culture, technology adoption, regulation, economics, generational behaviour, timing. These are not steps in a process. They're the environment. You don't "do" them. You read them.

A mental health solution shaped by smartphone usage, work habits, and social norms in Shanghai will look fundamentally different in a low-smartphone market. If you ignore that, you don't just risk solving the wrong problem. You risk solving a problem that doesn't exist here.

Most design thinking theatre happens when teams beautifully map the island while ignoring the weather.

What Design Thinking Actually Unlocks

Design thinking's real value is not hypothesis validation.

That's lean.

Lean helps you test whether something should exist. Design thinking helps you figure out what is worth testing in the first place. Once you move from shaping to scaling, growth becomes a decision system of its own.

Used properly, design thinking helps teams:

• Focus on end users rather than internal narratives
• Frame problems worth solving
• Shape propositions before they harden into bets

It's one methodology among many for creating new products and services. But its specific contribution is a relentless reminder to focus on real human problems or meaningful value, before momentum takes over.

That matters differently by category.

In financial services, problems are often precise and functional. In commoditised FMCG categories, there may be no clear functional problem left to solve. Differentiation shifts to emotional and social value. Treating all categories as if they have the same "problem structure" is a fast way to create nonsense.

Small Decisions, Big Impact

One of the easiest ways to fail is to solve problems you're not meant to solve.

During COVID, some small business owners were so stressed they were drinking less water. That doesn't mean their bank should launch water bottles. The problem may be real, but the right to solve isn't.

Good teams don't fall in love with a problem any more than they fall in love with an idea. They fall in love with finding many problems, then sizing them.

A practical way to do that:

• How painful is it?
• How often does it occur?
• Do we have a right to solve it?

An annual accounting headache may be deeply painful but infrequent. Day-to-day P&L visibility may be less painful but constant. That difference matters.

Another common trap is believing what people say without observing what they do. Latent unmet needs, the ones people don't articulate because they don't know they exist, are almost never discovered in surveys.

If Apple had asked consumers whether they wanted an expensive MP3 player with premium packaging, the iPod wouldn't exist.

Where Design Thinking Goes Wrong

There are predictable ways this breaks.

Problem theatre
Teams cluster problems until they lose all sharp edges. Themes replace specifics. Vague language replaces decisions.

Say-do confusion
Surveys and interviews surface stated needs. They rarely reveal latent ones. Without observation, teams design partial solutions.

One-to-one mapping fantasies
One problem does not need one solution. One solution may address multiple problems. Forcing elegance here creates fragility.

Early constraint collapse
Teams shut ideas down with "we can't do that" instead of asking why they can't: cost, capability, timing, or fear.

Research as procrastination
Over-research becomes a way to avoid committing. Confidence doesn't increase; time just passes.

How Experienced Practitioners Choose What to Do Next

Good judgment lives between art and science.

There are moments where intuition matters, when a problem or solution feels too important to abandon. But intuition without evidence is ego. Evidence without judgment is paralysis.

Evidence also comes in different fidelities:

• Existing research and known systemic issues
• Early interviews and behavioural signals
• Synthesis across multiple weak signals

The job isn't certainty. It's conviction proportional to risk.

A key skill is knowing when to:

• Push harder
• Park an idea
• Kill it
• Or go back upstream and reframe the problem

Parking is not avoidance. It's a strategic decision based on timing, intent, and constraints.

And momentum matters. Indecision kills more innovation than wrong decisions.

Why Order Matters More Than Tools

Once ideas become concepts, and concepts become propositions, the work isn't done.

Propositions should be reformed based on learning. Features change. Benefits shift. Some die. Others are parked because they don't match strategic intent: near-term revenue vs future bets.

Sometimes the honest outcome is that none of the ideas are good enough. The right move is to go back to the problems, not force a launch.

Before real budget is committed, propositions should face reality:

• Lightweight prototypes
• Landing pages
• Shadow or ghost brands
• Live experiments

Real market feedback, cost per click, sign-ups, repeat behaviour, will always trump internal research. Willingness to pay cannot be reliably discovered in a survey. This is where experimentation shifts from validation to learning.

Only after this should serious money flow.

User Psychology and Organisational Psychology

User psychology

The say-do gap is structural. People explain behaviour after the fact.

You don't start with ethnography. You start with what's already visible: reviews, forums, behaviour, social signals. That gets you most of the way.

Observation is for what's hidden by context. A wheelchair user's problem isn't just entering a taxi. It starts at the building exit, the pavement, the weather. Journey mapping exposes the edges. Ethnography reveals the truth.

Small samples are enough if chosen well. The goal is insight density, not scale.

Pricing research is especially misleading. Only live tests reveal real willingness to pay.

Organisational psychology

Many decision-makers have never run end-user work. That's not a criticism. It's reality.

Fear of failure, ego, legacy habits, and bad research all distort decisions. Large launches feel safer than small tests. They aren't.

Learning that something won't work is not failure. It's cost avoidance.

Practitioners also carry responsibility:

• Don't be arrogant about process
• Don't dismiss what came before
• Don't hide behind jargon

If stakeholders don't understand your language, that's on you.

Stakeholder mapping matters. Know who unlocks budget, who blocks progress, who needs to be neutral, and who must become a promoter. Manage that deliberately.

If You Remember One Thing

Don't launch what you like.

Design propositions for reality:

• Real unmet needs
• Real willingness to pay
• Real organisational constraints

Test to learn. Change your own bias.

Stop researching things to death when live learning is cheaper and faster.

Drop the arrogance about process.

Keep it simple.

Design thinking isn't the point.

Designing propositions that survive reality is.