Week 4 Instructor Cheat Sheet

A two-page printable reference card for the Course 4 Advanced Workshop deck — designed to sit next to the deck during the four-hour Teams session, so you never have to scrub back through 38 slides for a chat-paste block, the Debug Clinic script, or the next pair-rotation cue.

Print: Ctrl+P → Layout Portrait, Margins Default, Background graphics on. Two US-Letter pages. Site chrome and this preview note are hidden in print.

Use: page 1 is the live-delivery card — pacing strip, the Frontier silent timer, the Readiness Dashboard spec, the Debug Clinic three-student rotation, and the chat-paste cues for Slides 10 / 28 / 35. Page 2 is the anchor phrases, the recovery cues, and the Capstone-gate homework you must issue before logoff.

Download PDF Pre-rendered Letter-portrait two-pager — convenient for email or shared printers.
4Course 4 · Advanced Workshop
Instructor cheat sheet

Advanced Workshop

Frontier mapping, complex build (Readiness Dashboard), Debug Clinic, SOP QA drill, paired teach-back, workflow playbook. Coach the re-prompt — never type the fix.

4 hr · 6 modules
38 slides · 1 break · 3 chat-paste blocks
Companion to week-4-advanced.html + week-4-handouts.html
0:00M1 Frontier
0:30M2 Readiness Build
1:30Break 10′
1:40M3 Debug Clinic
2:20M4 SOP QA
2:50M5 Teach-Back
3:20M6 Playbook
130 min
Frontier Mapping 0:00–0:30 Silent + share
  1. Slide 10 chat-paste: drop the frontier-map starter from the Week 4 hand-out pack. Set silent timer 15 min.
  2. Brief (read verbatim): “Four columns: Category, Inside the frontier, Outside the frontier, Moving. Fifteen minutes silent. Use the starter from the hand-out pack. Then we share — one row per builder.”
  3. Share (15 min): one row per builder. Re-anchor when restrictions surface: “Map the world as it is, not as you wish it. Restrictions go in Outside.”
Outcome · map Unit Frontier Map seeded One row per builder logged; restriction list captured separately for the program lead.
260 min
Complex Build — Readiness Dashboard 0:30–1:30 Build · decompose first
  1. Hand-off (0:30): Deck → Power Platform. Pin the Readiness Dashboard spec slide in a side tab.
  2. Spec (read verbatim): “A single Power Apps screen that pulls Training (Excel), Equipment (CSV), and Alpha Roster. Show readiness % per Marine, with a drill-down. Decompose first — on paper — for ten minutes before you touch AI.”
  3. 10-min decompose on paper, no AI. Then 50 min build.
  4. Coach in chat. If anyone tries to skip decomposition, stop them: “Show me your fields and actions on paper. We will not unblock you until that exists.”
Deliverable · complex build Readiness % rendered per Marine Three sources joined behind one screen; decomposition page on paper for every builder.
BRK10 min
Break. Be back at H+1:40. Pre-flight: pick the three Debug Clinic candidates from chat (or pull the bug-bank fall-back); have the first volunteer’s screen-share authorized. 1:30–1:40
340 min
Debug Clinic 1:40–2:20 Coach · fishbowl
  1. Hand-off (1:40): switch from your screen to a student’s screen-share. You coach, you do not type.
  2. Brief (read verbatim): “Three students, ten minutes each. Share your screen, show your bug, walk us through your prompt history. The room diagnoses. The original builder retypes the fix — nobody else touches the keyboard.”
  3. Refuse the keyboard. “If I type it, you don’t learn it. Re-prompt with these three changes.” Walk away.
  4. Fall-back: if no volunteers, project a real Week-3 chat error from the bug bank and run it as a fishbowl.
Outcome · coaching habit Three live recoveries on the wall Each builder demonstrates re-prompt, not rescue. The room sees coaching modeled three times.
430 min
SOP QA Drill (Verification) 2:20–2:50 Pairs · 7-min rotations
  1. Slide 28 chat-paste: drop the SOP QA drill block from the hand-out pack. Pairs work in breakouts.
  2. Brief (read verbatim): “Take the AI-drafted SOP from the hand-out pack. Find the three confident hallucinations. Pairs, seven-minute rotations. We score as a room at the end.”
  3. Rotate every 7 min; reconvene at 2:47 for the room scoring.
Outcome · verification 3 hallucinations caught & named Verification habit (Week 1 Red Pen Review) re-applied to a builder’s real artefact, under time pressure.
530 min
Teach-Back 2:50–3:20 Pairs · 8-min teach + retell
  1. Reveal pairs drafted before the session (mix experience levels).
  2. Brief (read verbatim): “In your assigned pair, you have eight minutes to teach the other person one technique you mastered this course. They will repeat it back. If they cannot, you have not taught it yet.”
  3. Force a deliverable if pairs go silent: “In ten minutes I want one slide each — the technique, when to use it, when not to.”
Outcome · transferred skill Each builder taught one technique Required deliverable: one technique re-told back. The teach-back is the test of mastery.
630 min
Workflow Playbook 3:20–3:50 Hand-off doc
  1. Slide 35 chat-paste: drop the Workflow Playbook blank template from the hand-out pack.
  2. Brief (read verbatim): “Pick one of your own tools. Fill the playbook template: trigger, inputs, steps, verification, fallback, owner. This becomes your unit’s hand-off doc.”
  3. Issue the homework live (final 5 min): submit the playbook to the unit shared library by EOW. No exceptions.
Deliverable · institutional One playbook per builder First entry in the unit’s playbook library. Capstone-gate proposal also due in 7 days.
EDD · Week 4 cheat sheet · page 1 of 2 · pacing, prompts, deliverables Print landscape off · portrait, default margins, background graphics on
4Course 4 · Advanced Workshop
Cheat sheet · page 2

Anchors, recovery, homework

The phrases you repeat all afternoon, the failure modes to watch for at every chat-paste cue, and the homework that gates Week 6 (Capstone) attendance.

Use during: M3 Debug Clinic
Use during: any frontier-map drift
Companion to week-4-advanced.html

Pre-flight & hand-off cuesDone 48 h before; verified at T-30 min · chat-paste blocks staged for Slides 10, 28, 35

  • Gate-check the roster. Every attendee has a deployed-tool URL on file (collected at Week 3). Pull anyone without one to a 1:1 catch-up — do not let them sit through M2.
  • Tabs & portals. Deck (Week 4), this cheat sheet, the Week 4 hand-out pack (frontier-map starter, SOP QA drill, playbook template), GenAI.mil, Power Apps + Power Automate.
  • Sample data for M2. An Excel Training file, a CSV Equipment export, and an Alpha Roster snippet pre-staged in a OneDrive folder linkable from chat.
  • Bug bank. Keep three real prompt-failures from Week-3 chat ready for M3 if no one volunteers.
  • Teach-back pairs drafted from the roster (mix experience levels). Reveal at the start of M5.
  • 0:00 · Slide 10. Drop the frontier-map starter from the hand-out pack into chat. Silent timer 15 min.
  • 0:30. Deck → Power Platform. Pin the Readiness Dashboard spec slide in a side tab.
  • 1:40 · Debug Clinic. Switch from your screen to a student’s screen-share.
  • 2:50 · Slide 28. Drop the SOP QA drill chat-paste block. Pairs in breakouts; rotate every 7 min.
  • 3:20 · Slide 35. Drop the Workflow Playbook blank template. Each builder fills one for one of their tools.

Anchor phrasesPlant in M1; cite by name when you need them

  • 1. “Coach the re-prompt. Never type the fix.” The Debug Clinic test — if you took the keyboard, you broke the rule.
  • 2. Map the world as it is. Restrictions go in Outside. Captured separately for the program lead. Not vented.
  • 3. Decompose before you prompt. M2 starts with 10 minutes on paper. No paper, no help.
  • 4. Verification is non-negotiable. Same Red Pen Review from Week 1, run on a builder’s artefact under time pressure.
  • 5. The teach-back is the test. If your partner can’t repeat it, you haven’t taught it.
  • 6. The playbook ships, not the prototype. Trigger, inputs, steps, verification, fallback, owner — that’s the institutional artefact.
  • 7. Which language is this surface? Power Fx vs WDL vs DAX errors stall the room — project the Slide-22 matrix before any re-prompt.

Recovery & pacing cuesWhen the room slips, this is the order of operations

  • No one volunteers for the Debug Clinic. Cold-call the bug bank: pick a real Week-3 chat error and project it. Run it as a fishbowl.
  • A builder demands you type their fix during M3. Refuse. “If I type it, you don’t learn it. Re-prompt with these three changes.” Walk away from their keyboard.
  • Frontier map turns into venting about tool restrictions. Re-anchor: “Map the world as it is, not as you wish it. Restrictions go in Outside.” Capture the restriction list separately.
  • Power Fx vs WDL vs DAX errors stall the room. Project the language matrix from Slide 22. Ask “Which language is this surface?” before any re-prompt.
  • Teach-back pairs are silent / awkward. Force a deliverable: “In ten minutes I want one slide each — the technique, when to use it, when not to.”
  • Pacing valve. Behind at the break? Cut M3 to two students (not three) and protect M6 — the playbook is the artefact that survives the week.

Homework to issue before logoffSlide 38 — Week-6 (Capstone) gate hangs on the proposal

  • Submit the playbook from M6 to the unit shared library by EOW. One per builder, no exceptions.
  • Run a teach-back at your section within 14 days. Five minutes, one technique, witnessed by your supervisor.
  • Update the unit Frontier Map. Merge each M1 entry into the shared map. Flag any “Moving” items to the program lead.
  • Capstone gate. To attend Week 6 (Full-Stack), submit a brief proposal: which problem they’ll ship end-to-end. Due 7 days before Week 6.
EDD · Week 4 cheat sheet · page 2 of 2 · anchors, recovery, homework Pair with the Week 4 Facilitator Pack and the Week 4 hand-out pack