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, every module’s exercise prompts to read aloud, and the artefact / shift each module leaves behind. Page 2 is the anchor phrases 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.
1Course 1 · AI Fluency
Instructor cheat sheet
AI Fluency Fundamentals
The 80% who quit, the six 201 skills, the delegation equation, the Red Pen Review, centaur vs cyborg, and the start of the frontier map.
0:00M1 80% Quit
0:15M2 Six Skills
0:40M3 Delegation
0:55Break 10′
1:05M4 Red Pen
1:30M5 Centaur/Cyborg
1:45M6 Frontier & Wrap
115 min
Why 80% Quit
0:00–0:15
Framing · calibration
- Slide 2 poll (read aloud): “Hands up — who has used GenAI.mil this month? CamoGPT? ChatGPT? Gemini? Never?” Pause; do not advance until laptops light up with a tool open.
- Anchor: “You are not learning to use a tool. You are learning to manage one.” First plant of the hour.
Outcome · calibrated
Room read & tools open
You know who is fluent, who has never tried, and which tool examples land for this room.
225 min
The Six 201 Skills
0:15–0:40
Demonstration · quality judgement
- Quality-judgement exercise (5 min): “Same AI, same prompt — an end-of-tour NAM for SSgt Smith. Both came back instantly. Hands up: which one survives the awards board, A or B? Defend it.”
- Cold-call one defender per side before revealing why B (specific, verifiable facts) wins over A (filler adjectives).
- Surface the six skills on the next slide; tie each back to the A-vs-B reveal in one sentence.
Outcome · vocabulary
Six skills named & ranked
Quality judgement is the one they will reach for first. Plant: “If you can’t tell the difference, you can’t supervise it.”
315 min
The Delegation Equation
0:40–0:55
Individual exercise
- 3-min think (read verbatim): “Pick one task you owned this week. Write down: who is the audience? what does done look like? what could go wrong?”
- Decide aloud: “Now decide — would you delegate it to a brand-new Marine? If yes, that’s an AI-shaped task.”
- Cold-call two: one yes, one no. Don’t adjudicate — let the equation do the work.
Outcome · framework
Delegation test in head
Each person has run the test on a real task. Frames every example for the rest of the hour.
BRK10 min
Break. Be back at H+1:05. Pre-flight: stage the two Red Pen Review documents in Teams chat now so you paste the moment you return.
0:55–1:05
425 min
Red Pen Review
1:05–1:30
Activity · the protocol
- Drop both AI-drafted documents in Teams chat. Set a 10-min silent timer. Mute. (Read verbatim:) “You have ten minutes. Read both documents. Mark up everything you would change before sending it forward. Mute your mic. Go.”
- Debrief (10 min) — surface three categories on the reveal slide: fabricated facts, missing context, tone mismatch.
- Close: “The point is the protocol, not the score. You will run this on every AI output for the rest of the program.”
Outcome · habit
Verification habit installed
The Red Pen Review is the verification rule cited in Weeks 4 and 5. This is where it lands.
515 min
Centaur vs Cyborg
1:30–1:45
Workflow mapping
- 8-min mapping (read verbatim): “Pick one recurring task. Sketch its current steps. Mark each step: only-me, centaur (I design, AI executes), cyborg (continuous back-and-forth), only-AI. Now circle which step you’ll change next week.”
- Cold-call three from chat or hand-up — one centaur example, one cyborg, one only-me they’d like to flip.
Outcome · vocabulary
Two postures, one decision
Anchor: “Centaur when you know the answer. Cyborg when you don’t. Pick on purpose.” (Re-cited in Week 3.)
615 min
Frontier Map & Wrap
1:45–2:00
Seed + assignment
- Frontier seed (5 min): “On a sticky note: one task AI does well for you, one task AI fails at for you. We’ll grow this into the full unit map in Week 4.”
- Issue homework live (do not let people leave without writing it down): use AI on one task this week, two more frontier entries, builders/supervisors read the right Course 2 / Course 5 page before next week.
- Repeat the anchor: “You are not learning to use a tool. You are learning to manage one.”
Outcome · commitments
Frontier seeded · homework banked
Two frontier entries per student in your collection bucket; track choice (Course 2 or 5) for next week.
1Course 1 · AI Fluency
Cheat sheet · page 2
Anchors, recovery, homework
The phrases you repeat all hour, the recovery cues for when the room slips, and the homework you must issue before logoff.
Pre-flight & hand-off cuesVerified at T-15 min · deck stays primary all hour, no platform switch
- Tools. Confirm the room can reach GenAI.mil (preferred, CAC) and one fallback (CamoGPT, ChatGPT, Gemini). Test on 2–3 student laptops the morning of.
- Tabs open. Deck (Week 1), this cheat sheet, GenAI.mil, NAVMC 10274 reference for the Module 2 examples.
- Sample data. The two pre-drafted SSgt Smith NAM citations (Output A and B) loaded for M2; both Red Pen Review documents staged for M4 before the break starts.
- Teams. Spotlight presenter; chat on; recording off unless approved. Cameras-on prompt at start.
- Slide 2. Pause and watch laptops light up with their AI tool open. Don’t advance until most are visible.
- M4 hand-off. Drop the prepared documents in chat → 10-min silent timer → mute → return to deck for the debrief reveal slide.
- M5 hand-off. Each student writes one current task on a notecard / chat line and labels it Centaur or Cyborg. Cold-call three.
Anchor phrasesPlant in the opening; cite by name when you need them
- 1. “You are not learning to use a tool. You are learning to manage one.” Open with it; repeat at Slide 8 and at the wrap.
- 2. “Quality judgement is the floor.” If you can’t tell A from B in M2, none of the other five skills matter.
- 3. The Delegation Equation. Audience · done · risk — would I hand this to a brand-new Marine? If yes, it’s AI-shaped.
- 4. The Red Pen Review is non-negotiable. Three categories: fabricated facts, missing context, tone mismatch. Run it on every AI output.
- 5. Centaur vs Cyborg is a choice. Centaur when you know the answer; cyborg when you don’t. Pick on purpose — don’t drift.
- 6. Map the frontier as it is, not as you wish it. One does-well, one fails-at. Two more by next week.
- 7. Today is unclassified, no PII. Re-anchor if a question drifts toward classified or sensitive data; point to the Tools page.
Recovery & pacing cuesWhen the room slips, this is the order of operations
- AI tool unreachable for the whole room. Skip the live tool. The Module 2 outputs and the Red Pen Review documents are in the deck — run as paper exercises. Don’t cancel.
- Quiet room, no hands at the show-of-hands. Cold-call by name. Quiet rooms are confused rooms; re-state the question more concretely.
- Student insists Output A is better in M2. Don’t argue. Ask: “Which sentence in A could you verify with a record? Which in B?” Let the count make the case.
- Running long at the break. Compress M5 to a single cold-call (skip the workflow mapping); protect the M4 Red Pen debrief and the M6 wrap-assignment.
- Student asks “what about classified?” Re-anchor: today is unclassified, no PII. Point to Tools page for full data-handling boundaries.
- Pacing valve. If you fall behind, M5 is the cut. Never cut the Red Pen debrief or the homework issue — they are the two artefacts that survive next week.
Homework to issue before logoffSlide 51 — do not let the room exit without these
- Use it once for real this week. Pick one task from the M5 workflow map; use AI on it. Bring the result — success or failure — to the section meeting.
- Add to the frontier sticky. Two more entries: one task AI handled well, one it didn’t. We collect these for the unit map in Week 4.
- Builders & supervisors: read the Course 2 (Builder Orientation) and Course 5 (Supervisor) course pages before next week so they self-select the right track.
- Blocker channel. If something blocks them (no tool access, unclear policy), email it to the program lead by EOW — we’ll resolve it before Week 2.