Back to AI Fluency Fundamentals

Week 1 · Course 1 · 2 Hours · All Personnel

AI Fluency
Fundamentals

The six 201-level skills that separate sustained adopters from the 80% who quit.

Course 1 · AI Fluency Fundamentals

Before we start

How this works.

  • Two hours, six modules, one ten-minute break at the midpoint.
  • Two hands-on activities — the Red Pen Review and a workflow mapping exercise. Have a notepad open.
  • Stop me with questions. If something is unclear here, it will be unclear in your section meeting tomorrow.
  • You'll need an AI tool. GenAI.mil if you have CAC; ChatGPT, Gemini, or CamoGPT also work. Open it now.
  • This is unclassified. No real names, no PII, no operational details in your prompts today.
Course 1 · AI Fluency Fundamentals

Agenda

Six modules. Two hours.

0:00 – 0:15 1 · Why 80% Quit Frontier Recognition 0:15 – 0:40 2 · The Six Skills That Actually Matter All six — overview 0:40 – 0:55 3 · The Delegation Equation Task Decomposition, Context Assembly 0:55 – 1:05 Break 10 minutes 1:05 – 1:30 4 · The Trust Problem — Red Pen Review Quality Judgment, Frontier Recognition 1:30 – 1:45 5 · Centaur, Cyborg, or Neither Workflow Integration 1:45 – 2:00 6 · Frontier Mapping & Your Assignment Frontier Recognition, all six
Course 1 · AI Fluency Fundamentals
01

Module One

Why 80% Quit
(and how you won't)

Open instructor notes for this section ↗
Course 1 · AI Fluency Fundamentals
80%

Microsoft Work Trend Index

Three weeks of excitement. Then a crater.

Microsoft tracked AI tool adoption across 300,000+ employees. Excitement peaked at three weeks. Then most people quietly stopped.

Course 1 · AI Fluency Fundamentals

The failure loop

It always looks the same.

  • You type "help me with this report." You get something generic.
  • You try again. You get something confident and wrong.
  • You try a third time. You decide it's faster to do it yourself.
  • You never come back.
Course 1 · AI Fluency Fundamentals
25 MIN

UK Government Digital Services

Per worker. Per day. With training.

20,000 government workers, 12 departments, three months. After training, 80% refused to give the tools back — and 9 of 12 departments kept their licenses.

Course 1 · AI Fluency Fundamentals

You are not learning to use a tool. You are learning to manage one.

The thesis of this course

Course 1 · AI Fluency Fundamentals

The management framing

Would you hand a 100-page RFP to a brand new Marine and say "handle this"?

  • No. You'd break it into pieces.
  • You'd tell them which parts to tackle first.
  • You'd explain what good looks like.
  • You'd review their work and give feedback.

That's how you should work with AI.

Course 1 · AI Fluency Fundamentals
Knowledge Check — Module 1

What separates the 20% who stick with AI from the 80% who quit?

Not better prompts. Not a better tool. Not being more technical.

They manage AI — like a capable but inexperienced team member. They give it context, break work into pieces, evaluate the output, and iterate. The same skills you already use to lead Marines.

Course 1 · AI Fluency Fundamentals
02

Module Two

The Six Skills
That Actually Matter

Open instructor notes for this section ↗
Course 1 · AI Fluency Fundamentals

The Six 201 Skills

Six skills. None of them are prompt formulas.

01 Context Assembly Give AI the right information to produce useful output.
02 Quality Judgment Know whether AI output is correct, complete, and appropriate.
03 Task Decomposition Break large tasks into AI-appropriate subtasks.
04 Iterative Refinement Improve AI output through structured feedback loops.
05 Workflow Integration Embed AI into recurring processes, not one-off experiments.
06 Frontier Recognition Know what AI can and cannot do — and when that boundary shifts.
Course 1 · AI Fluency Fundamentals

Skill 1 · Context Assembly

Same task. Same AI. Different prompts.

101 — Vague

Write me a counseling statement.

201 — Expert

Write a counseling statement for a Lance Corporal who was late to formation twice this month. Tone: corrective but not adversarial. The Marine is otherwise a solid performer. Use the format from NAVMC 10274. Page 11 entry, not an adverse 6105.
Course 1 · AI Fluency Fundamentals

Skill 2 · Quality Judgment

Same prompt. Two outputs. Which gets approved?

Output A

SSgt Smith demonstrated exceptional leadership and unparalleled dedication to duty. His outstanding performance and tireless work ethic resulted in tremendous success across all areas of responsibility...

Output B

SSgt Smith led a four-Marine maintenance team responsible for 87 principal end items valued at $2.1M, maintaining 98% operational readiness over 18 months with zero accountability discrepancies across three command inspections...
Course 1 · AI Fluency Fundamentals

Skill 3 · Task Decomposition

Don't hand it the whole task. Hand it the next step.

101 — One giant ask

Write me a training plan for the platoon.

201 — Sequenced subtasks

First, list the required annual training events for FY26. Then map them against the calendar, avoiding known conflicts. Then identify which events need range time and put those first.
Course 1 · AI Fluency Fundamentals

Skill 4 · Iterative Refinement

First draft is 70%. Three passes get you to 95%.

  • Pass 1. "The tone is too formal. Make it sound like a Gunny talking to his Marines."
  • Pass 2. "Add the duty officer info: Capt Rodriguez, (831) 555-0147. Add a 250-mile liberty radius. Cut the third paragraph — it repeats the first."
  • Pass 3. "Tighten to one page. Add: no swimming at Point Lobos due to rip current advisory. Remind them about the Monday 0630 formation."

Three specific prompts. Not "make it better." Specific.

Course 1 · AI Fluency Fundamentals

Skill 5 · Workflow Integration

Stop using it sometimes. Start using it on the same task every week.

101 — Side activity

"I'll try the AI thing for this one report later."

201 — Recurring step in the workflow

"Every Friday the duty NCO drafts the weekend safety brief in GenAI.mil from the current weather, liberty boundaries, and recent incidents. That's how we do it."
Course 1 · AI Fluency Fundamentals

Skill 6 · Frontier Recognition

Know what AI can do for you. Know what it can't. Know that the line moves.

AI handles well

Drafting correspondence, summarising long documents, formatting, naming conventions, brainstorming, restructuring text, translating between styles.

AI handles poorly

Interpreting specific MCOs, calculating TIS/TIG accurately, anything requiring institutional knowledge that isn't in its training data, anything where the cost of being wrong is high.

Course 1 · AI Fluency Fundamentals
−19 PTS

BCG × Harvard, 2023

Untrained AI use can make you worse than no AI at all.

When 758 BCG consultants used AI on tasks outside the frontier, they were 19 percentage points less likely to produce correct work than the control group with no AI.

Course 1 · AI Fluency Fundamentals
Knowledge Check — Module 2

An AI draft of an awards write-up has dates, names, dollar figures, and reads beautifully. Sign it?

No. Not until Quality Judgment kicks in. AI presents fabricated facts with the same confidence as real ones. Verify the dollar figures against the property book. Verify the dates against the award period. Verify the reference numbers exist.

Reads beautifully ≠ is accurate. Your name goes on the bottom.

Course 1 · AI Fluency Fundamentals
03

Module Three

The Delegation
Equation

Open instructor notes for this section ↗
Course 1 · AI Fluency Fundamentals

Three questions, every task

Before you delegate, ask:

  • 1. Human baseline. How long would this take me to do myself?
  • 2. Probability of success. How likely is AI to produce acceptable output?
  • 3. AI process time. How long does it take me to request, wait, and evaluate?

Delegate when (1) is large, (2) is high, and (3) is much smaller than (1).

Course 1 · AI Fluency Fundamentals

Example 1 · 5-paragraph order

Verdict: Delegate.

  • Human baseline: 4 hours from scratch.
  • AI drafts in: minutes.
  • Review time: 45 minutes for accuracy and unit-specific details.
  • Probability AI gets the structure right: ~70%.
  • Net: roughly three hours saved. Delegate the structure, fix the specifics.
Course 1 · AI Fluency Fundamentals

Example 2 · TIS/TIG calculation for promotion

Verdict: Don't delegate.

  • Human baseline: 5 minutes with the right references.
  • AI process: may or may not be right, hard to tell.
  • Review time: as long as just doing it yourself.
  • Net: zero saving, real risk of error. Do it yourself.

Short tasks with a high cost of being wrong are usually not worth delegating.

Course 1 · AI Fluency Fundamentals

Example 3 · Quarterly training schedule

Verdict: Delegate the structure. Fill in the specifics yourself.

  • Human baseline: 6 hours.
  • AI produces: a solid first-draft structure in minutes.
  • Review time: 30 minutes to align with your unit's calendar.
  • Net: ~5 hours saved on structure. Specifics still come from you.
Course 1 · AI Fluency Fundamentals

AI doesn't replace expertise.
It rewards it.

The expertise multiplier — Mollick, 2026

Course 1 · AI Fluency Fundamentals
Knowledge Check — Module 3

A task takes you 10 minutes. AI does it in 30 seconds — but you spend 12 minutes verifying. Delegate?

No. The third number in the equation — AI process time — includes evaluation. If checking takes longer than doing, the AI cost you time, not saved you time.

The fast tasks where AI looks efficient are often the ones where the math doesn't actually work. Always count evaluation time.

Course 1 · AI Fluency Fundamentals

Halfway point

Break.

Ten minutes. Stretch, refill, check messages. We're back at [TIME] for the Red Pen Review.

Course 1 · AI Fluency Fundamentals
04

Module Four

The Trust Problem —
Quality Judgment

Open instructor notes for this section ↗
Course 1 · AI Fluency Fundamentals

AI is confidently right and confidently wrong — in the same paragraph.

The fundamental Quality Judgment problem

Course 1 · AI Fluency Fundamentals
Exercise 10 min individual · 5 min pair · 10 min debrief

Red Pen Review.

Your job

  1. Read each of the three AI-generated documents in the Teams chat.
  2. Mark every claim you would not sign — facts, references, numbers, procedures, anything.
  3. Note why you flagged each one.

Use this checklist

  • References & citations — do they exist?
  • Facts & statistics — verifiable?
  • Internal consistency — do dates / names / units match?
  • Procedural accuracy — is this how it really works?
  • Substance vs style — real content or polished filler?
  • Would you sign it?
Course 1 · AI Fluency Fundamentals

The three documents

Realistic AI output. Not trick questions.

  • Doc 1 · Award narrative. A NAM recommendation for a Corporal — reads polished, looks reasonable.
  • Doc 2 · SOP excerpt. Check-in / check-out procedures with reference numbers and step lists.
  • Doc 3 · Training write-up. An after-action style summary with statistics and dates.

These are not "gotcha" documents with one planted error. They're realistic first drafts — the kind of output AI actually produces, with the kinds of problems it actually creates.

Course 1 · AI Fluency Fundamentals

Debrief · Document 1

Award narrative for Cpl Hernandez.

What's wrong

  • "47% reduction" and "156 man-hours per quarter" are unsupported — AI invented them.
  • Reference to "MARADMIN 045/26" — verify it exists; cited MARADMINs are a common AI fabrication.
  • "Highest mark in the regiment" — bold claim, no source. Awards boards will ask.
  • Filler vocabulary: unparalleled, tireless, selfless. Sound impressive, prove nothing.

What's right

  • Format follows NAM narrative conventions.
  • Period of service and unit are correctly placed.
  • Closing reflects-credit-upon paragraph is correct boilerplate.
Course 1 · AI Fluency Fundamentals

Debrief · Document 2

SOP excerpt — check-in / check-out.

What's wrong

  • Reference (a) "MCO 1000.6A" — verify the order and revision letter exist.
  • "CMC Form 4790/142" — AI loves to invent plausible form numbers. Look it up.
  • Times and locations ("Bldg 1284, Rm 203", "every Monday at 0800") — specific enough to look real, but ungrounded in any source you gave the AI.
  • Procedural gap: no mention of the medical, dental, or finance check-in stops most units actually require.

What's right

  • Document structure and numbering follow standard SOP conventions.
  • Inclusion of an effective date and references section is correct.
  • The 72-hour reporting window is a reasonable default.
Course 1 · AI Fluency Fundamentals

Debrief · Document 3

Training event after-action.

What's wrong

  • Statistics presented to one decimal place ("98.7%") suggesting precision the source data can't support.
  • Inconsistent attribution — the document credits one billet for work another billet performed.
  • Claims that are positive but unverifiable: "highest in the regiment", "first time in five years".
  • Recommendations section parrots the observations — no real analysis underneath.

What's right

  • Five-paragraph after-action structure is correctly applied.
  • Tone is appropriate — descriptive, not adversarial.
  • Useful as a starting structure if you replace the invented specifics with real ones.
Course 1 · AI Fluency Fundamentals

The Verification Hierarchy

Match the depth of review to the cost of being wrong.

  • High-stakes documents (legal, personnel, financial) — line-by-line verification of every fact, reference, and number. Centaur mode. Human verifies everything.
  • Medium-stakes documents (correspondence, reports, briefings) — spot-check key claims, verify references, check tone. Mixed mode.
  • Low-stakes documents (first drafts, brainstorming, formatting) — quick review for obvious errors. Cyborg mode.
Course 1 · AI Fluency Fundamentals
Knowledge Check — Module 4

An AI document includes a confident reference to "MCO 5215.1J". You don't recognize it. Action?

Look it up. Always. AI invents Marine Corps order numbers in confident, plausible formats — correct prefix, correct format, completely fabricated content.

If a reference can't be verified in MCO Library / EPME / your reference library, it's fabricated. Strike it. Verifiable references go in. Made-up ones don't.

Course 1 · AI Fluency Fundamentals
05

Module Five

Centaur, Cyborg,
or Neither

Open instructor notes for this section ↗
Course 1 · AI Fluency Fundamentals

The two patterns — BCG × Harvard, 2023

Pick the pattern that fits the task. Don't pick one and apply it to everything.

Centaur

Clear division of labour. Human does Phase 1, hands off to AI for Phase 2, human reviews in Phase 3. Distinct responsibilities, clear handoff points, verification at every boundary.

Best for: high-stakes work that needs accountability. Legal review, admin separations, security packages, fitrep drafts.

Cyborg

Continuous integration. Constant back-and-forth between human and AI. The boundary is fluid — sometimes you write, sometimes AI does, sometimes you edit each other.

Best for: creative and iterative work. Building Power Apps, writing SOPs, drafting training materials, exploratory data analysis.

Course 1 · AI Fluency Fundamentals

Centaur, in practice

Phase. Handoff. Phase. Handoff.

  • Human designs. You decide what's needed, what good looks like, and the rules.
  • AI executes. AI drafts, formats, summarizes — whatever the design calls for.
  • Human verifies. Every fact, every reference, every number — line by line.
  • AI refines. You hand back specific corrections; AI applies them.
  • Human accepts. Final review before your name goes on it.

Verification at every boundary. This is the pattern for anything you sign.

Course 1 · AI Fluency Fundamentals

Cyborg, in practice

Continuous back-and-forth. Both hands on the wheel.

  • Start with a rough idea: "I need to see who's overdue on annual training."
  • Build incrementally — data model, input, dashboard, reports.
  • At each step, evaluate and redirect: "That chart shows it by person; I need it by date."
  • Sometimes you type. Sometimes AI generates. The boundary is fluid.

Use this for creative work, prototyping, and exploration — not for documents you sign.

Course 1 · AI Fluency Fundamentals
Exercise 7 min individual · 3 min share-out

Map one of your workflows.

On your notepad

  1. Pick one recurring task from your real job.
  2. Break it into 3–5 subtasks.
  3. Mark each subtask: Human only / AI could help / AI should do this.
  4. Decide: is this centaur or cyborg?
  5. Estimate time saved if AI handled the appropriate subtasks.

Then

  • Two volunteers will share their map.
  • The room reacts: did they put a subtask in the wrong column?
  • Common pattern: 30–50% of recurring work has AI-appropriate subtasks people have never tried delegating.
Course 1 · AI Fluency Fundamentals
Knowledge Check — Module 5

You're prototyping a Power App. Centaur or cyborg?

Cyborg. Prototyping is creative, iterative, exploratory — the boundary between you and AI is fluid. You're not signing anything; you're discovering what the right tool looks like.

Once the prototype works and you're documenting it for production — switch back to centaur. Verify everything before your name goes on the user guide.

Course 1 · AI Fluency Fundamentals
06

Module Six

Frontier Mapping
& Your Assignment

Open instructor notes for this section ↗
Course 1 · AI Fluency Fundamentals

The Jagged Frontier

The line is uneven. The line moves. Map it for your work.

AI handles well today

Drafting correspondence · summarizing long documents · restructuring text · brainstorming · formatting · explaining concepts · translating between styles.

AI handles poorly today

Specific MCO interpretation · TIS/TIG calculations · current personnel data · anything classified · anything where institutional knowledge isn't in its training set.

Course 1 · AI Fluency Fundamentals
Exercise 5 min individual · 5 min share-out

Seed your section's frontier map.

On your notepad

  1. Write three columns: Handles well, Handles poorly, Moving frontier.
  2. Add at least two examples per column from your real work.
  3. Star the failure cases that surprised you.

Then

  • Three volunteers share one example from each column.
  • The room adds to the master list in the Teams chat.
  • That list goes home with you — it's your section's starter map.
Course 1 · AI Fluency Fundamentals

Your assignment — before next week

Three things. One week.

  • 1. Pick one recurring task from your workflow map (Module 5).
  • 2. Try AI on it this week — centaur or cyborg, your call.
  • 3. Bring your results — especially your failure cases — to share with your section.

If you're continuing to Builder Orientation: bring a problem you want to build a tool to solve.

Course 1 · AI Fluency Fundamentals

Course recap

What you take with you.

6
Skills. Context, Quality, Decomposition, Iteration, Workflow, Frontier. None are prompt formulas.
3
Numbers in the equation. Human baseline. Probability of success. AI process time — including evaluation.
2
Patterns. Centaur for what you sign. Cyborg for what you explore. Switch as the task changes.
1
Habit. Always look up references. Always count evaluation time. Always share failure cases.
11
Weeks. The time it takes to build the AI habit. You are on Day 1. Stay on the curve.
80%
Quit. They didn't have what you have now. You will be in the other 20.
Course 1 · AI Fluency Fundamentals

Where you go from here

If you want to use AI better — you're done. If you want to build — Course 2 is next.

Course 2 · Builder Orientation

2 hours. Aspiring builders. From user to builder. Live builds. Debugging with AI. Decomposition exercises on a real problem you bring.

Bring: a problem in your workflow you want to solve with a tool.

For everyone else

Keep applying the six skills this week. Re-take this course on the EDD site any time. Add to your section's frontier map. Recommend the course to one person who hasn't taken it.

Course 1 · AI Fluency Fundamentals
Instructor only After class — before you forget

What to do once the room clears.

Today (within 1 hour)

  1. Send the Teams chat transcript — especially the seeded frontier map — to every attendee.
  2. Note which knowledge-check questions caused the longest pause; flag for next delivery.
  3. Capture any failure cases the room shared — they're examples for the next cohort.

This week

  1. One-week follow-up message: ask attendees what they tried and what failed.
  2. Forward Builder Orientation sign-ups to the program coordinator.
  3. Update the EDD frontier-map page with new examples from the cohort.
  4. Schedule the next session before momentum decays. 11 weeks to habit, remember.
Course 1 · AI Fluency Fundamentals

Thank you

Questions?

You now have the framework that separates the 20% who stick from the 80% who quit. The tools will keep changing. The six skills won't.

Course 1 · AI Fluency Fundamentals