Back to Daily Daily Prep: Thursday, May 14, 2026

Daily Prep: Thursday, May 14, 2026

Josh 1:1 day. The R/R/R + role-evolution email is still in Drafts — must decide before 10am whether to send first or open verbally. Lakshmi demo 1:30pm is the second big block. Light email/Slack day otherwise. Timecard due tomorrow.

ISTE Live 2026 — DECIDED (May 14, pre-1:1). Yes, doing it. Session title + description already submitted to ISTE. Awaiting next steps from Nadia. No longer a Josh-1:1 decision point — drops out of the agenda.

Open Threads from Yesterday

  • 🚨 R/R/R + role-evolution email NOT SENT. Drafted May 13 4:59pm in Apple Mail Drafts under subject “For tomorrow: the Reach/Robust/Resonance conversation, brought to its actual subject.” Decision before 10am: send now and let Josh skim, OR raise verbally without the doc, OR delay to a longer dedicated window. Recommendation: send the moment you’re up, so Josh has skim time before the 1:1.
  • Strategic Huddle (May 12) running-notes — never filed to meetings/running-notes.md. Decisions and follow-ups from that conversation aren’t captured yet. Worth a 15-min write-up before they slip.
  • Cyan DeVeaux — committed at the huddle to either “2 intros this week or formal pause.” Today is Thursday. Window narrowing.
  • CRISPRkit handoff — open question for Cathy from the huddle, not yet resolved.
  • Joe’s OOO dates — asked at the huddle, no answer yet captured.

Today’s Calendar

10:00–10:45 AM PT — Josh ↔ Reuben 1:1 🔴 (THE big slot)

With: Josh Weiss Zoom: stanford.zoom.us/j/94194351840 Prep doc (refreshed yesterday):

  • prep/2026-05-07-josh-1on1-reach-robust.md — Reach/Robust/Resonance with Strategic Huddle outcomes folded in

Note: goals/role-evolution-working-notes.md is personal thinking material only (JD draft, quarterly cadence, questions for me) — NOT shared with Josh. The shareable version is the May 14 email draft + the R/R/R prep doc above.

Two decisions to land:

  1. Resonance — keep, kill, or rename. The third leg is also the personal-role leg.
  2. Title timing path — (a) title update first, comp follows in cycle, or (b) earn the new scope first, both adjust together.

(ISTE Live 2026 was the third decision — now resolved. Decided yes, session submitted, awaiting Nadia.)

Discussion (not decisions):

  • Control-list pressure test
  • Cyan stall as a Robust signal — what’s the system fix?
  • Cost sheet feedback (sent Wed May 6, no read yet)

Filing: meetings/josh-1on1s.md with heading ## Josh 1:1 (May 14, 2026). Do NOT file in running-notes (1:1 with Josh goes in josh-1on1s).

🎯 Pre-1:1 Brief

Docs Josh has (via Slack link, sent this morning):

  • prep/2026-05-07-josh-1on1-reach-robust.md — R/R/R, your edited voice version
  • prep/2026-05-14-role-jd-and-quarterly-for-josh.md — Role Evolution, heavily trimmed to 3 R’s + 6 Key Capabilities. Note: you cut the explicit “What I want from your review” section, so the asks need to come up verbally.

Success in 45 minutes — three things to land:

  1. Josh’s pressure-test on the Robust / System Designer vector. It’s the part you have the least visible scaffolding for. If he says “the portfolio-lead piece is real, the System Designer extension is the bet” — you’ve named the truth together. Hard pushback here is the most valuable thing you’ll learn today.
  2. Josh’s read on a plausible title at Stanford grade. Get a direction, not a final answer. Even “Director-track is plausible, but not yet” is useful. You cut the title options from the doc, so bring them verbally if Josh doesn’t surface a name himself.
  3. Agreement on a next step. A small one. Don’t leave without a next action — (a) Josh advocates internally before next 1:1, (b) you draft a tighter scope doc by [date], or (c) you and Josh book a longer dedicated slot.

Anchor moves (phrases to use):

  • If Josh drifts to comp: “I’m not asking for a comp answer today. I’m asking for the path.”
  • If Josh hedges on advocacy: “You shouldn’t have to make the case for me. I want to make it with you.”
  • If Josh questions the seed-grant framing: “The portfolio is the substrate. The formats grew out of that work, not separately.”
  • If Josh challenges the Robust vector: agree fast. “That’s exactly the part I want pressure on. What would make it real?”
  • If it gets transactional: “Comp is the trailing indicator, not the goal.”

Anticipated pushback + your move:

What Josh might say What it means Your move
“Let’s see how ISTE goes first.” He wants proof points before going upstream. Agree. Make ISTE the Q1 anchor. Ask what other proof points he’d want.
“Resonance is the squishy one.” Same gut you have. “I agree. It’s the bet. What would make it real for you?”
“Title change is hard at Stanford.” True. Not a no. “I’d rather know the realistic path than push for the wrong move.”
“We need to talk to Isabelle.” Sponsor activation. “Great. When? What’s the framing you want me in?”
“What about Joe?” Org-chart question. Listen. “That’s worth us thinking about together.” No clean answer needed.
“This is great, let’s keep talking.” Polite deflection. Push for a next step. “What’s the most useful next-step from here?”

Listen-fors:

  • Anything about Isabelle’s view of the Studio’s direction (sponsor signal)
  • Hints about Stanford’s grade structure (even loose language helps)
  • A new responsibility he wants you to take on (he’s bidding scope up)
  • A responsibility he wants to remove (tells you what he sees as misaligned)
  • Stories of others re-leveled at SAL or peer schools (pattern data)

Things NOT to do:

  • Don’t read from the doc. He has it. Treat it as shared backdrop.
  • Don’t relitigate ISTE — decided, status update only.
  • Don’t bring personal-notes content (questions for yourself, “what changes if I get a no”).
  • Don’t oversell Resonance. Your honest caveat (you cut it from the doc but it’s still true) is your asset; surface it verbally.

Regular check-in items to fit in briefly:

  • ISTE Live → “Decided yes, session submitted to Nadia, awaiting next steps.” Move on.
  • Cyan DeVeaux → your call on commit-2-intros vs. formal-pause (huddle commitment from Tue).
  • CRISPRkit handoff → confirm Cathy’s read, close the huddle question.
  • Joe’s OOO dates → still open.
  • Cost sheet → sent May 6, no feedback. Mention if space.

Rough time allocation:

  • 2 min: regular check-in (ISTE, Cyan, CRISPRkit)
  • 25-30 min: the role conversation. Hand the floor to Josh. Don’t fill silences.
  • 5 min: next steps. Don’t leave without one.
  • 5-8 min: buffer / spillover.

Right before you start:

The two asks you cut from the doc but need to land verbally:

  1. “Where am I overclaiming? Especially the Robust / System Designer piece.”
  2. “Is the title plausible at Stanford grade — and which version would you advocate for?”

If you walk out with answers to those two, you’ve won the meeting.

🃏 Wild card: the Technical Project Manager hire

What you know (as of Tue May 12): the new hire’s title will be Technical Project Manager.

Why this matters for today’s conversation: the TPM hire is the single biggest factor in whether the Robust / System Designer vector is real or aspirational. Your honest caveat in the original doc was that System Designer (the multiplier piece) was the part you had the least visible scaffolding for. The TPM hire IS the scaffolding — if you scope it right.

But it cuts both ways:

  • Best case: TPM owns project-management execution across the seed-grant portfolio and format delivery. Reports dotted-line (or solid-line) to your evolved role. You become the strategic / design / external person; they become the operational person. Robust vector goes from aspirational to live.
  • Worst case: TPM is brought in as a peer who project-manages your work without you having authority over it. Your scope shrinks. The Studio buys execution capacity but doesn’t elevate the role above it. Title conversation gets harder, not easier, because “we just added capacity, let’s see how it lands.”

The frame to bring: treat this as a joint scoping conversation, not two separate decisions. Your role and the TPM’s role need to fit together. If Josh scopes the TPM first and then your role evolution second, you lose leverage. If you scope them together, the architecture is clean.

Open questions to get answers on today:

  1. What’s the scope of the TPM role as Josh is imagining it? Listen for: does it overlap with what you do today, or does it free you to do bigger work?
  2. Who does the TPM report to? Josh directly? You? Dotted line? This is the org-chart signal.
  3. What’s the timing? Is the JD posted? Are they interviewing? If pre-posting, you have leverage to shape the scope.
  4. What level / grade is the TPM? Tells you a lot about how it positions relative to your evolved role.

Anchor moves:

  • Lead with curiosity, not threat: “Tell me more about the TPM role — what’s the scope you’re imagining?”
  • When Josh answers, listen for whether the scope frees you or compresses you. Don’t react yet.
  • Then bridge to your role: “That actually unlocks the Robust vector. System Designer mode needs a person to scaffold to, and now there’s going to be one. How do you see my role fitting around theirs?”
  • If the TPM scope sounds like it overlaps yours: “Help me think through where the boundary is. What’s mine to keep, what’s theirs to own?”
  • If Josh hesitates on your title conversation because of the new hire: “I’d rather scope these together than sequentially. The TPM role and mine define each other.”

Risks to watch:

  • Josh frames TPM as “your project manager” without authority. Worst case. Push back gently: “That works if the reporting line is clear. What are you imagining there?”
  • Josh delays your role conversation because of the hire. “Let’s see how the TPM lands first.” Counter: “The TPM’s scope and mine are easier to land together than apart. If I’m a Director above them, the JD writes itself differently than if we’re peers.”
  • TPM scope includes format stewardship or seed-grant portfolio decisions. That’s your core scope. Hold the line: “Those are my responsibilities. The TPM should be operating in service of that work, not deciding it.”

The strategic gift: Your “honest caveat” about System Designer being the bet vector? The TPM hire turns that bet into a live test. By Aug 2027 you’ll know whether you can operate as a multiplier through this person. That makes the Robust vector defensible upstream.

One sentence to deliver if there’s a clean opening: “The TPM hire is the proof of concept for the Robust vector. If I can operate as a multiplier through them, the System Designer mode is real, and the JD I sent you stops being aspirational.”

1:30–2:30 PM PT — AI Flash Lab + Build-a-Bot demo for Lakshmi 🔴

With: Lakshmi Balasubramanian (Chris Lemons lab) Zoom: stanford.zoom.us/j/94883898830 Context: Josh-introduced. First demo with her — she’s looking at AI literacy resources for Lemons lab’s K-12 work. Walkthrough of both Flash Lab and Build-a-Bot. No people profile exists yet — worth creating people/lakshmi-balasubramanian.md after the demo. (Light prep per the no-pre-read-for-sales rule; this is a discovery/scoping call.) Filing: meetings/running-notes.md with heading ## Lakshmi Balasubramanian demo (May 14, 2026).

NeoLens 5pm — NOT on calendar today

Yesterday’s look-ahead said “NeoLens 5pm” Thursday. The actual recurring NeoLens slot is Tuesdays at 12pm and Wednesdays at 5pm — not Thursday. Yesterday’s prep was likely wrong about this. Treat the Thursday evening as open.

Optional / FYI

  • 4–5pm — Learning Impact Exchange (Joe + Sarahí, Longview Raikes 4th floor). Joe posted to #general May 12. You’re not on the invite list explicitly. Could drop in for the seed-grant networking value. Skip if you need recovery time after the 1:1 + demo.

Calendar Reconciliation

Yesterday’s look-ahead said today would have: Josh 1:1 10am ✅, Lakshmi demo 1:30pm ✅, NeoLens 5pm ❌.

Discrepancy: NeoLens 5pm appeared in yesterday’s prep but is not on any calendar today. The actual NeoLens cadence is Tue 12pm + Wed 5pm. Not a missed meeting — yesterday’s entry was wrong. Noting it so the pattern doesn’t repeat.

Email Action Items

Needs Action

  • Reminder: Axess Timecard Due Tomorrow (Stanford do-not-reply, May 14 6:22am) — submit before EOD Friday. See cadence below.

FYI Only

  • BTS comes to Stanford campus this weekend (Stanford Report) — newsletter. Skip.

Inbox is unusually light — only 2 emails since yesterday’s prep. Carryover from yesterday (Nadia, Jaylen, Angel Velasquez, Loren Pamo, Joe Sherman Airtable adds) still owed if not handled.

Slack Catch-Up

Scanned 126 channels, 12 with unreads. Highlights:

  • Jessica Tsang DM (May 13 7:59pm): “the airport people definitely felt suspicious” — appears to be a casual exchange continuation. No action needed unless context says otherwise.
  • #general — Joe Sherman (May 12): Learning Impact Exchange Thu May 14, 4–5pm, Longview Raikes. RSVP form linked. Drop-in optional.
  • #general — Various: PhD summer projects Brazil grant call (May 22 deadline, not your target audience); Educational Opportunity Projects newsletter (Rachel Reis).

Nothing urgent. No DMs from Josh / Joe / Isabelle / Cathy / Christine / Marily / Jessica (ISTE) requiring a response. No @mentions flagged.

Reminders

Overdue

  • (none on Apple Reminders for today)

Due Today

  • (none with due dates set)

Aspirational / no due date (in Claude-ToDo, mobile capture)

  • githubworkspace/cli — research for executive assistant integration
  • Personal-life assistant bot scoping (off-work-laptop)
  • SQLite musings (already partially actioned — ETL is built)
  • Amazon Business charge check
  • 2 X.com link reads

These are old aspirational items. Worth a 15-min triage this week — most can be deleted or pushed to a “someday” file.

Personal (Claude list)

  • Chris at Ascendant Aviation re: tax questions (carried Feb 13)
  • Echinacea
  • 3 article reads (personal-laptop tonight)

From Inbox Processing

INBOX.md is empty. Nothing to route.

Cadence Checks

  • 🔴 Timecard: Stanford reminder confirms — due tomorrow (May 15). Submit before EOD Friday via Axess.
  • End-of-month Airtable: Last week of May still ~2 weeks out. No nudge yet.
  • Strategic Horizon: Still overdue from April. Mentioned yesterday. Worth a 30-min push this week if the Josh conversation lands clean.
  • Travel — DCI June 5: ~3 weeks out. If Egencia booking hasn’t happened, do it this week. Carryover from yesterday.
  • Meeting prep needed (next 3-5 days):
    • Mon May 18, 9am — 100x AI Roadmap Update with Marion Shields, Lloyd Reeb, Pete Chambers (personal/gmail calendar). Pre-read worth pulling Sunday evening if you have history of the prior roadmap.
    • Tue May 19, 8:30am — TMT & Reuben call (Leopold, tmteaching.co.za). Unknown context — check email thread or origin.
    • Wed May 20, 10am — GSE May All-Staff (Dan Schwartz farewell). Optional postcard contribution by Mon May 18.
  • qmd re-index: Run after daily file generation.

Today’s Priorities (Top 5)

  1. 🚨 Send the R/R/R / role-evolution email to Josh before 10am 1:1 (or decide to raise verbally instead). Currently sitting in Apple Mail Drafts. Also: update the email to remove ISTE as decision #1 — it’s already decided.
  2. 🔴 Josh 1:1 10am — two decisions to land (Resonance keep/kill/rename, title-timing path). ISTE is now a status update, not a decision.
  3. 🔴 Lakshmi demo 1:30pm — Flash Lab + Build-a-Bot walkthrough. Create people/lakshmi-balasubramanian.md after.
  4. File the Strategic Huddle (May 12) meeting note — decisions and asks from that conversation aren’t captured yet.
  5. Cyan DeVeaux — commit to 2 intros today, or formally pause the chain (per huddle commitment).

Stretch: Submit timecard (deadline tomorrow). Egencia/STAP receipts. Drop in at Learning Impact Exchange 4pm if energy holds.

Full task queue: see action-items.md — many open carryover items (anniversary emails, Anthony Pollina, Vanessa Monterosa, mybook audit, Quoted Impact Airtable, Strategic Horizon, Chinese BaB, etc.).

This Week + Next Look-Ahead

Day Date Events
Thu May 14 Josh 1:1 10am, Lakshmi demo 1:30pm, optional Learning Impact Exchange 4pm
Fri May 15 Weekly Personal Review 2pm, timecard deadline EOD
Sat-Sun May 16-17 River Church Sun
Mon May 18 100x AI Roadmap Update 9am, GSE all-staff postcard contribution due
Tue May 19 Ardent hold 8am, TMT/Leopold 8:30am, AS:DE 11am, NeoLens 12pm, Outpouring 10:30am, Josh 1:1 (Mon variant — was the Mon slot)? Check.
Wed May 20 Chiropractor 8am, GSE All-Staff 10am (Dan farewell), NeoLens 5pm, CAP check-in 6pm

Session Notes

Josh 1:1 (10am-10:45am) — major reframe

  • The meeting pivoted. Title/comp did not come up. Neither did the TPM hire. Both still open threads.
  • Josh met Reuben in the “feel a little lost” place and reframed the entire conversation around GPS narrative scaffolding for the next year, using R/R/R as the guiding grammar.
  • Language shift: Josh prefers Robustness (full word), not “Robust.” Resonance is sharpening toward “agency” + persistence at multiple levels (skills, agency, connection).
  • Two-doc deliverable: retrospective GPS narrative + forward-looking plan. Reuben drafts retrospective by mid next week. Josh sends sacrificial first draft by mid next week. Tight iteration cadence.
  • Voice: first-person, reflective journaling. Lots of “I.” STAR-style prompts.
  • Goal categories for the forward plan: Technical, Communication, Wellness, Time/PM. Meshed, not siloed.
  • Full notes filed in meetings/josh-1on1s.md (May 14, 2026 entry).
  • Decisions logged in decisions.md (R/R/R framework adoption + two-doc structure).
  • Action items in action-items.md (drafting deadlines, Christine’s slides, etc.). Fizzy cards #109-112 created.

What didn’t happen (worth noting)

  • Title conversation deferred. Reuben’s role-evolution doc became raw material for the framework conversation, not the centerpiece.
  • TPM hire not raised. Surface in a future 1:1 once the GPS narrative is in flight.
  • Cost sheet feedback not raised. Still owed by Josh from May 6.

Strategic read

  • The vulnerability in the Slack message worked. Josh responded with scaffolding, not pushback.
  • The R/R/R framework is now shared infrastructure — durable across whatever happens with title/comp later.
  • The deferred title conversation is not a loss. It’s a postponement to a more grounded moment.

Generated: 2026-05-14 morning. Daily file uses the lean format (top-5 only, references action-items.md for the full queue). R/R/R email in Drafts is the #1 surface — decide before 10am.

Source: daily/2026-05-14.md