Reach / Robust / Resonance

Reach

Year-end story (Aug 2027)

We sit down for ice cream and can say:

• “Flash Lab is running in places we’ve never been, run by people we’ve never met, and the participants are leaving with the real thing. Not a watered-down version.”
• “Three of our seed grant prototypes are now in published research.”
• “When ISTE / NewSchools / a foundation needs a credible Stanford voice on AI+learning, we’re who they call.”
• “The Studio shows up in conversations we weren’t in the room for.”

What’s in the Studio’s control

• Scoping. Choosing which asks turn into which formats (e.g., 90-min ISTE to train-the-trainer pivot).
• Support availability. How much capacity we put behind a relationship at each lifecycle stage.
• Format design. The structure that determines whether the work travels.

What’s in my control

• What I publish. Toolkits at designkit.stanford.edu and bot101.app. The next-layer artifact (Flash Lab basic vs. deluxe; the cost sheet, one-pager, case studies) makes the offering legible to outside money.
• Who I train. Courtney, Anna-Lena, Gregory. Independent facilitators are the cleanest unit of Reach. The ISTE train-the-trainer is the next order of magnitude.
• Where are our workshops? ISTE Live (locked in), SXSWedu(?), Stanford

Talents I bring

• Build + facilitate in the same person. The combination is what makes Flash Lab survive contact with real educators.
• Pedagogical judgment under time pressure. Knowing when 60 minutes isn’t enough. Knowing when a participant is stuck in the wrong loop. Not automatable.
• Stanford trust + working-in-the-weeds. I can sit at a faculty table without being labeled “the IT guy.” Josh’s phrase from Apr 23 (“relationship writer”)

Q1 to today, what we already have

• Toolkits live (designkit, bot101)
• Anna-Lena + Courtney = facilitator independence proven at small scale
• ISTE pipeline = train-the-trainer at organizational scale (in motion)
• Cost sheet drafted = revenue layer takes shape

---

Robust

Year-end story (Aug 2027)

• “Something breaks (a partnership shifts, a tool gets deprecated, a team member leaves) and the work survives.”
• “New people on the Studio team can pick up a Flash Lab and run it without us in the room.”
• “We say no to the wrong asks without losing the relationship.”
• “Our identity holds through the pivots.”

What “robust” means

• Scoping done before build starts
• Front-loading the boring things (governance, IP, hand-off paths)
• Ugly first version that survives a real participant
• Initial buy-in secured so the project doesn’t die when one person leaves
• Sequencing that maintains momentum through the slow weeks
• Defining “good enough” before chasing perfect
• Building in slack instead of optimizing away the margin
• Knowing which decisions are reversible and acting accordingly
• Identity that survives pivots

What’s in my control

• Format Designer mode. The 80% that isn’t code. Defensible against AI tooling.
• Strategic Filter mode. The “no” that protects the format. The pivot that finds the right shape.
• System Designer mode (next move). Not (always) “I build for you” but “here’s how you build for yourself.”

What’s in the Studio’s control

• Capacity discipline. Tag system informing where to invest.
• Lifecycle clarity. SPARK → BUILD → SHARPEN → SCALE.
• Hand-off paths. Clear plans to mark a project finished

The robustness question:

How do we remove the variables that might contribute to failure, so the idea is tested on its own merit?

---

Resonance (proposed third leg)

Why a third R?

Triple-R sounds cool! Also, I think it maps to our previous work.

• Robust = make it durable (inputs / outputs)
• Reach = make it travel (outputs / outcomes)
• Resonance = make it resonate and shift identity (outcomes / impact)

This also maps cleanly onto the partnership criteria filter we talked about on Apr 23: Reach · Revenue/Model Validation · Identity Shift. Resonance is the criterion for Identity Shift. Does the work have a lasting impact on: who we are, who the partner is, or who the participant is?

Year-end story (Aug 2027)

• “An educator who came through Flash Lab in 2025 is now running her own version, and describes herself differently because of it.”
• “When researchers explain what the Studio does to a peer, they don’t say ‘the prototyping team.’ They say ‘the people who help us see what’s possible.’”
• “I describe myself differently than I did in 2025. The role evolved past ‘Emerging Technology Lead’ and we have words for what came next.”

What’s in my control

• What I write down and share. Logic model, blog posts, case studies, Accelerator Handbook, this doc. The artifacts that let the work be repeated and recognized.
• Which framings I sharpen. Broken Proxy, AI Driver’s License, “remove the oracle from the LLM.” Name something true and it travels.
• The reflective practice. Quarterly logic model reviews, EOM Airtable. Our identity sharpens because we get better at articulating it.

What’s in the Studio’s control

• Cross-pollination as a deliverable. Putting SAL grantees, tEquity, and Create+AI in the same room (like we did with Legal 101) is the Studio’s strength and we should treat it as a “product.”