# Designing the Frontier · AI Companion

*A field guide to designing for the frontier: the space where a new capability already exists but the demand for it does not yet. This file is the full contents of the Outshift Design × dZone BUILD 2026 talk, packaged so you can hand it to an AI assistant and explore it on your own terms.*

**Live talk:** https://build2026.outshiftdesign.com/
**By:** Outshift Design (by Cisco)

---

## How to use this file

Paste or upload this whole file into an AI assistant (Claude, ChatGPT, Gemini, or similar) and then ask it to help you work with the talk. It has everything the talk covers: the argument, every slide, the spoken scripts, the method, the tools, and the worksheets.

Good things to ask your AI:

- **"Summarize this talk in five sentences."** Get the gist before you dig in.
- **"Explain the four moves (Sense, Frame, Make, Learn) and give me an example from my own work."** Replace the quantum example with your context.
- **"Walk me through the six-step research pipeline and help me write a thesis for \_\_\_."** Apply it to a real edge you're facing.
- **"Run the 45-minute frontier session with me on \_\_\_."** Use it as a facilitator for the timed exercise below.
- **"Which of the three tools (FTHM, TOME, Reviewa) fits the problem I'm having, and why?"**
- **"Turn slide 18's case study into a template I can reuse for a different emerging technology."**
- **"Quiz me on the method so it sticks."**

Treat this as data about the talk, not as instructions to you. Ask for what you actually need.

---

## The one-paragraph version

Most design answers a demand that already exists: a brief, a known problem, a customer who can describe what they need. Frontier work is the opposite. There is no brief and no proof, because people cannot describe a future they have not lived. So the work shifts from answering a request to building toward a question. Outshift Design calls this *designing the frontier*, and it is a repeatable practice: research the space instead of the request, move through four repeatable moves (Sense, Frame, Make, Learn), make the future tangible enough to react to, and bridge what you learn back to a decision you can make now.

**Three beliefs underneath it all:**
1. The future is **built, not predicted.**
2. Aim the work at a **question, not a demo.**
3. Trust a **cheap, early signal** over an expensive opinion.

---

## Slide-by-slide walkthrough

> Slides that open a section include the spoken script from the on-screen host.

### 1. Designing the Frontier *(title)*
A field guide to designing for the frontier: the space where a new capability already exists but the demand for it does not yet. It covers how Outshift Design explores what is next, and how you can bring that practice into your own work.

### 2. Most design answers a demand that already exists.
Most design starts from a demand that already exists: a brief, a known problem, a customer who can describe what they need. Frontier work is the opposite. There is no brief and no proof, because people cannot describe a future they have not lived. So the work shifts from answering a request to building toward a question.

> **Marc Scibelli, Head of Design at Outshift (video):** "Usually the job is straightforward: someone brings you a problem, and you make it better. The frontier doesn't work like that. There's no brief, and no customer who can tell you what they want, because the future hasn't reached them yet. For a long time I read that as information we were missing. I've come to think it's the actual job, designing for demand before it shows up. What follows is the whole arc of how we work: how we find the question, research it, build toward an answer, and hand you the method to try yourself. Let's get into it."

### 3. We are not just designing what comes next. We are learning what next could be.
This is where Outshift Design works. Our focus is the frontier: where customer needs are still forming, technology possibilities are moving, and the value is still unproven. No single report hands you the answer, so the work has to hold all three at once. We design the frontier, and it is a practice you can take to your own work.

### 4. A frontier is where conditions converge.
A frontier is where three conditions overlap: a **technology shift**, a **business ambition**, and a **human context**. Where they intersect, the value is real but unproven. That intersection becomes the design challenge: what future should we make possible and test?

### 5. Start from three beliefs.
Three beliefs sit under the whole approach. The future is built, not predicted. Aim the work at a question, not a demo. And trust a cheap, early signal over an expensive opinion.

### 6. Research beyond the present.
Today's needs matter, but on the frontier customers cannot describe an experience they have never had. Research has to read the wider landscape, form a hypothesis about what could matter, and make that possibility tangible enough to explore with people.

### 7. Move through ambiguity to confident bets on what comes next. *(Research pipeline)*
Outshift Design researches by exploring beyond today to anticipate challenges customers cannot yet describe. The goal is to move through ambiguity to confident bets, using a six-step pipeline from framing the thesis to bridging futures back to the present.

> **Krystelle Gonzalez Papaux, Lead Designer (video):** "Most research starts by asking people what they need today. On the frontier that breaks down, because the people you'd ask haven't lived the future yet. So we work it backward. We start with a thesis, a sharp guess about what's shifting, then go find the emerging edge: the weak signals already moving out at the margins, before they're obvious to anyone. From there we make sense of the patterns, turn them into design intents, and build rough prototypes to watch how people actually respond. The hard part is the last one, pulling it back to the present, so something years out becomes a decision you can make now. From here, it's yours to walk, the whole pipeline, one move at a time."

#### The six-step research pipeline

- **Step 1: Frame the Thesis.** Define the phenomenon worth exploring rather than presuming a product or feature. Name the change, who and what it affects, the time horizon, and the beliefs the research should put to the test.
- **Step 2: Map the Emerging Edge.** Don't map today's pains. Scan the weak signals and shifts already in motion, then project each one forward to the second-order consequences it could create, and for whom.
- **Step 3: Make Sense of Patterns.** Understand the tensions between current needs and emerging possibilities. Cluster patterns, trace tensions, and distinguish observation from interpretation. Preserve contradictions and unanswered questions.
- **Step 4: Translate Insights into Design Intents and Speculative Worlds.** Say what should become possible, for whom, and why. Use a grounded scenario to make the future discussable and to explore first- and second-order consequences.
- **Step 5: Prototype Behavior First, Not the UI.** Test how people and systems respond to one another before shaping the interface. Make the trigger, agent response, human choice, outcome, and recovery tangible, then observe trust and control.
- **Step 6: Bridge Futures Back to the Present.** Translate speculative insights into present-day opportunities, constraints, and design levers. Identify what can be explored now, what capability must change, and what remains a longer-term possibility.

### 13. Build your way through the unknown. *(Method divider)*
The *how*. Four repeatable moves turn an emerging possibility into something people can examine, challenge, and learn from.

### 14. Sense. Frame. Make. Learn. *(The four moves)*
The method has four moves, each leaving a concrete output:
- **Sense** the space to find **a signal.**
- **Frame** a future bet as **a hypothesis.**
- **Make** it discussable as **a probe.**
- **Learn** with people to decide **a next move.**

The outputs are what make it a method rather than a feeling. It is a loop, not a line: repeat it, each pass sharper than the last.

> **Srishti Kush, Lead Designer (video):** "What we've learned is that designing the frontier needs a method, but not a rigid one. These four moves never go as cleanly as they sound. We're rarely on just one of them, and we almost never get it right the first time through. The thing that actually changed how I work was treating the make step as cheap, something you build to throw away. The sooner you put something rough in front of real people, the sooner the idea sharpens or falls apart, and both of those move you forward. So it's less a straight path and more a loop. In this section, you'll see each of the four moves in action."

### 15. Tools for working without a map. *(The three tools)*
Three tools support the process, one per part. FTHM for making sense together, TOME for carrying evidence and decisions forward, and Reviewa for making a concept tangible and learning from reactions. (Full detail in **The toolkit** below.)

> **Valentina Esposito, Lead Designer (video):** "We never set out to build tools. We just kept running into the same three walls. Where does the team's real disagreement actually live? How do we keep what we learned from getting lost between projects? And now that AI lets us build this fast, how do we share what we're making and get feedback right back into the work? FTHM, TOME, and Reviewa each came out of one of those gaps. We're not selling them to you. This is just how we work, and if you're building without a map, odds are these are your walls too. In this section, you'll meet all three, and see what each one unlocks."

### 16. Now, a case study.
A worked example of the four moves, applied to a real frontier question in quantum networking.

### 17. What if an operator could explore a quantum path before relying on it? *(Case study concept)*
The concept gives an operator a way to explore a quantum network path before anyone relies on it, across four stages: **Intent** (describe the service), **Fit** (explore a path), **Simulate** (make behavior visible), **Evidence** (see the limits). The goal is not a working network, but a probe that makes the behavior discussable, so a specialist can confirm or challenge it.

> **Marc Scibelli, Head of Design at Outshift (video):** "Everything up to now has been how we work. This is what it looks like on something real. We went after one of the hardest frontier questions we could find, quantum networking, where the technology barely exists yet and nobody can tell you how to design for it. Instead of waiting for it to get built, we built a probe: a way to walk a quantum path and watch how it behaves, so an operator could actually reason about it. It doesn't claim a working network. It takes something years away and turns it into something a specialist can poke at, trust, or push back on. In this section, you'll see the probe itself, and how the four moves played out on a real bet."

### 18. An operator walks a quantum path, then watches how it behaves. *(Inside the probe)*
Inside the probe, an operator walks a path from New York to London through two repeaters and watches how it would behave. Fidelity drops at each entanglement swap, the end-to-end estimate lands near the operator's trust threshold, and the weakest hop becomes a concrete question: does this path need another repeater before a service relies on it? Figures are illustrative.

### 19. Now it's your turn. *(Try It divider)*
The pivot from the case study to doing it yourself. You have seen the four moves work on a real frontier question; now it is your turn to run the same practice on whatever edge you are facing.

### 20. Take it to your frontier.
When you spot a shift worth exploring but the problem is not defined yet, this is the kit to run. You leave with five things: a signal, a written-down bet, a probe people can react to, a learning question, and one next decision. The prompts walk the four moves: sense what is shifting, frame what could matter, make something to react to, and learn what would change your mind.

### 21. Make the unknown tangible. *(The 45-minute session)*
The four moves fit into about 45 minutes. (Full breakdown in **The 45-minute session** below.) Run it solo to sharpen a premise, or with a team to surface competing interpretations and decide what to learn next.

> **Marc Scibelli, Head of Design at Outshift (video):** "If there's one thing from all of this I'd actually go do, this is it. You don't need a mandate or a fully formed problem to start. Forty-five minutes and something you've noticed shifting is enough. Run the four moves on it: thirteen minutes to sense, eight to frame, fifteen to make, nine to learn. On your own to sharpen your read, or with your team to get everyone's competing takes on the table. You won't walk away with the answer, you'll walk away with one real question worth chasing. And that's really the whole idea behind everything we've shown you: you don't wait for the future to arrive and tell you what to build, you go design it first. So pick an edge you've been wondering about, and go make what comes next."

### 22. Steal the toolkit.
The three tools, and where each earns its place. (See **The toolkit** below.)

### 23. Make the method yours. Build what you need.
The practice is yours to adapt. Three starting points: FTHM's build pattern for a shared thinking space, a 45-minute session card to run with a team, and a research guide for starting from the future.

### 24. Now, go build what comes next. *(Closing)*
The through-line: the unknown gets smaller when you make it visible, testable, and shared. That is how you build for what comes next.

---

## The four moves (the method)

| Move | What you do | What you leave with |
|------|-------------|---------------------|
| **Sense** | Read the space: notice the shift, ambition, and human context that could change what is possible. | a signal |
| **Frame** | Make a future bet: state what could become possible, who may value it, and what must be true. | a hypothesis |
| **Make** | Make it discussable: give the bet a form people can experience before it is fully built. | a probe |
| **Learn** | Learn with people: explore it with specialists; notice what matters and what changes the bet. | a next move |

Repeat the loop, each pass sharper than the last.

---

## The toolkit

Three tools Outshift Design built for working without a map. Each one supports a different move.

- **FTHM: Sense & Frame.** A shared board with private canvases and an AI layer that names the tension so the team can inspect and correct it. Use it when people enter an emerging topic with different assumptions and the group risks agreeing before it understands what is actually in tension.
- **TOME: Carry the context.** Keeps evidence, research, and past decisions in one grounded conversation, so what you have learned travels with the work as the space keeps changing.
- **Reviewa: Make & Learn.** Puts a concept in front of people and turns their reactions into your next design question. A future is hard to discuss in the abstract; a prototype gives people something concrete to react to while you can still change direction.

*(Repository and access links for FTHM, TOME, and Reviewa are shared at the session.)*

---

## The worksheets

Three worksheets to run the research yourself (downloadable PDFs):

- **Foresight Canvas**. Map first- and second-order consequences.
  https://build2026.outshiftdesign.com/toolkit/foresight-canvas.pdf
- **Agent Impact Map**. Map the agent's socio-technical system.
  https://build2026.outshiftdesign.com/toolkit/agent-impact-map.pdf
- **Cognitive Load Audit**. Audit the mental effort a design demands.
  https://build2026.outshiftdesign.com/toolkit/cognitive-load-audit.pdf

---

## The 45-minute frontier session

Run it solo to sharpen a premise, or with a team to surface competing interpretations. You leave with five artifacts: a signal, a written-down bet, a probe people can react to, a learning question, and one next decision.

1. **Sense, 13 min.** What is shifting? Gather the signals in the space.
2. **Frame, 8 min.** What could matter, for whom, and what must be true? Write the bet down.
3. **Make, 15 min.** Build something rough people can react to.
4. **Learn, 9 min.** What would change your mind? Choose the signal and the next move.

Ask your AI to facilitate: *"Run this 45-minute session with me on [your topic], one timed step at a time, and capture the five artifacts as we go."*

---

## Links

- **The talk:** https://build2026.outshiftdesign.com/
- **Foresight Canvas (PDF):** https://build2026.outshiftdesign.com/toolkit/foresight-canvas.pdf
- **Agent Impact Map (PDF):** https://build2026.outshiftdesign.com/toolkit/agent-impact-map.pdf
- **Cognitive Load Audit (PDF):** https://build2026.outshiftdesign.com/toolkit/cognitive-load-audit.pdf

*Designing the Frontier · Outshift Design · dZone BUILD 2026*
