- Your group's **M2 prototype** open in Figma Make · the one screen you'll wire - Your group's **data source ready** — sheet populated with real rows · or API endpoint with sandbox creds · or fixture JSON committed - The **locked PRD** from S07 with the wiring tier confirmed in S08 - A blank claude.ai chat ready · your group's Design Project loaded with the prototype context
No essays. Show up with the data source live and the prototype open.
Session goal
By end-of-session:
1. **Every group has wired one screen** to their committed tier — sheet · API · or fixture 2. **Every group has run two dry-runs** of the 7-min showcase narrative 3. **The showcase shape is locked** — same 7 min, same beats, same close — across all three groups 4. **Friday's logistics are committed** — room, AV, time, leadership names, dress, the order
B100–10
From S08 hot-seat to tonight's wire-up
6 items
Cold open. The hot-seat told us what's weak. Tonight is the last build before the showcase.
▤ Slide · s9-B1-1pb-coverB1L23
Read live data · rehearse the demo
Three groups · three wired prototypes · two rehearsals before Friday.
▤ Slide · s9-B1-2statementB1L30
M3 is the wire
M2 is your prototype. M3 is your prototype reading from a source your audience trusts. Not a backend. Not a database project. One screen. On
▤ Slide · s9-B1-3activationB1L44
Before we start — one S08 change
What's the single biggest fix your group made between last night and tonight?
B210–35
Worked example · Sheet-backed wiring · pattern lock
9 items
The core teach. PG walks one Sheet-backed wiring end-to-end — concept, demo, the pattern. Cohort watches first, builds in B3.
▤ Slide · s9-B2-1pb-sectionB2L59
The wiring pattern · one worked example
▤ Slide · s9-B2-2listB2L65
Wiring is three things
Not engineering. Just three small pieces. Compose them.
A source — a Google Sheet you own · or a public/internal API endpoint · or a fixture file
A read — one function call that fetches what your screen needs · returns JSON
A render — your prototype's mock data swaps for the live read · the screen updates when the source updates
▤ Slide · s9-B2-3codeB2L79
The Sheets-as-backend pattern
▤ Slide · s9-B2-4activationB2L104
PG demos the wire-up · live
One sheet · one Figma Make screen · one read · the screen updates when the sheet does.
B335–60
Group build · wire one screen to your tier
7 items
Each group wires one screen to their committed tier. PG floats. Cohort builds in parallel.
▤ Slide · s9-B3-1pb-sectionB3L133
Wire one screen · your tier · your data
▤ Slide · s9-B3-2listB3L139
What each group ships in this block
One screen reading live data. That's the bar.
The screen — pick the one that most needs to feel real for the showcase
- **Three wired prototypes** — one screen per group reads live data · source verified - **Three timed 7-min walks** rehearsed twice · opens and closes sharpened - **Showcase logistics committed** — room, AV, order, audience, what to bring - **Last-mile fixes** — anything that surfaced in round 1 + 2 feedback goes into a group fix list · sharpen Thu evening - **For S10 (Fri 17 Jul):** show up 30 min early · set up laptop + data source · backup screenshots ready · the PRD pinned - **Failure-mode recovery (trainer-side):** - **A T1 group hits auth wall in B3** → drop to T3 fixture without ceremony · the demo still reads as live for 7 min - **A sheet doesn't render in B3** → check share settings (public link viewable); if that's not it, check the range string - **Round 1 runs long** → keep round 2 as bookends-only (don't extend); the polish is in the open + close - **A group can't sharpen their close** in round 2 → PG drafts the closing line for them on the spot · they read it back · move on - **Logistics gaps in B5** ([?CONFIRM]s unresolved at delivery) → PG names what's known and commits to confirming the rest in cohort chat Wed
---
## Open items (for polish pass / PG review)
1. **S09 reflection URL** — `[?CONFIRM]` placeholder in B1 activation. Cohort home banner; verify Mon morning. 2. **Demo sheet** — PG creates a populated 5-row mock-BW-goals sheet for the B2 worked example by Sunday. Public-link viewable. Sheet ID into the code slide. 3. **Demo Figma Make prototype** — PG builds the "today's goals" screen Saturday for the B2 worked example. Pre-flight the wire-up end-to-end before the session. 4. **Activation count** — 5 activations across B1–B5 (reflection · PG demo · group wire-up · dry-run round 1 · dry-run round 2) · 2 surfaces (link · screen-share). Passes §17 floor for 90 min. 5. **§31 compliance** — verified no cohort-facing timing on slide headlines/subheads/footnotes (timer ranges live in trainer notes + frontmatter agenda). 6. **§32 brand naming** — verified Lab/programme used; no Bootcamp references. 7. **Round 1 vs Round 2 split** — round 1 is full 7-min walks (~25 min for 3 groups), round 2 is 2-min bookends per group (~6 min total). Adjust if PG wants round 2 to also be full walks (would push showcase logistics out of B5). 8. **Showcase order** — current draft is A → B → C alphabetical. PG may want to order by demo strength (strongest last, or strongest first to set tone). Decide before Friday.
Add ?token=… to the URL.
This site uses cookies to measure how content performs and to improve your experience.
No cookies are set until you choose.
Privacy policy
Cookie preferences
Choose which cookies you allow. Your choices are saved for one year.
You can change them anytime via the "Cookie settings" link in the footer.
Necessary
Always on
Required for the site to function. Includes your consent choice and security features like Cloudflare Turnstile. Cannot be disabled.
Analytics
Helps us understand how visitors use the site — which pages are popular, how you arrived, and where you drop off. Data is aggregated and anonymous.
Used by services like Google Analytics and Microsoft Clarity.
Marketing
Used to measure ad campaign effectiveness and show relevant content across platforms.
Used by services like Google Ads and Microsoft Advertising (UET).