Design Thinking Is a Strategy Tool, Not a Workshop Exercise

Design thinking for business strategy is the practice of applying human-centred problem-solving methods to commercial decisions: starting with the people you are trying to serve, defining the real problem before reaching for solutions, and testing ideas cheaply before committing resources at scale. Done properly, it is one of the more useful frameworks available to senior marketers and business leaders. Done the way most organisations do it, it is an expensive afternoon with sticky notes.

The gap between those two outcomes is almost entirely about intent. Companies that use design thinking as a genuine strategic discipline treat it as a way to interrogate assumptions. Companies that use it as a process ritual treat it as a way to feel innovative without changing anything.

What Design Thinking Actually Means in a Business Context

The original framework, developed at Stanford’s d.school and popularised through IDEO, has five stages: empathise, define, ideate, prototype, test. Those labels have been repeated so many times that they have lost most of their meaning. What they are actually describing is a discipline of intellectual honesty.

Empathise means going to find out what is true about your customer’s world, not confirming what you already believe. Define means writing a problem statement that is specific enough to be useful, not a vague aspiration dressed up as a brief. Ideate means generating options without immediately killing them. Prototype means making something tangible quickly. Test means learning from real reactions, not from internal consensus.

None of that is complicated. All of it is harder than it sounds, because organisations are not naturally structured to do any of it well. Most businesses are structured to execute decisions that have already been made, not to question whether those decisions are the right ones.

I spent years watching this play out in agency pitches. A client would brief us on a campaign, we would do the work, and somewhere in the process it would become clear that the brief itself was wrong. The product had a problem. The pricing was off. The customer segment they were targeting had already moved on. The marketing was being asked to compensate for a business issue that marketing could not fix. Design thinking, applied earlier in the process, would have surfaced that before anyone spent money on creative.

Why the Empathy Phase Gets Skipped

The empathy phase is where design thinking earns its keep, and it is the phase that organisations are most likely to shortcut. The reasons are structural. Senior leaders have usually been insulated from direct customer contact for years. Market research gets filtered through layers of interpretation before it reaches anyone with decision-making authority. And there is always pressure to move faster than genuine discovery allows.

The result is that most businesses operate on a version of customer understanding that is somewhere between two and five years out of date. They know what their customers looked like, not what they look like now. They know what those customers said in a focus group, not what they actually do when no one is watching.

Tools like behavioural feedback platforms have made it significantly easier to observe what customers actually do on digital touchpoints, rather than relying entirely on what they say they do. That is not a replacement for real conversation, but it closes some of the gap between assumption and reality.

When I was running iProspect, we grew the team from around 20 people to over 100 across a few years. One of the things that discipline forced on us was a much more rigorous approach to understanding what clients actually needed versus what they said they wanted. Those are often different things. A client asking for more impressions usually needs more pipeline. A client asking for better creative usually has a conversion problem. Getting to the real question underneath the stated question is exactly what the empathy phase of design thinking is supposed to do.

The Problem Definition Step Is Where Strategy Gets Made

If the empathy phase is the most skipped, the define phase is the most underestimated. Writing a good problem statement is a strategic act. It determines everything that follows. A vague problem statement produces vague solutions. A precise one creates genuine creative constraint, which is where good strategy comes from.

The classic design thinking format for a problem statement is the “How might we” question: “How might we help [specific person] do [specific thing] in [specific context]?” The specificity is the point. The more precisely you can define who you are solving for and what you are actually solving, the more useful the ideation phase becomes.

Most go-to-market failures I have seen trace back to a problem definition that was either too broad or never written down at all. The team was aligned on a solution before they had agreed on the problem. That is a common pattern in organisations that are under pressure to show momentum. Design thinking, used properly, forces a pause at exactly the moment when everyone wants to accelerate.

For anyone building or refining a go-to-market approach, the Go-To-Market and Growth Strategy hub covers the broader commercial context in which problem definition sits. Getting the problem right is not a design exercise in isolation. It is the foundation of every strategic decision that follows.

Ideation Without Permission Is Just Brainstorming

The ideation phase has a reputation problem. In most organisations, brainstorming sessions produce a lot of ideas and very little change. The reason is not that the people in the room lack imagination. It is that the conditions required for genuine ideation are almost never present.

Good ideation requires psychological safety, a clear problem statement, and genuine openness to options that might challenge existing commitments. Most organisations can provide none of those things reliably. The HiPPO in the room (highest paid person’s opinion) shapes the output before the session is over. Ideas that challenge current strategy get filtered out before they reach the whiteboard. The session produces variations on what already exists, dressed up as innovation.

I remember my first week at Cybercom. There was a brainstorm for Guinness, and the founder had to step out for a client call. He handed me the whiteboard pen on the way out. I was new, I did not know the account, and the room’s immediate energy was not exactly encouraging. I did it anyway. What that experience taught me was that the quality of ideation has almost nothing to do with seniority and almost everything to do with whether people feel they have permission to say something that might be wrong. Most brainstorms punish that. The best ones create the conditions for it.

The practical fix is simple in theory and difficult in practice: separate idea generation from idea evaluation. Run them as distinct sessions with different rules. In the generation session, nothing gets killed. In the evaluation session, everything gets tested against the problem statement and commercial criteria. The two phases require different mindsets, and mixing them produces the worst of both.

Prototyping Is Not a Design Department Function

The word “prototype” makes people think of product development or UX design. In a business strategy context, a prototype is anything that makes an idea testable before you commit resources to it. That could be a landing page, a one-page proposition document, a conversation with ten customers, or a mock-up of a pricing model. The form is less important than the function: make the idea concrete enough that someone can react to it.

The principle that matters here is that the cost of a prototype should be dramatically lower than the cost of being wrong. If your first test costs six figures, you have not prototyped anything. You have launched. Those are different things with very different risk profiles.

BCG’s work on scaling agile across organisations makes a related point: the value of iterative working is not just speed, it is the reduction of the cost of failure. Small, fast tests produce learning that expensive launches cannot. That logic applies directly to design thinking. The prototype phase is not about making something polished. It is about making something that generates a real signal.

In practice, this means marketers need to get comfortable with things that look unfinished. A rough proposition deck shared with five customers will tell you more than a polished one that never leaves the building. The instinct to make things look complete before sharing them is understandable, but it is the enemy of genuine learning.

Testing Means Learning, Not Confirming

The test phase is where design thinking most frequently breaks down in practice. The intention is to learn from real reactions. What usually happens is that teams look for evidence that supports the direction they have already chosen, and discount evidence that does not.

This is not unique to design thinking. It is a feature of how human beings process information, and it is particularly pronounced in organisations where careers are attached to specific strategic bets. The person who championed an idea is rarely the best person to evaluate whether the test results are telling them to abandon it.

Genuine testing requires defining what success looks like before the test runs, not after. It requires being willing to act on negative results. And it requires distinguishing between a test that failed because the idea was wrong and a test that failed because the execution was poor. Those are different problems with different implications.

The growing complexity of go-to-market environments makes this more important, not less. When markets are moving quickly and buyer behaviour is shifting, the feedback loop between test and decision needs to be short. Organisations that wait for perfect information before acting will consistently be behind those that act on good-enough information and adjust.

I judged the Effie Awards for several years. The work that won consistently had one thing in common: the teams behind it had a clear hypothesis about what would change behaviour, they tested it, and they were willing to iterate based on what they found. The work that did not win was often technically accomplished but strategically vague. It had not been tested against a real question. Design thinking, done properly, is the discipline that produces the former rather than the latter.

Where Design Thinking Connects to Commercial Strategy

The critique of design thinking from commercially minded leaders is usually that it is too slow, too process-heavy, or too focused on user experience at the expense of financial outcomes. That critique is valid when applied to how design thinking is typically implemented. It does not hold when the method is applied with commercial rigour from the start.

The connection between design thinking and business strategy is straightforward: both are disciplines of problem definition. Good strategy starts with a precise understanding of the competitive and customer context. Good design thinking starts with a precise understanding of the human problem you are solving. The methods are different. The underlying logic is the same.

BCG’s research on go-to-market strategy in financial services illustrates how deeply customer understanding shapes commercial outcomes. The organisations that outperformed in that context were not the ones with the best products. They were the ones with the most accurate picture of what their customers actually needed at different life stages. That is an empathy problem before it is a product or marketing problem.

Design thinking becomes a commercial tool when it is used to answer questions that have direct revenue implications. Which customer segment has a problem we can solve better than anyone else? What is the real barrier to purchase, and is it about the product, the price, the message, or the channel? What would we have to believe about customer behaviour for this go-to-market strategy to work? Those are strategic questions. Design thinking provides a method for answering them with evidence rather than assumption.

There is a broader point worth making here. Marketing is often positioned as a function that compensates for business problems it did not create. A product that does not quite solve the problem it claims to solve. A customer experience that does not match the promise in the advertising. A pricing model that creates friction at exactly the wrong moment. Design thinking, applied at the strategy level rather than the campaign level, is one of the few tools that can address those problems before they become marketing’s problem to paper over.

If you are working through how design thinking fits into a broader growth framework, the Go-To-Market and Growth Strategy hub covers the full commercial context, from market entry decisions to scaling and positioning. Design thinking is a method. Strategy is the system it serves.

The Practical Application: Where to Start

Most organisations do not need to adopt design thinking as a company-wide operating model. They need to apply its core principles to the decisions where they are most likely to be working from assumption rather than evidence.

The highest-value applications tend to be: new product or service development, where the cost of building the wrong thing is high; go-to-market strategy, where misreading the customer leads to expensive misdirection; and positioning work, where the difference between a message that lands and one that does not is usually a gap in customer understanding rather than a gap in creative quality.

For teams that want to build this capability without a full methodology overhaul, three practices make the most difference. First, spend time with actual customers before writing any brief. Not a survey. Not a focus group report. A real conversation, or direct observation of how they use your product or interact with your category. Second, write a problem statement before generating solutions, and make it specific enough that someone could tell you whether a proposed solution addresses it or not. Third, test the cheapest version of an idea before committing to the full version.

The growth strategies that have produced durable results at scale share a common thread: they were built on a precise understanding of a specific customer problem, not on a broad aspiration to grow. Design thinking is the discipline that produces that precision. The method is not the point. The precision is.

Vidyard’s research on pipeline and revenue potential for go-to-market teams points to a consistent pattern: the gap between available opportunity and captured revenue is rarely a channel problem. It is usually a targeting or messaging problem, which is to say a problem of customer understanding. That is exactly the gap that design thinking, applied seriously, is built to close.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions