Josh 1:1 Prep — Thu Apr 30, 10:00 AM PT

Apr 23 1:1 left two homework prompts: pen-and-paper free-write on robust (5 min walking + 20 min writing, no computer), and bring a reach framing into this 1:1. Josh’s August-2027 ice-cream-conversation lens applies to both.

Where Apr 23 left “robust”

Josh’s reflection back to you was that robust has two layers stacked on top of each other:

1. Technical robustness — hardening Flash Lab / Build-a-Bot / the toolkit so they hold up when we’re not in the room.
2. Attitudinal/emotional robustness of the team and partners — solidifying the team’s understanding of itself, building partners’ confidence that we’re a serious operation. Josh’s quote: “You’re not just an IT guy — you’re a relationship writer.” And: “When Reuben steps into the room, you get unsucked. We make interesting and novel connections we didn’t know were there. We don’t feel quite so alone.”

Both layers — product hardening AND relational hardening — are doing the same job: making the studio’s work survive contact with the outside world.

Pen-and-paper free-write — priming questions for “robust”

(Josh said no computer for this — these are the prompts to take into the walk + the page.)

1. When Josh said “you’re a relationship writer, not an IT guy,” what did that land on for you? What part of it do you accept, what part do you push back on?
2. If you had to point at three things from Q1 that prove the studio is robust right now — what are they? (Concrete artifacts, moments, partnerships.)
3. Where is robustness currently fragile? What would crack if you got hit by a bus tomorrow?
4. The vibe-coded MVP pattern (SofIA, CRISPRkit) — is filling that gap robust work or is it a sign of fragility somewhere else?
5. August 2027, ice cream after the academic year: what does the “robust” story sound like? What did the studio harden between now and then?
6. What’s the difference between us being robust and what we make being robust? Are they the same project or two projects?

“Reach” — bring this to the conversation

Josh’s framing on Apr 23: what role does the accelerator/studio play in reach, what control do we have, what control does Reuben have.

A few angles to put on the table:

Reach vehicles already in motion

• ISTE Live (locked in — Wed Jul 1, 9–10:30am, AI Pavilion). Session description converged with Josh today on Slack; just needs to ship to Nadia.
• Build-a-Bot facilitator network (CRM + train-the-trainer materials still to formalize).
• Flash Lab beyond Stanford — Tinkery, Lake Forest, Alexander Dawson (Lane Young, pending Christine), NewSchools (Vanessa pending).

Reach vehicles not yet in motion

• SXSWedu (Mar 2027), ASU+GSV (Apr 2027), Learning & the Brain, CUE — Josh’s bucket from Apr 16. Decide which to prepare for and which to skip.
• Funder conversations as reach (CZI, LEGO, OpenAI Academy, Anthropic education, Google for Ed, Microsoft Ed) — these are reach AND revenue, but the relationship work is reach-shaped.

What’s in your control vs. studio’s

• Yours: who you say yes to, what you build into Flash Lab as transferable IP, how aggressively you pursue ISTE multipliers (CLS faculty, district partnerships).
• Studio’s: headcount, how much capacity protects deep work vs. ad hoc requests, partnership agreement structures.
• Neither’s: whether ISTE leadership treats Stanford as a revenue partner vs. a brand partner. Whether faculty directors’ growing recognition (Schumann naming Studio as must-have) translates to budget conversations.

The honest tension The reach framing wants quantity (more districts, more facilitators, more partnerships). The robust framing wants quality (training that holds, materials that survive without us). They aren’t opposites but they compete for your time. That tension is itself the conversation.

The spear: tip vs staff

Reuben’s framing for the 1:1 — the studio’s reach is a spear. The tip is what we make. The staff is what carries it.

• Tip = Accelerator-Studio-created things. Sharp, branded, ours. Build-a-Bot, AI Flash Lab, the toolkit on designkit.stanford.edu.
• Staff = supporting other things that already have reach. Seed grantees, SAL convenings, ISTE’s network, partner platforms.
• A spear with no staff doesn’t reach. A spear with no tip doesn’t pierce. Both, doing different jobs.

Cross with internal vs external (where the reach lands) to see the field:

	Tip (AS-created)	Staff (carries others’ reach)
Internal (SAL / Stanford / AS)	• Build-a-Bot used inside Stanford (Cathy’s bots, Marily Health Coach, Wen mybook, Comic Studio for Ana) • Flash Lab on-campus (Tinkery, GSE) • SAL Summit prototypes / internal demos	• Supporting seed grantees one-on-one (Cyan, Camryn parsing, Belinda CRISPRkit, Forssell-Ramirez, King) • SAL convenings (Summit, Legal 101, AI Seed Grants info session) • 3-C’s, accelerator-studio model docs
External (K-12, districts, conferences, funders)	• ISTE Live Jul 1 session • Flash Lab at Lake Forest, Alexander Dawson (Lane Young pending), NewSchools (Vanessa pending) • bot101.app + designkit.stanford.edu as public products • Oman Hackathon (shipped)	• ISTE train-the-trainer (Build-a-Bot riding ISTE’s network) • DCI Celebration Flash Lab Jun 5 (Isabelle’s ask) • 100x Forum participation • Funder conversations (CZI, LEGO, OpenAI, Anthropic, Google, Microsoft Ed)

What the 2×2 surfaces:

1. Internal-Staff is the heaviest cell by volume of work. That’s the seed-grantee day-job. It’s also the cell with the least visible “branded” reach — it shows up as Stanford’s reach, not AS’s.
2. External-Tip is the cell with the most leverage per hour but the smallest count today. ISTE is the marquee bet to grow this cell.
3. External-Staff is the multiplier — every external-staff partnership (ISTE, NewSchools, DCI) lets a tip travel further.
4. Ongoing vs one-off runs orthogonally — most internal-staff is ongoing relationships; external-tip leans one-off (a session, a workshop). The question for Josh: which one-offs do we want to convert into ongoing?

The Reuben-specific question: which cell does your time disproportionately help, and which cell would be hardest to fill if you weren’t here? Josh’s “relationship writer” comment suggests Internal-Staff is where you’re load-bearing. But the studio’s growth story may need you spending more time in External-Tip.

Logistics & also-bring

• ISTE 150-word — Josh edited your revised version on Slack today, you confirmed his edits at 17:44 (“I like your edits … 136/150 words, so I think it looks good”). Final converged. Just need to send to Nadia — no further Josh signoff required.
• ISTE registration via Moraima — no early bird discount for presenters, so May 1 is not a real deadline. De-prioritize.
• Strategic Huddle (May 12, 2–3:30 PM with Cathy) — invite accepted. Note SofIA reassignment to Joe.
• Vibe-coded MVP support as a service — flagged for Strategic Huddle, but worth a 30-second mention here so Josh isn’t surprised when it lands on the agenda.
• CRM survey questions — Josh has been waiting since Mar 5. Either commit to a draft date or de-scope.

Open Qs to surface (if there’s room)

• Headcount — Josh mentioned “headcount growth may be coming.” What does the JD look like, and what’s the timeline you should plan around?
• The grantee response Josh dumped on Apr 21 with the anonymous “consultation from Cathy/Josh/Reuben” line — which grantee was it? (For Quoted Impact attribution.)
• Health Coach Bot IRB — still waiting on Marily/Caitlin. Update?