What strategic design actually is (and isn't)

A client asked us in a proposal meeting last month what we actually meant by "strategic design." It was a fair question. They'd been pitched the term by three different consultancies that year — one of them a management consultancy, one a brand agency, one us — and none of the three had used the word to mean the same thing. They wanted to know what they'd be buying.

I've been running a strategic design consultancy for the better part of a decade, and the question gets harder, not easier, to answer over time. Not because the practice has changed — it hasn't, much — but because everyone else's has.

So here's the answer I gave them.

What we mean by strategic design

Strategic design is the practice of using design methods — research, framing, prototyping, narrative-making — to determine what an organisation should do, not only how it should do it.

Three qualities matter.

Strategic design is research-grounded. The recommendations come from interviews with people the organisation is trying to serve, not from desk research or internal workshops. When we worked with TAC on their internal communications strategy, the strategic direction came from over fifty interviews with staff across the organisation. The synthesis was a synthesis of what the organisation actually was — not what the executive team thought it was.

Strategic design produces artefacts that survive the engagement. A good strategic design output isn't a deck — it's a set of working documents the organisation can hand to the comms team, the product team, or the procurement team. When we worked with Headspace on their strategic narrative for schools and communities, the engagement produced the narrative itself, but also a brief template the Headspace team now uses to commission new programs. The framework outlived the consultancy hours.

Strategic design treats organisations as systems where humans determine whether the strategy survives reality. Most strategy work treats people as variables to optimise. Strategic design treats them as the substrate. This is the assumption design brings to strategy — that an idea is only as good as the people who can actually carry it. Our framework for human-centred systems change covers the underlying theory.

What strategic design isn't

The clearer way to define strategic design is by drawing it out from four neighbours.

vs Design strategy

Design strategy is about the design function inside an organisation — how the design team operates, what its standards are, where it sits in the org chart. Strategic design uses design methods to set direction for the organisation as a whole.

A design leader rewriting a team charter is doing design strategy. A design team helping the Menzies Foundation rethink the role of schools as multi-opportunity communities is doing strategic design.

vs Service design

This is the most common confusion. Service design works at the touchpoint level — how a citizen experiences enrolling in a service, how a patient navigates a clinic, how an employee gets onboarded. The unit of analysis is the journey.

Strategic design works at a different zoom level. It asks why the service exists, what change it is meant to produce, and whether the system around it makes that change possible. You can do excellent service design on a service that shouldn't exist. Strategic design is what determines whether the service should exist at all.

The practical version: if the brief is "make this service better," that is usually service design. If the brief is "we don't know what this part of our organisation should be doing in five years," that is strategic design.

vs Management consulting

This is the most contested boundary, because both practices claim to set strategic direction. The difference is in what gets produced and what happens to it.

Management consulting tends to produce written strategy — analysis, recommendations, frameworks, presented in slides. It is excellent at structured thinking. It is often weaker at translating that thinking into something the rest of the organisation can pick up and operate from. The slides leave. The implementation often stalls.

Strategic design produces the strategy plus the working artefacts of execution. The TAC engagement produced a communications strategy, but it also produced a set of editorial principles and message frameworks the internal comms team uses to make day-to-day decisions. Six months later, the strategy is still in active use, not waiting for the next consulting engagement to revive it.

vs Design thinking

This is the most fraught comparison, because design thinking is the older relative — the methodology that came out of Stanford and IDEO in the early 2000s, organised around empathy, ideation, prototyping, and testing. It is a real practice with real wins behind it. A lot of the design profession working in industry today learned to talk about their craft through its vocabulary, and plenty of strategic design teams (ours included) came up through it.

But the two practices ask different questions. Design thinking asks: what solution might work for this user? Strategic design asks: what should the organisation be doing in the world, and how does it get there?

Design thinking treats the user as the locus of insight — the protagonist whose unmet need is the design problem. Strategic design treats the organisation and the system around it as the unit of analysis. A user who can't navigate a service is a design thinking problem. A government that funded the wrong service in the first place is a strategic design problem.

That's not a hierarchy. Good consultancies do both, and the methodologies overlap heavily in the early stages — research, framing, prototyping all show up in either practice. But they aren't the same thing, and confusing them produces bad commissioning. Design thinking teams briefed on strategic problems produce solutions to the wrong question. Strategic design teams briefed to run a sprint produce strategy when what was needed was a prototype.

When you actually need strategic design

Three signals suggest an organisation needs strategic design rather than one of the practices it gets confused with.

The first is that strategy keeps getting written but never lands. If multiple consultancies have produced multiple strategies in the past few years and none have taken hold, the problem is rarely the strategic thinking. It is the gap between thinking and the people meant to act on it. Strategic design closes that gap by producing strategy in forms the organisation can operate from.

The second is that the people being served have lived experience the leadership doesn't share. Public services, health, justice, disability, energy transition — these are domains where strategic decisions made without research with affected populations tend to produce strategies that fail in implementation. Our work on DSP Help, supporting people with disability in the criminal justice system, and systems design for Australia's energy sector with AEMO all started from that premise. Strategic design bakes that research into the strategy itself, which means the strategy has been pressure-tested before it gets adopted.

The third is that the work involves systemic change rather than incremental improvement. If you are reshaping how a sector operates, redirecting a department's purpose, or repositioning a major service, the linear path from analysis to recommendation to execution doesn't hold. The strategy itself has to be designed to survive contact with the system. Our piece on mapping ripple effects in policy change goes deeper on this point.

What to ask if you're commissioning this work

If you are about to commission strategic design work — or you suspect you are paying for something else — these four questions will tell you what you are actually buying.

What research is being done, and with whom? If the answer is interviews with your executive team, that isn't strategic design. That is facilitated thinking with your existing assumptions. Real strategic design grounds in research with the people the strategy will affect.

What does the deliverable look like at the end? If it is a deck and an executive presentation, you are getting management consulting. If it is a strategy plus the working artefacts your team will operate from — narratives, frameworks, principles, prototypes, briefs — you are getting strategic design.

Who owns the work six months later? Good strategic design transfers ownership. If your team can pick up the strategy and run with it, the engagement worked. If keeping the strategy alive requires another contract, it didn't.

Did anyone in the room change their mind? Strategic design that produces no surprises usually means the research wasn't deep enough or the framing wasn't sharp enough. The whole point of grounding strategy in research with affected populations is that they tell you things the leadership didn't already know.

Closing

Strategic design is a real practice with a real definition. It uses design methods to set direction. It is grounded in research with the people the strategy affects. It produces artefacts the organisation can use after the consultants are gone. And it treats organisations as human systems where execution is part of the design problem, not someone else's problem.

If your organisation is in the position of needing strategy to actually land, strategic design is the practice you should be looking for. The four questions above will tell you whether you've found it — or whether the proposal in front of you is one of the neighbouring practices in strategic design's clothing.