Week 2 Instructor Cheat Sheet

A two-page printable reference card for the Course 2 Builder Orientation deck — designed to sit next to the deck during the two-hour Teams session, so you never have to scrub back through 28 slides for a prompt or the next platform switch.

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 five live-build prompts to run in M2, the M3 hand-off, and the M4 paper drill. Page 2 is the anchor phrase you repeat all hour, the recovery cues for when the room slips, and the homework you must issue before logoff.

Download PDF Pre-rendered Letter-portrait two-pager — convenient for email or shared printers.
2Course 2 · Builder Orientation
Instructor cheat sheet

Builder Orientation

From AI user to AI-assisted builder. One live build (Equipment Tracker), one student build, one paper decomposition drill. Decompose first, prompt second.

2 hr · 5 modules + wrap
28 slides · 1 break · 2 platform switches
Companion to week-2-builder-orientation.html
0:00M1 User→Builder
0:15M2 Live Build
0:40Break 10′
0:50M3 Student Build
1:30M4 Decompose
1:50M5 Wrap
115 min
User → Builder 0:00–0:15 Framing · talk
  1. Slide 2 hand-raise: “Who skipped Course 1?” Pair anyone who raises with a stronger partner before M3.
  2. Anchor (plant now, repeat at M4 and the wrap): “Decompose first. Prompt second. The prompt is the easy part.”
Outcome · framing Posture set Room knows today is hands-on; pairing risk identified before the live build runs.
225 min
Live Build — Equipment Tracker 0:15–0:40 Demo · watch only
  1. Hand-off (audible): “Watch — do not type along.” Open make.powerapps.com and GenAI.mil; press P in the deck to keep speaker notes pinned.
  2. 5-min decompose on whiteboard: Four questions — data fields? user actions? simplest useful version? data structure? Capture: item name, serial, assigned-to, date out, date due, status. Actions: check out, check in, see what’s out, see overdue.
  3. Prompt 1 (Define, 2 min): “I need an equipment checkout tracker for a Marine rifle section (~30 people, ~50 items) in Power Apps… Give me a step-by-step plan before we build.”
  4. Prompt 2 (Data structure, 3 min): “Give me the exact SharePoint list configuration — EquipmentCheckout: columns, types, CSV template, post-import steps.”
  5. Shortcut (audible): SharePoint → Integrate → Power Apps → Create an app. Power Apps auto-generates form + gallery.
  6. Prompt 3 (Refine, 5 min): “Filter the gallery to checked-out items, color overdue rows red, add a check-in button next to each row.”
  7. Prompt 4 (Iterate, 3 min): “Add a SearchBox + an overdue warning icon, sort overdue to the top.”
  8. Prompt 5 (Debug, 4 min): introduce one error intentionally (Choice syntax or type mismatch). Show the debug loop live.
  9. Prompt 6 (Polish, 3 min): “Marine color scheme — red, gold, dark background.”
  10. Narrate every rejection. When AI emits JavaScript instead of Power Fx, stop and re-prompt out loud. The rejection is the lesson.
Outcome · demo artefact Half-built tracker on screen Leave it visible in a second tab over the break — reference point for M3, not a copy target.
BRK10 min
Break. Be back at H+0:50. Pre-flight: confirm GenAI.mil + Power Apps are still responsive; load the Debugging Exercise Fallback (instructor page Module 2) in case anything dies. 0:40–0:50
340 min
Student Build + Peer Review 0:50–1:30 25 build · 15 review
  1. Hand-off (read verbatim): “Now you build. I’ll roam — if you get stuck, post the screenshot in chat; do not DM me.”
  2. Brief (25 min build): “Pick one starter problem — Leave request tracker, Training attendance log, Vehicle inspection checklist, or your own (clear scope with me first). Decompose on paper for 2 min. Then prompt. Post your errors and re-prompts in chat so the room sees the recovery.”
  3. Time cues: call “15 minutes left,” “5 minutes left,” hard stop at 25.
  4. Peer review (15 min): pair up. 6 min each — demo + four checks (clear problem, core function works, evidence of iteration, can explain decisions). Last minute: full-class debrief.
  5. Coach — do not type. If a student demands you fix it, refuse: “If I type it, you don’t learn it.” Ask the question that leads them to the answer.
Outcome · first build Every student has a prototype on screen Plus at least one recovered error per student logged in chat — raw material for next week.
420 min
Decomposition Drill 1:30–1:50 Paper · no AI
  1. Hand-off (audible): “Close laptops.” M4 is whiteboard / paper only. The whole point is no AI.
  2. Individual (10 min): “Pick one real problem from your section — the annoying recurring one. On paper: problem statement (one sentence), core requirements, 4–6 subtasks with Human/AI/Pattern columns, frontier risks, simplest useful version.”
  3. Pair review (8 min): trade worksheets. 4 min each — run the four checks: clarity, scope, frontier, MVP.
  4. Debrief (2 min): “Who changed their decomposition based on what their partner caught?” Take one or two examples.
  5. Walk the room. Watch for: problem too big, problem too vague, no frontier recognition, all-AI subtasks. The decomposition they walk out with is the homework they will build.
Outcome · foundation One-page decomposition of a real problem Foundation for the homework prototype and Week 3’s failure-sharing block.
510 min
Wrap & Assignment 1:50–2:00 Talk + commitments
  1. Repeat the anchor: “Decompose first. Prompt second. The prompt is the easy part.”
  2. Issue homework live (do not let people leave): build one tool of your own (Form + Gallery class), bring the failure case to Week 3, verify M365 / Power Platform access 48 h out, read the SOP · Decomposition page.
Outcome · commitments Build assignment banked One tool per student before Week 3 · failure case logged for the Week 3 chat thread.
EDD · Week 2 cheat sheet · page 1 of 2 · pacing, prompts, outcomes Print landscape off · portrait, default margins, background graphics on
2Course 2 · Builder Orientation
Cheat sheet · page 2

Anchors, recovery, homework

The phrases you repeat all hour, the failure modes to watch for at the platform switches, and the homework you must issue before logoff.

Use during: M2 & M3 platform switches
Use during: any stuck moment
Companion to week-2-builder-orientation.html

Pre-flight & hand-off cuesVerified at T-30 min · two platform switches today, narrate every decision

  • Account check. Every student needs Power Apps + Power Automate licensed in M365 and a working AI tool (GenAI.mil preferred). Run a roster check 48 h before; pair the unprovisioned with a provisioned partner.
  • Tabs open. Deck (Week 2), this cheat sheet, GenAI.mil, make.powerapps.com, a clean SharePoint test site you can create the EquipmentCheckout list on during M2.
  • Do not pre-build anything. The whole value of M2 is the room watching you decide live. Start from a blank SharePoint site.
  • Paper exercise. Print 1 decomposition worksheet per student (or post a Word/Forms link); have whiteboard markers ready for the M2 whiteboard decompose and the M4 individual drill.
  • 0:15 · deck → Power Apps. Open make.powerapps.com. Audible cue: “Watch — do not type along.”
  • 0:40 · back to deck for the break slide. Leave the half-built tracker visible in a second tab.
  • 0:50 · M3 hand-off. “Now you build. I’ll roam in chat. If you get stuck, post the screenshot — do not DM me.”
  • 1:30 · Power Apps → paper. Close laptops audibly. M4 is whiteboard / paper only.

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

  • 1. “Decompose first. Prompt second. The prompt is the easy part.” Open with it; cite at every M2 prompt and at the wrap.
  • 2. The rejection is the lesson. When AI emits the wrong language or the wrong shape, narrate the re-prompt out loud. That is the demo, not a glitch.
  • 3. Coach — do not type. If you take the keyboard, the student doesn’t learn. Hand them the re-prompt; never the fix.
  • 4. Watch — do not type along. M2 is a demo. Students build in M3, not over your shoulder.
  • 5. Post the error, not the DM. Errors go in chat so the whole room sees the recovery.
  • 6. Ship something small. A tool that runs beats a spec that doesn’t. The homework is to ship one of their own.

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

  • Power Platform / GenAI.mil / internet down. Switch to the Debugging Exercise Fallback on the instructor page (orientation.html#module-2). Walk the room through the four-bug Filter / Patch / Overdue case on paper. Do not cancel.
  • AI emits JavaScript / C# / Python instead of Power Fx. Show the error. Re-prompt: “Use Power Fx for canvas apps only — no JavaScript, no forEach, no arrow functions.” Use it as a teaching moment.
  • Half the room is unprovisioned in Power Apps. Pair-and-share — one driver, one navigator per laptop. Log the unprovisioned roster for the program lead before close.
  • Student skips decomposition and just prompts. Stop them. “Show me your fields and actions on paper. We will not unblock you until that exists.”
  • Live build runs long; M3 is being squeezed. Cut M2 prompts 5 (debug) and 6 (polish). The room will hit their own errors in M3 — more authentic. Protect M3 hands-on time at all costs.
  • Pacing valve at the break. If you are behind, M4 pair review contracts from 8 min to 4 min. Never cut M3 build time or the M5 assignment.

Homework to issue before logoffSlide 27 — do not let the room exit without these

  • Build one tool of your own (Form + Gallery class). Pick a problem from the section. Decompose on paper first. Deploy to a test SharePoint site.
  • Bring the failure case to Week 3. Whatever broke or confused you. We will use it as a live debugging case during the Frontier-recognition break.
  • Verify M365 access before Week 3: make.powerapps.com, make.powerautomate.com, a SharePoint site they can write to. Email the program lead 48 h out if any are missing.
  • Read the SOP · Decomposition page. The paper drill from M4 is the foundation Week 3 builds on.
EDD · Week 2 cheat sheet · page 2 of 2 · anchors, recovery, homework Pair with the Week 2 Facilitator Pack for prep / hand-off / homework detail