s10-B1-1 pb-cover M1 → M2 → M3
Three groups · three demos · seven sessions and a build break behind them.
Showcase — three demos, leadership Q&A, credentials
s10 · Betterworks · 60m · Full Cohort + Senior Leadership ·
draft
s10 → 5 blocks, 16 slides, 7 trainer notes, 8 exercises, 1 reflects, 0 quizzes, 0 asides
Pre-read
Tonight has no pre-read. The work happened in the seven sessions and the build break. Today is the demo.
A two-paragraph one-pager from PG describing what the cohort committed to, what each group's PRD landed on, and what "M1 / M2 / M3" mean. Distributed via cohort sponsor 24 hr before. [?CONFIRM PG drafts this Thu evening.]
A two-paragraph one-pager from PG describing what the cohort committed to, what each group's PRD landed on, and what "M1 / M2 / M3" mean. Distributed via cohort sponsor 24 hr before. [?CONFIRM PG drafts this Thu evening.]
Session goal
By end-of-session:
1. **Three working demos** delivered to senior leadership — M1 chain, M2 prototype, M3 wired to live data
2. **Leadership has asked the questions they wanted to ask** — Q&A is part of the format, not bolted on
3. **Twelve practitioners credentialed live** — each named, each receiving the credential link in the room
4. **The practice's promise lands as evidence** — the cohort has built what the program said they would
1. **Three working demos** delivered to senior leadership — M1 chain, M2 prototype, M3 wired to live data
2. **Leadership has asked the questions they wanted to ask** — Q&A is part of the format, not bolted on
3. **Twelve practitioners credentialed live** — each named, each receiving the credential link in the room
4. **The practice's promise lands as evidence** — the cohort has built what the program said they would
PG opens · the practice's promise · the build break as accelerant
4 itemsCold open. Land the frame, then get out of the way. The cohort is the show.
s10-B1-2 statement What you'll see today
Three demos. Each runs the chain: backlog intelligence · design system in Claude · prototype reading live data. No mock data. No hand-waving
Group A · M1 → M2 → M3 demo + leadership Q&A
8 items7-min demo · 5-min leadership Q&A · 3 min transition. Same shape for B / C.
s10-B2-1 pb-section [?CONFIRM Group A demo title]
s10-B2-2 activation Group A walks the chain
PRD · M1 live · M2 walk · M3 wired demo · close with the break narrative woven through.
s10-B2-3 activation Q&A · Group A
Leadership asks · cohort answers · 5 min · the demo team owns the mic.
Group B · M1 → M2 → M3 demo + leadership Q&A
7 itemsSame shape. Same lenses. Different group.
s10-B3-1 pb-section [?CONFIRM Group B demo title]
s10-B3-2 activation Group B walks the chain
PRD · M1 live · M2 walk · M3 wired demo · close with the break narrative woven through.
s10-B3-3 activation Q&A · Group B
Leadership asks · cohort answers · 5 min.
Group C · M1 → M2 → M3 demo + leadership Q&A
7 itemsFinal demo. Same shape. End the block by transitioning to credentialing.
s10-B4-1 pb-section [?CONFIRM Group C demo title]
s10-B4-2 activation Group C walks the chain
PRD · M1 live · M2 walk · M3 wired demo · close with the break narrative woven through.
s10-B4-3 activation Q&A · Group C
Leadership asks · cohort answers · 5 min.
Cohort reflection · credential ceremony · close
11 itemsThe closing arc. One cohort reflection beat · PG names each practitioner · credential link delivered live · leadership closes.
s10-B5-1 statement One thing the cohort wants to say
Before the credentials — one practitioner per group · 30 seconds each · what they're taking back to BW that they didn't have seven sessions
s10-B5-2 activation Three cohort reflections · 30 sec each
One per group · what changed · what you're doing Monday.
s10-B5-3 statement The AI-Native Practitioner credential
Awarded to every cohort member who shipped: a PRD · a working prototype · a reflection trail across all sessions. Twelve practitioners crede
s10-B5-4 activation Naming · credentialing · twelve practitioners
PG names each · credential link delivered live · in cohort-roster order.
s10-B5-5 pb-thankyou (no title)
After this session
- **Credentials delivered** — every practitioner has the credential link in their inbox
- **One-pager retrospective** — PG drafts a 1-page summary of the showcase for the BW sponsor within 48 hr (what the cohort built, what leadership asked, where the practice could compound at BW)
- **Cohort chat stays open** — for 30 days post-showcase · for follow-up questions, reuse moments, and PG to land the alumni-channel offer
- **LinkedIn nudge** — PG asks each practitioner Sunday: *"if it lands for you, post your credential — tag the cohort and the program"*
- **Failure-mode recovery (trainer-side):**
- **A demo's live data read fails** during the showcase → demo team narrates from the backup screenshots without breaking flow · names the failure honestly · *"the wire works at home; we'll show you the cached version" *
- **Leadership Q&A goes silent** after a demo → PG curates: *"I'm curious about [specific thing from the demo] — can you walk us through it?"*
- **A demo runs over 7:00** → soft-stop at 7:30 (not 7:00) on the day · the room won't notice 30 sec but will feel an aggressive cut
- **Credential email doesn't send live** for a name → PG continues the ceremony · sends the link manually within 1 hr · acknowledges *"yours will land in your inbox by [time]"*
---
## Open items (for polish pass / PG review)
1. **Leadership audience size + names** — `[?CONFIRM]` placeholder. Affects room layout, Q&A facilitation, the one-pager retrospective.
2. **Group demo titles + 1-line PRD summaries** — `[?CONFIRM]` × 3 in B2/B3/B4 section slides. Filled from the locked PRDs in the S07 gdoc.
3. **Showcase order (A → B → C)** — alphabetical default. PG's call whether to lead with strongest, close with strongest, or alphabetical.
4. **Three cohort reflection speakers** — one per group, nominated by group Thu evening. PG confirms in cohort chat Fri morning.
5. **Credential page live-render trigger** — confirm /certificate/ page renders called name + sends link on PG action. Pre-flight Thu evening.
6. **Backup screenshots** — every group prepares a PDF of their wired demo as fallback (S09 close already names this). Verify in cohort chat Fri morning.
7. **Activation count** — 8 activations across B1–B5 (3× demos · 3× Q&As · cohort reflection · credential ceremony) · 2 surfaces (screen-share · audio). Exceeds §17 floor for 60 min.
8. **§31 compliance** — verified no cohort-facing slide carries a timing string (all pacing in trainer notes + frontmatter).
9. **§32 brand naming** — verified Lab/programme used; "AI-Native Practitioner" credential phrasing matches brand.ts levels[0].
10. **One-pager retrospective for sponsor** — PG drafts Thu evening; covers what was built, what leadership asked, BW-specific compounding opportunities. Distributed Sun.
- **One-pager retrospective** — PG drafts a 1-page summary of the showcase for the BW sponsor within 48 hr (what the cohort built, what leadership asked, where the practice could compound at BW)
- **Cohort chat stays open** — for 30 days post-showcase · for follow-up questions, reuse moments, and PG to land the alumni-channel offer
- **LinkedIn nudge** — PG asks each practitioner Sunday: *"if it lands for you, post your credential — tag the cohort and the program"*
- **Failure-mode recovery (trainer-side):**
- **A demo's live data read fails** during the showcase → demo team narrates from the backup screenshots without breaking flow · names the failure honestly · *"the wire works at home; we'll show you the cached version" *
- **Leadership Q&A goes silent** after a demo → PG curates: *"I'm curious about [specific thing from the demo] — can you walk us through it?"*
- **A demo runs over 7:00** → soft-stop at 7:30 (not 7:00) on the day · the room won't notice 30 sec but will feel an aggressive cut
- **Credential email doesn't send live** for a name → PG continues the ceremony · sends the link manually within 1 hr · acknowledges *"yours will land in your inbox by [time]"*
---
## Open items (for polish pass / PG review)
1. **Leadership audience size + names** — `[?CONFIRM]` placeholder. Affects room layout, Q&A facilitation, the one-pager retrospective.
2. **Group demo titles + 1-line PRD summaries** — `[?CONFIRM]` × 3 in B2/B3/B4 section slides. Filled from the locked PRDs in the S07 gdoc.
3. **Showcase order (A → B → C)** — alphabetical default. PG's call whether to lead with strongest, close with strongest, or alphabetical.
4. **Three cohort reflection speakers** — one per group, nominated by group Thu evening. PG confirms in cohort chat Fri morning.
5. **Credential page live-render trigger** — confirm /certificate/ page renders called name + sends link on PG action. Pre-flight Thu evening.
6. **Backup screenshots** — every group prepares a PDF of their wired demo as fallback (S09 close already names this). Verify in cohort chat Fri morning.
7. **Activation count** — 8 activations across B1–B5 (3× demos · 3× Q&As · cohort reflection · credential ceremony) · 2 surfaces (screen-share · audio). Exceeds §17 floor for 60 min.
8. **§31 compliance** — verified no cohort-facing slide carries a timing string (all pacing in trainer notes + frontmatter).
9. **§32 brand naming** — verified Lab/programme used; "AI-Native Practitioner" credential phrasing matches brand.ts levels[0].
10. **One-pager retrospective for sponsor** — PG drafts Thu evening; covers what was built, what leadership asked, BW-specific compounding opportunities. Distributed Sun.
Add ?token=… to the URL.