Week 3 Facilitator Pack

One-page companion for the Course 3 instructor deck. Print landscape, keep next to the deck during delivery.

Print this page in landscape from Chrome or Edge: Ctrl+P → Layout Landscape → Margins None or Default → Background graphics on. The site chrome above is hidden in print. Chat-paste blocks for this session live in the Week 3 hand-out pack.

In the print dialog, leave Margins at Default (or pick None). Picking Custom or Minimum shrinks the printable area below what this layout assumes and the pack tips onto a second page.

Download PDF Pre-rendered Letter-landscape one-pager — convenient for email or shared printers.
3 Course 3 · Facilitator Pack

Platform Training

Three deployed tools: Centaur (Request Routing), Cyborg (Training Tracker), and your own. Power Platform under live load.

Duration4 hr (2 breaks)
AudienceBuilders
PrereqCourse 2 + M365 / Power Platform
0:00–0:15M1 Setup & Review15 min
0:15–1:15Build #1 Request Routing60 min · Centaur
1:15–1:30Break + Failure share15 min
1:30–2:30Build #2 Training Tracker60 min · Cyborg
2:30–2:45Break15 min
2:45–3:45Build #3 Your Problem60 min · choose mode
3:45–4:00Frontier update & wrap15 min

Pre-session prepDone 48 h before; verified at T-30 min

  • 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 pack, GenAI.mil, make.powerapps.com, make.powerautomate.com, a clean SharePoint site for the day’s lists.
  • Sample data. Stage Requests SharePoint list (5 sample rows with $ amounts spanning the $500 / $2000 thresholds) for Build #1; stage an Excel TrainingRoster for Build #2.
  • Roster of supervisors for the routing approval test; have a stand-in account ready in case real approvers are unreachable.
  • Course 2 failures collected. Pull homework failure cases from the Week 2 chat into a one-screen list for the 1:15 break share.

Live hand-off cuesThree platform switches; deck stays as anchor

  • 0:15. Deck → Power Apps + Power Automate side-by-side. Drop the Build #1 spec into chat.
  • 1:15 break. Return to deck. Run the “failure share” slide; surface 2–3 students’ Build #1 errors. Do not solve — pattern-match.
  • 1:30. Deck → Power Apps for Build #2. Switch posture: “Now it’s exploratory. You drive, AI rides shotgun.”
  • 2:45. Deck → student’s own portal. Each student picks Centaur or Cyborg before they start — record the choice in chat.
  • 3:45. All laptops up to camera or shared-screen for the Frontier Map update; capture in deck on Slide 31.

Exercise & activity promptsRead these to the room verbatim

Build #1 · Centaur (60 min) — Request Routing. “You are building 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. Centaur mode means you design the logic; AI writes the steps. No exploration — you know the answer before you prompt.”

Failure share (15 min, after the break). “Three of you in chat — post your single biggest error from Build #1 and what you tried. We do not solve. We label: prompt issue, connector issue, logic issue, or platform issue.”

Build #2 · Cyborg (60 min) — Training Tracker. “Build a Training Tracker that reads a roster, lets a section leader mark someone qualified / lapsed, and emails a weekly summary. Cyborg mode means continuous loop — you and the AI explore options together. Try at least one path you discard.”

Build #3 · Your Problem (60 min). “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.”

Frontier Map update (15 min). “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.”

Anchor phrase“Centaur when you know the answer. Cyborg when you don’t. Pick on purpose.”

When this goes sidewaysTop failure modes & recovery

  • 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: add a comments column, build a managers-only view, or pair with a stuck student as navigator.
  • 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.

Post-session homeworkIssue at Slide 31, before logoff

  • Deploy Build #3. If you didn’t finish, ship the smallest version you 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 clinic.
  • Frontier Map update. Sync your personal map with your unit’s shared map. We’ll consolidate it on Week 4 · M1.
  • Advanced track gate. To attend Week 4 you must have at least one deployed tool. Post evidence (URL or screenshot) by 72 h before Week 4.
3 Share-in-chat URL sheet

Platform Training — class links

Every URL the Week 3 deck cues you to drop into Microsoft Teams chat. Read aloud or type into the chat — no copy buttons since this is the printed pack.

Deck materials

The four files instructors typically share at the start of the four-hour session.

  • Week 3 Student Handout

    When: Drop in chat at session start (and again after the break) so latecomers have the build prompts.

    https://jeranaias.github.io/ExpertDrivenDevelopment/handouts/week-3-platform-training.html

  • Week 3 Facilitator Pack (HTML)

    When: Send to a co-facilitator running the failure-sharing capture in Module 3 or 4.

    https://jeranaias.github.io/ExpertDrivenDevelopment/facilitator/week-3-platform-training.html

  • Week 3 Facilitator Pack (PDF)

    When: Email-friendly one-pager.

    https://jeranaias.github.io/ExpertDrivenDevelopment/facilitator/pdf/week-3-platform-training.pdf

  • Week 3 PowerPoint deck

    When: For instructors who present from PowerPoint or want to edit the slides locally.

    https://jeranaias.github.io/ExpertDrivenDevelopment/pptx/week-3-platform-training.pptx

  • Week 3 slide deck (HTML)

    When: For students who missed the live session.

    https://jeranaias.github.io/ExpertDrivenDevelopment/decks/week-3-platform-training.html

Build support & references

Resources to drop in chat during the three live builds — QA, prompt scaffolds, and the EDD SOP for the verification habit.

  • QA Checklist template

    When: Drop after each of the three builds so students can self-check before they ship to their unit.

    https://jeranaias.github.io/ExpertDrivenDevelopment/templates/qa-checklist.md

  • Prompt Library

    When: Slide 11 references “canonical answers from the instructor page” — this is the working library students should pull from when stuck.

    https://jeranaias.github.io/ExpertDrivenDevelopment/resources/prompt-library.html

  • Documentation Package Outline

    When: For the Module 5 wrap — the structure students use to document each Power Platform tool they ship.

    https://jeranaias.github.io/ExpertDrivenDevelopment/templates/documentation-package-outline.md

  • Tool Registry Entry template

    When: Drop after Module 5 so students log their three deployed tools to the unit registry.

    https://jeranaias.github.io/ExpertDrivenDevelopment/templates/tool-registry-entry.md

  • EDD SOP (PDF)

    When: Reference for the verification habit, the documentation package, and the tool registry process referenced throughout Week 3.

    https://jeranaias.github.io/ExpertDrivenDevelopment/pdf/SOP_Expert_Driven_Development_v5.pdf

Frontier map & failure-case capture

Slides 15 and 27 point to the “shared frontier-map doc on the EDD site” for failure-case capture.

  • Shared frontier-map / failure-case doc Not on site

    When: Slides 15 and 27 cue instructors to tell students “where to log failure cases (the shared frontier-map doc on the EDD site).” The shared doc is maintained per-unit (typically in your Teams channel or unit OneNote), not as a single canonical page on the public EDD site.

    No URL — managed in your Teams channel / unit OneNote.

EDD · Week 3 Share-in-chat URL sheet · UNCLASSIFIED · mirror of the on-site Class Links page
jeranaias.github.io/ExpertDrivenDevelopment/decks/links/week-3-platform-training.html