Read the space
Notice the shift, ambition, and human context that could change what is possible.
a signalOutshift Design
What it takes to build for the edge of the known.
This is a field guide to how Outshift Design explores what's next, and how you can bring that practice into your own work.
The frontier is the opposite problem. You design before the demand exists, with no brief, no proof, and no customer who can describe a future they have not lived.
Our focus is where...
People feel the friction before they can name the future they need.
The question shifts from "what can it do?" to "what should it make possible?"
We have to learn what matters, for whom, and under what conditions.
Here's how we explore it, build on it, and learn our way across it, so you can do the same.
No single signal tells us what to build. The work is to form a useful hypothesis from the intersection of a technology shift, a business ambition, and a human context.
The future is built, not predicted
You do not forecast the frontier. You make a piece of it real enough to react to.
Aim at a question, not a demo
Frame the belief that, if it is wrong, ends the idea, before you build. The artifact's only job is to earn a yes or a no.
Trust the cheap signal, not the expensive opinion
Put rough work in front of people whose reaction you trust, early, before the budget makes you need it to be true.
Today's needs matter. But customers cannot describe a future they have not experienced. So research has to understand the wider space, form a hypothesis about what could matter, and make that possibility real enough to explore.
Our six step process is how we get there, turning emerging signals into hypotheses we can test and act on.
We begin by defining the phenomenon worth exploring, rather than presuming a product or feature.
How might AI agents change how people coordinate complex work in a world where agents can act across multiple tools and services?
We don’t map today’s pains. We scan for the weak signals and emerging shifts already in motion, then project where they could lead.
Trace the trajectory of AI agents acting across tools and services: not how people coordinate work today, but the new behaviors, dependencies, and risks that emerge as agents take on more.
Steal the templateForesight Canvas ↗We seek to understand the tensions between current needs and emerging possibilities.
Identify tensions between how people coordinate work today and how AI agents could reshape that in a world where agents act across tools and services.
Steal the templateAgent Impact Map ↗We explore how a design intent could shape first and second-order consequences.
How might we help people see what an AI agent is doing, understand why, and redirect it while it coordinates work across tools?
We test how people and systems respond to one another before shaping the interface.
Prototype the agent’s behavior in a short scenario and observe how a person responds before designing the interface.
Steal the templateCognitive Load Audit ↗We translate speculative insights into present-day opportunities, constraints, and design levers.
Backcast from a future where AI agents coordinate complex work across tools and services: what can we do today to prepare people to work with them?
Four moves turn an emerging possibility into something people can examine, challenge, and learn from.
Notice the shift, ambition, and human context that could change what is possible.
a signalState what could become possible, who may value it, and what must be true.
a hypothesisGive the bet a form people can experience before it is fully built.
a probeExplore it with specialists. Notice what matters, what changes the bet.
a next moveEach tool supports a different part of the process.
A shared board, private canvases, and AI that names the tension.

Evidence, research, and prior decisions in one grounded conversation.

Make a concept visible and turn reactions into the next design question.

See the four moves work on a real frontier question: an illustrative quantum networking probe that helps an operator explore a path before anyone relies on it.
A probe makes the behavior discussable. It does not claim a working quantum network: fidelity drops across each swap, the end to end estimate lands near the operator's trust threshold, and the weak hop becomes a concrete question a specialist can confirm or challenge. Figures would be illustrative.
You have seen the four moves work on a real frontier question. Here is how to run the same practice on your own.
When you spot a shift worth exploring but the problem is not defined yet, run this. Solo to sharpen a premise, or with a team to make competing reads visible.
Run the four moves in 45 minutes. Solo to sharpen a premise, or with a team to make competing interpretations visible and decide what to learn next.
Map a technology shift, business ambition, and human context, and the questions they raise together.
Describe what could become possible, for whom, and what must be true.
Sketch one scenario or service moment that lets someone encounter the possibility.
Look for evidence that would make you keep, change, or drop the hypothesis.
Three tools we built for working without a map. Use each at the move where it helps most.
Open a shared board, give everyone a private canvas, and let an AI layer name the tension so the team can inspect and correct it.
Steal the repo ↗Keep evidence, research, and past decisions in one grounded conversation, so what you have learned travels with the work.
See how we built it ↗Put a concept in front of people and turn their reactions into your next design question.
Steal the repo ↗The practice is yours to adapt. Three starting points to make sense of an emerging opportunity, build your own sensemaking space, and explore it with your team.
A shared board, private canvases, and an AI layer that names a possible tension for people to inspect and correct.
Four moves, timed prompts, and the artifacts to leave with: a signal, a bet, a probe, and a learning question.
Read changing conditions, ground a future hypothesis, and use tangible concepts to learn with people.
One file holds everything in this session: the argument, every slide, the spoken scripts, the four moves, the tools, and the worksheets, formatted to hand straight to an AI assistant. Drop it into Claude, ChatGPT, or your tool of choice and let it parse the talk for you, apply the method to your own work, or facilitate the 45-minute session.
Designing the Frontier · Outshift Design
The unknown gets smaller when we make it visible, testable, and shared.
The whole talk in one file, built for an AI to read.
Drop it into any AI to explain the talk, apply the method, and put the lessons and tools to work on your own project.