Advanced Workshop
Frontier mapping, complex builds, group debugging clinic, verification, teach-back, workflow playbook.
Pre-session prepDone 48 h before; verified at T-30 min
- 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, this pack, 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 a clinic case.
- Teach-back pairs drafted from the roster (mix experience levels). Reveal at the start of M5.
Live hand-off cuesFrequent switches; the deck holds the architecture
- 0:00 · Slide 10. Drop the frontier-map starter from the hand-out pack into chat. Set 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. You coach, you do not type.
- 2:50 · Slide 28. Drop the SOP QA drill chat-paste block. Pairs work in breakout rooms; rotate every 7 min.
- 3:20 · Slide 35. Drop the Workflow Playbook blank template. Each builder fills one playbook for one of their tools.
Exercise & activity promptsRead these to the room verbatim
M1 · Frontier Mapping (15 min silent + 15 share). “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.”
M2 · Unit Readiness Dashboard (60 min). “Spec: 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.”
M3 · Debug Clinic (40 min). “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.”
M4 · SOP QA Drill (30 min). “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.”
M5 · Teach-Back (30 min). “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.”
M6 · Workflow Playbook (30 min). “Pick one of your own tools. Fill the playbook template: trigger, inputs, steps, verification, fallback, owner. This becomes your unit’s hand-off doc.”
Anchor phrase“Coach the re-prompt. Never type the fix.”When this goes sidewaysTop failure modes & recovery
- 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 for the program lead.
- 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.” Pressure produces dialogue.
Post-session homeworkIssue at Slide 38, before logoff
- 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 your M1 entries 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 you’ll ship end-to-end. Due 7 days before Week 6.