Week 3 Instructor Cheat Sheet

A two-page printable reference card for the Course 3 Platform Training deck — designed to sit next to the deck during the four-hour Teams session, so you never have to scrub back through 32 slides for a build spec, a switch cue, or the next failure-share.

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 three build specs to drop in chat, the failure-share script, the Centaur/Cyborg posture switch. Page 2 is the anchor phrases you repeat all afternoon, the recovery cues for when the platform misbehaves, and the homework you must issue before logoff.

Download PDF Pre-rendered Letter-portrait two-pager — convenient for email or shared printers.
3Course 3 · Platform Training
Instructor cheat sheet

Platform Training

Three deployed tools in four hours. Build #1 Centaur (Request Routing), Build #2 Cyborg (Training Tracker), Build #3 your own. Pick your posture on purpose.

4 hr · 5 modules + frontier wrap
32 slides · 2 breaks · 3 platform switches
Companion to week-3-platform-training.html
0:00M1 Setup
0:15Build #1 Centaur
1:15Brk + Share 15′
1:30Build #2 Cyborg
2:30Break 15′
2:45Build #3 Your Own
3:45Frontier & Wrap
115 min
Setup & Review 0:00–0:15 Framing · Course-2 carry-in
  1. Slide 2 hand-raise: “Who didn’t deploy a tool last week?” Pair them now — do not let them sit through Build #1 alone.
  2. Plant the anchor: “Centaur when you know the answer. Cyborg when you don’t. Pick on purpose.”
  3. Tabs check (audible): deck, Power Apps, Power Automate, your test SharePoint site, GenAI.mil. Confirm Approvals connector lit.
Outcome · calibration Roster ready · pairings set Unprovisioned students paired; the room knows today is three deploys, not three demos.
B160 min
Build #1 — Request Routing 0:15–1:15 Centaur · you know the answer
  1. Hand-off (0:15): Deck → Power Apps + Power Automate side-by-side. Drop the spec into chat now.
  2. Spec (paste verbatim): “Build a request-routing flow. Spec: any request < $500 auto-approves; $500–$2000 routes to the section chief; > $2000 routes to the OIC. SharePoint list named Requests; Power Automate flow on item-create.”
  3. Posture brief (read aloud): “Centaur mode means you design the logic; AI writes the steps. No exploration — you know the answer before you prompt.”
  4. Coach in chat. Push the stuck to re-prompt with the language name in the first sentence (“in Power Fx”, “in WDL”).
Deliverable · build #1 Routing flow deployed Each student has a flow firing on item-create; thresholds verified with a test row.
BRK15 min
Break + failure share. Be back at H+1:30. Run the “failure share” slide on return: surface 2–3 students’ Build #1 errors. Do not solve — pattern-match into prompt / connector / logic / platform. 1:15–1:30
B260 min
Build #2 — Training Tracker 1:30–2:30 Cyborg · you don’t know the answer
  1. Hand-off (1:30): Deck → Power Apps. Switch posture audibly: “Now it’s exploratory. You drive, AI rides shotgun.”
  2. Spec (paste verbatim): “Build a Training Tracker that reads a roster, lets a section leader mark someone qualified / lapsed, and emails a weekly summary.”
  3. Posture brief: “Cyborg mode means continuous loop — you and the AI explore options together. Try at least one path you discard.”
  4. Roam in chat. When students lock in too early, push back: “What’s the path you didn’t try?”
Deliverable · build #2 Tracker + weekly summary email Plus one discarded path documented in chat — that’s the cyborg artefact, not just the tool.
BRK15 min
Break. Be back at H+2:45. Pre-flight: confirm everyone’s test SharePoint site is reachable; have the Build #3 hand-off slide queued. 2:30–2:45
B360 min
Build #3 — Your Problem 2:45–3:45 Choose mode · deploy
  1. Hand-off (2:45): Deck → each student’s own portal. Each picks Centaur or Cyborg before they start — record the choice in chat.
  2. Brief (read verbatim): “Pick one tool from your unit’s real backlog. State in chat: which mode you’re in and why. If you finish, deploy to your test site and post the URL.”
  3. Stretch for the fast finishers: add a comments column, a managers-only view, or pair with a stuck student as navigator.
Deliverable · build #3 Deployed URL in chat If anyone didn’t finish, they owe the URL by EOW — the Week 4 gate hangs on it.
F15 min
Frontier Update & Wrap 3:45–4:00 Map + assignment
  1. Frontier sync (read verbatim): “Looking at all three builds today — where did AI land inside the frontier? Where did it fall outside? Add three entries to your map. We feed these into the unit-wide map in Week 4.”
  2. Capture on Slide 31 (all laptops up; share-screen or camera).
  3. Issue the Week-4 gate: at least one deployed tool URL or screenshot 72 h before Week 4. No URL, no seat.
Outcome · commitments Frontier updated · gate set Each student logs three frontier entries; gate evidence due 72 h before Week 4.
EDD · Week 3 cheat sheet · page 1 of 2 · pacing, build specs, deliverables Print landscape off · portrait, default margins, background graphics on
3Course 3 · Platform Training
Cheat sheet · page 2

Anchors, recovery, homework

The phrases you repeat all afternoon, the failure modes to watch for at the platform switches, and the homework that gates Week 4 attendance.

Use during: 1:15 failure share
Use during: any platform glitch
Companion to week-3-platform-training.html

Pre-flight & hand-off cuesDone 48 h before; verified at T-30 min · three platform switches today

  • Provisioning sweep. Every roster student has Power Apps, Power Automate, and Approvals connectors enabled. Fix at least 24 h out — tickets take time.
  • Tabs & portals. Deck (Week 3), this cheat sheet, GenAI.mil, make.powerapps.com, make.powerautomate.com, a clean SharePoint site for the day’s lists.
  • Sample data. Stage a Requests SharePoint list (5 sample rows spanning the $500 / $2000 thresholds) for Build #1; stage an Excel TrainingRoster for Build #2.
  • Approvers. Roster of supervisors for the routing approval test; have a stand-in account ready in case real approvers are unreachable.
  • Course 2 failures. Pull homework failure cases from the Week 2 chat into a one-screen list for the 1:15 failure share.
  • 0:15. Deck → Power Apps + Power Automate side-by-side. Drop Build #1 spec into chat.
  • 1:15. Return to deck. Failure share — pattern-match, do not solve.
  • 1:30. Deck → Power Apps for Build #2. Switch posture audibly.
  • 2:45. Deck → student’s own portal. Each student records mode choice in chat.
  • 3:45. All laptops up to camera or share-screen for the Frontier Map update; capture on Slide 31.

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

  • 1. “Centaur when you know the answer. Cyborg when you don’t. Pick on purpose.” Open with it; cite at the Build #1 / Build #2 / Build #3 hand-offs.
  • 2. We pattern-match, we don’t solve. The failure share is diagnosis — prompt / connector / logic / platform — not group debugging.
  • 3. Name the language in the first sentence. “In Power Fx …” “In WDL …” “In DAX …” The wrong-language emit is the #1 fix.
  • 4. Try one path you discard. Cyborg without exploration is just slow centaur. The discarded path is the artefact.
  • 5. Map the world as it is. Connector denials, tenant gaps — that’s “Outside the frontier,” not a complaint. Capture, don’t vent.
  • 6. Deployed beats demoed. A URL in chat is the only acceptable Build #3 artefact. Anything else is owed by EOW.

Recovery & pacing cuesWhen the platform misbehaves, this is the order of operations

  • SharePoint “Integrate” / Power Apps button missing. Build a blank Canvas app and connect to the list manually. Lose 5 min, gain a useful skill.
  • Approvals connector unavailable in tenant. Skip the approval step in Build #1 — email-on-create instead. Note the gap for the program lead.
  • AI returns JavaScript / DAX instead of Power Fx or WDL. Re-prompt with the language name in the first sentence. Coach — do not paste the fix.
  • Student finishes Build #1 in 20 min and is bored. Issue the stretch: comments column, managers-only view, or pair as navigator with a stuck student.
  • Whole room is behind at 2:30. Compress Build #3 to 30 min — spec only, no deploy. Protect the Frontier wrap; that’s the Week-4 hand-off.
  • Pacing valve. If you’re behind at 1:15, cut the failure-share to one student and the Build #2 brief to two sentences. Never cut the Frontier update.

Homework to issue before logoffSlide 31 — Week-4 attendance gate hangs on these

  • Deploy Build #3. If they didn’t finish, ship the smallest version they can defend by EOW. Post the URL in the Week 3 chat thread.
  • Take one tool to a real user. Watch them use it once without coaching. Record what broke. Bring that to Week 4’s Debug Clinic.
  • Frontier Map update. Sync each personal map with the unit’s shared map. Consolidated on Week 4 · M1.
  • Advanced track gate. To attend Week 4, every student must have at least one deployed tool. Post evidence (URL or screenshot) by 72 h before Week 4. No evidence, no seat.
EDD · Week 3 cheat sheet · page 2 of 2 · anchors, recovery, homework Pair with the Week 3 Facilitator Pack for prep / hand-off / homework detail