Teaching What You Hand Off
Offloading isn’t the villain and abstinence isn’t the lesson. This is how to teach it as a decision — historically normal, newly high-stakes, and worth making on purpose.
Why this is hard to teach.
The instinct in the room will pull toward one of two slogans — “technology is making us stupid” or “this is just the next calculator, relax.” Both short-circuit the actual lesson, which lives in the space between them: offloading is genuinely useful and genuinely has a cost, and the skill is choosing which capacities to keep and which to let go.
The second difficulty is that the cost is invisible in the moment and slightly embarrassing to admit. Students (and adults) don’t like discovering they can no longer do something they used to. Keep the tone matter-of-fact and zero-shame — this is a portfolio decision, not a confession.
Finally, the highest-stakes version is the one that’s hardest to see: AI offloads analysis and judgment, not just memory. A class can nod along about forgetting phone numbers and miss that the same mechanism is now pointed at the thing their future competence is made of.
Target misconceptions.
Misconception: “Offloading is bad — real learning means doing it all in your head.”
Reframe: Offloading is one of the oldest and most useful things humans do. Nobody mourns long division. The lesson isn't 'don't offload' — it's 'decide what you're offloading, on purpose.'
Misconception: “If I can look it up, I don't need to know it.”
Reframe: Sometimes true, sometimes not. The pre-AI research found that offloading spreads on its own — look one thing up and you look up the next, easier thing too. The drift is the risk, not any single hand-off.
Misconception: “AI just handles the boring parts so I can focus on thinking.”
Reframe: Usage data shows the opposite pattern — people delegate the analysis, synthesis, and writing, the top of the skill hierarchy, more than the drudgery. Worth checking which end you're actually handing over.
Two classroom-ready activities.
As a class, list everything the room has collectively stopped doing unaided — mental math, spelling, directions, phone numbers, recall of facts, first drafts. Then sort each one together into who cares / who chose this. Two columns: “fine, we chose it” and “wait, we didn’t decide that.” The surfacing is the whole point — offloading is a decision, it’s historically normal, and some of it was never actually decided.
Materials: whiteboard or shared doc. Facilitation:resist letting it become a lament for lost skills. The energy you want is “huh, we should decide that on purpose,” not “kids these days.”
Make it a class rule for a unit: on any AI-assisted task, students write their own answer first, thenconsult AI, then revise — and hand in all three. The diff between the first attempt and the revision becomes the thing you actually discuss. It operationalizes the guide’s single best-evidenced move (commit-first, from the cognitive-forcing-function research) and it makes the thinking visible in a way a finished document never does. Pair it with the Offload Audit as a private reflection students run on themselves first.
Facilitation:the revision diff, not the final answer, is where you spend class time. “What did the AI change your mind about, and was it right to?”
Discussion prompts.
Ordered easy to charged.
- 1What's something humans used to do in their heads that almost nobody does now? Was losing that skill a good trade, a bad one, or just a trade?
- 2Name one thing you've stopped doing without AI in the last year. Did you decide to stop, or did it just happen?
- 3The research says using a search tool on hard questions makes people look up easy ones too. Have you noticed that in yourself?
- 4What belongs on your keep-sharp list — the capabilities you'd want in five years whether or not the tool exists? Why those?
- 5If you wrote your own answer before opening the chat every time, what would change about how you use AI? What would be annoying about it?
- 6Is there a skill you'd be embarrassed to have quietly lost? Are you doing anything to keep it?
Seeing whether it landed.
Without a quiz, where possible:
- Have each student produce a personal keep-sharp list with a one-line defence of each item. You're assessing whether they can distinguish a capability worth protecting from one worth handing off.
- Collect the commit-first triples (attempt → AI → revision) across a unit and look for growth in the quality of the initial attempt, not just the final product.
- Ask students to catch offloading spreading in their own week — one example of reaching for AI on something they'd normally do themselves — and reflect on whether it was a decision.
When a student asks “is this actually proven?”
The offloading foundation is solid — the Google-effect studies and decades of cognitive-offloading research are well established. Be straight about the softer parts: “The finding that we later misremember AI work as more our own is real and peer-reviewed, but it’s about whose idea was it, not general memory loss. The survey linking heavy AI use to weaker critical thinking is correlational and single-author — suggestive, not settled.”
The honest headline: “that offloading has a cost is well established; exactly how much AI-specific offloading costs us, over years, is still being measured.” That’s not a hedge — it’s the state of the science, and saying so is part of the skill.
Where this leads
Teaching this is a different skill than knowing it.
Teaching AI Well is CPAI's train-the-trainer curriculum for educators — ten lessons on how to teach AI honestly, including the material on this page.