7 Failure Modes of Speculative Design in Organisations

Most accounts of speculative design tell success stories. We have a long list of those, and we are happy to tell them. But the more useful thing — for anyone trying to apply this work in a real organisation — is the failure pattern.

After fifteen years of working with start-ups, multinationals, public institutions, and NGOs, we have learned that speculative design fails in organisations more often than it succeeds, and it almost always fails in the same ways. The seven patterns below cover the majority of what we see. None of them are about talent or budget. All of them are about how the work is framed, scoped, and absorbed.

1. The work is positioned as inspiration instead of decision

This is the single most common failure mode. Leadership commissions speculative work to "get the team thinking differently" with no defined decision the work is meant to inform. The artefacts are produced, the screening happens, everyone is mildly inspired, and three months later nothing has changed.

The remedy is to insist, from the framing workshop onward, on naming the decisions the work is supposed to feed. What capex line will this affect? What hiring decision? What portfolio choice? If no one in the room can answer, you do not have a speculative design brief — you have an entertainment brief, and you should price it accordingly.

2. The brief is too close to the existing roadmap

Closely related, but distinct. The brief says "speculate" but constrains the work to the categories, customer segments, and time horizons of the current strategy. The result is futures that look like the present with one new feature. The organisation's actual blind spots are protected from the work.

The tell: every scenario the team produces sits inside the same five-year strategic plan everyone has already seen. The fix is in the framing workshop — name explicitly, in writing, which assumptions the work is allowed to break. Without that, the brief will quietly reassert itself every week.

3. Provocation gets diluted in stakeholder review

The team produces work that is genuinely uncomfortable. It goes to a stakeholder review. By the time it comes out of the third round of revisions, all the edges have been sanded off. The artefact is now "safe" — and useless. Provocation that has been made comfortable is no longer provocation.

This is structural, not personal. Stakeholders are not bad actors; they are doing what review processes are designed to do, which is reduce risk. The solution is not to argue harder in the review. It is to set up the engagement so that some of the work is explicitly outside the review process — a "provocation track" alongside the "delivery track." Treat the provocative work as research output rather than client deliverable, and the dilution pressure largely vanishes.

4. The aesthetic does the wrong rhetorical job

Designers default to the register they are best at. If the team is good at glossy product renders, the speculative artefacts look like product renders. If they are good at editorial film, the speculations look like films. The choice of register is treated as a stylistic preference rather than a rhetorical decision.

The cost is real. A glossy render of a fictional product reads as a near-term roadmap leak; a documentary film about a future reads as a prediction. Both close down the conversation they are meant to open. The fix is to choose register deliberately — what argument is the artefact trying to make, and what aesthetic best does that argument? — and to do so before any production begins.

5. The future is built bottom-up

The team starts by designing the artefact: the fictional product, the new service, the imagined interface. They reason from the artefact outward to the world that contains it. The result is a beautiful object floating in nothing, with no internal logic, no coherent culture around it, no plausible institutional or infrastructural support.

Strong speculative work builds top-down: what does this world believe? What institutions does it have? What infrastructure? What practices? Then — and only then — what artefacts do those practices produce? When organisations dismiss speculative work as "not serious," nine times out of ten it is because they are looking at bottom-up work and they are right to be unconvinced.

6. The organisation has no mechanism to absorb the output

The work is excellent. The framing was right, the artefacts are sharp, the implications are clear. And then the deck goes to a director, who lacks the authority to act on it. Or it goes to a strategy team, whose annual planning cycle closed last month. Or it goes to product, who already have the next two roadmap cycles locked.

Speculative design does not absorb itself. Before the work begins, identify the receiving function — who, specifically, will own the implications, and at what point in their cycle. If there is no answer to that, the project will produce orphan insight. We have seen this kill more genuinely good speculative work than any other failure mode.

7. The work is judged by whether the future arrived

Eighteen months later, someone in the leadership team says "well, that didn't happen, did it?" The speculative artefacts did not become real products; the world did not unfold as the scenarios described. Therefore the work was wrong. Therefore the methodology does not work. Therefore the next budget cycle does not fund it.

This is a category error. Speculative design does not predict futures; it makes possible futures available to present-day decision-making. The right evaluation is not "did this future arrive?" but "did this work change a decision we would not otherwise have made?" If the answer is yes — even if the specific scenario looks dated in hindsight — the work paid for itself. The organisations that succeed with this discipline learn to evaluate it in the present tense.

A note on what these failure modes share

Six of the seven failures above are not failures of the design work itself. They are failures of how the organisation frames, reviews, and absorbs the work. The lesson we have drawn from this, repeatedly, is that speculative design projects need at least as much attention paid to the organisational scaffolding around the work as to the work itself. Designers tend to assume the scaffolding is someone else's problem. It is not.

If you are commissioning speculative work, ask the design team how they will avoid each of these seven patterns. If they do not have answers, they are not yet a partner you can trust with a budget. If you are doing the work yourself, run the failure modes as a checklist before you start, at the midpoint, and at the end. The work is not finished when the artefacts are finished; it is finished when the organisation has acted.

Key takeaways

• •Speculative design fails predictably, and almost always in the organisational scaffolding around the work rather than in the work itself.
• •The most common failure is positioning: work commissioned as "inspiration" with no named decision to inform.
• •Diluted provocation, bottom-up world-building, and aesthetic-as-default-not-rhetoric are common production-side failures.
• •Absorption is structural: identify the receiving function and its decision cycle before the work begins.
• •Do not let the work be evaluated by whether the future arrived. Evaluate it by what decisions it changed.

Related reading

• •The Speculative Design Methodology: A Practitioner's Workflow — the workflow these failure modes derail.
• •Measuring Speculative Design ROI — how to evaluate the work in the present tense.