What is Speculative DesignPart 8

Bringing It into Tomorrow's Meeting

How can a product team, with neither a museum nor a government commission, use speculative design? A summary of a small-scale process you can try, and the traps people often fall into.

Even if you find speculative design fascinating to read about, the sprint board is waiting when you get to work the next day. So this method can easily feel far removed from practice, but scaled down, parts of it can be used by an ordinary product team.

First, let me set expectations clearly. The process below isn’t a standard in the field; it’s one approach put together from the works we’ve looked at so far. And this method won’t plan next quarter’s roadmap for you. That’s still the job of research and data. What this method does well is bring out the assumptions a roadmap takes for granted.

When It’s Worth Using

Not every project needs it. It’s worth trying when you see signs like these.

  • “Everyone’s going that way anyway” comes up often in meetings.
  • The metrics are improving, but an uneasy feeling lingers in the team.
  • You’re dealing with a technology that has no shape yet, one that users can’t easily answer questions about.

A Process for Half a Day

As an example, imagine a team building a customer support service. The team is preparing a feature that automates support with AI.

1. Write down the default. Write what will happen five years from now if current trends simply continue. Most support may be handled by AI, and talking to a person may mean going through a difficult process or paying for it. This step puts the center of the futures cone, the default future, into words first.

2. Twist it with “What if.” Change one of the default’s assumptions. “What if the right to talk to a person were guaranteed by law?” “What if users sent their own AI to negotiate with ours?” “What if support conversations were used in credit scoring?” This isn’t the place to find the right answer, so write down both the futures you want and the ones you don’t.

3. Make one prop. This step is the core. Make a small, ordinary object that could plausibly have come out of that world. A price list for “human support passes,” a complaint email sent by a user’s AI, an update notice for the support app, a grumbling post on a community forum: any of these is enough. The key is not to explain the future but to write it like an everyday document from that world. With a design tool, it takes about an hour.

4. Ask about the subject. Use the question from the previous piece here. Who benefits in this future? What happens to customers who aren’t articulate or aren’t comfortable with digital devices? Where did the support agents go? Also write down who isn’t in the room.

5. Come back to today’s decisions. Finally, look at the prop and ask: which future is the feature we’re preparing today taking a step toward? If there’s a future you want to prevent, what can you change in this spec? It’s fine to come back to something as small as where to put the button that connects to a person.

A Few Traps

When you actually try it, people often slip at points like these.

  • It turns into a product mockup. When a prop comes out looking great, it drifts toward “Let’s build this.” That’s the road toward the Corning video we saw earlier. Deliberately making at least one uncomfortable prop helps.
  • It only wrecks the world. Drawing dystopias is easy and fun, but on its own it leads to no decisions. If you’ve drawn a bad future, also work through what it would take to prevent it.
  • The same people do it together. When only teammates with similar backgrounds gather, imagination stays in a similar range too. It’s good to invite support agents, colleagues from other departments, and, if possible, actual users.
  • It ends without a conclusion. All that remains is the feeling that it was fun. In the last step, write down at least one question or decision to carry into the current spec.

Why It’s Fine to Start Small

Some may say this scaled-down approach isn’t real speculative design. It never left the market, and in the end it was used for a company’s product. That’s not wrong. If you present this as critical work, it could become another example of the language of critique being absorbed into marketing, as we saw earlier.

Still, this small exercise is clearly useful, because it turns “It’ll happen that way anyway” into “We’re choosing that direction.” The moment you realize that deciding the future isn’t the business of someone far away but is tied to today’s spec, a designer’s responsibility gets a little heavier, and what they can do grows a little wider.

The next piece is the last in this series. After going through all the criticism so far, I’ll talk about why we should still speak of a preferred future.