Prep: AI Learning Day — Planning Meeting

Planning meeting: Tue Jul 7, 2026 Event date: Tue Jul 28, 2026 Owners/facilitators: Josh, Isabelle, Marlene, Gregory, Reuben Reuben’s role: Co-lead (with Josh) the three Flash Lab segments — Mapping Opportunities → Form Teams, Spark Gallery, Team Build Sprint. Also floats to support teams during the build.

Framing

A hands-on team day: moving the Accelerator team from consumers of AI to designers and operators of it. Three aims:

1. Greater operational efficiency across the org
2. Less busywork, more satisfying work
3. Amplified impact of collective work

Working Agenda (as circulated)

Time	Activity	Lead
10:00–10:10	Buffer / arrive + mingle	—
10:10–10:25 (15m)	Welcome + Framing the Day	Josh, Isabelle, Marlene
10:25–10:35 (10m)	AI 101: “AI or Not?”	Gregory
10:35–10:50 (20m?)	Security & Data: the “Nutrition Label”	Josh + UIT
11:00–11:30 (30m)	Flash Lab Pt 1: Mapping Opportunities → Form Teams	Josh & Reuben
11:30–11:45 (15m)	Spark Gallery: What’s Possible	Josh & Reuben
11:45–12:45 (60m)	Lunch	—
12:45–1:25 (100m?)	Flash Lab: Team Build Sprint	Josh & Reuben (+Gregory float)
1:30–2:00 (100m?)	Showcase — every team demos	—
2:00–2:15 (15m)	Closing & Reflection: What Success Looks Like	Gregory & Marlene

⚠️ Things to raise at the planning meeting

1. The schedule doesn’t add up — the Build Sprint is the casualty.

• “Team Build Sprint” is labeled 100 min but the slot (12:45–1:25) is only 40 min.
• “Showcase” is also labeled 100 min but the slot (1:30–2:00) is only 30 min.
• Those two “100 min” labels look like copy-paste artifacts. The real question: how long is the actual build? 40 min is very tight for teams to go from problem statement → working prototype with agents/vibe-coding. If the intent was ~100 min of build, the back half of the day needs a rethink (day currently ends 2:15).

2. Minor timing nits.

• Security & Data (10:35–10:50) is 15 min but labeled 20.
• There’s an unaccounted 10:50–11:00 gap before Flash Lab Pt 1.

3. Showcase capacity. “Every team demos” in 30 min — need a per-team time box once team count is known (e.g. 6 teams = ~4 min each incl. transitions).

4. Reuben/Josh division of labor across the three co-led segments isn’t split yet — worth agreeing who drives what (esp. Spark Gallery, which pulls from real Studio builds — Reuben has the deepest catalog here).

Spark Gallery — build candidates to pull from (Reuben’s)

(fill in at planning meeting — spans robust prototypes → scrappy one-offs to show range)

• Quick-builds catalog: projects/quick-builds/

</content> </invoke>