Cognitive offloading is not new and it is not bad. Writing a shopping list is offloading. So is setting an alarm, using a calculator, and keeping a calendar. Every one of those moves work out of your head into something external, and nobody thinks a calendar is hollowing them out.
So the interesting question was never whether to offload. It is which part of thinking you are handing over.
What actually changed
Earlier tools absorbed storage and arithmetic. A calendar holds dates you would otherwise rehearse. A calculator runs an operation you know how to do but would do slowly and badly.
Language models absorb synthesis, evaluation and judgement. Those are not support functions for thinking; they are what thinking is made of.
That is the whole difference, and it is why the calculator analogy — deployed constantly in this debate — does not settle anything. Nobody's professional identity rested on doing long division. A great many people's rests on being the person who can look at a mess and say what it means.
The test
Here is the version I actually use.
Would doing this myself have taught me anything I want to keep?
If no: delegate freely, and stop feeling bad about it. There is no encoding to lose. Converting a date format, remembering a syntax you look up every time anyway, cleaning a spreadsheet — you were never developing through any of it.
If yes: you are trading learning for time. That is sometimes exactly the right trade. Deadlines are real, and not every capability is worth protecting. But make it deliberately, because the trade is invisible if you do not name it.
Worked examples
Abstract rules are easy to agree with and hard to apply, so:
Beneficial — delegate freely
- Formatting, citations, converting between structures
- Recalling API syntax you look up every time regardless
- First-pass summarisation of material you will then read properly
- Boilerplate you have written a hundred times
- Translation into a language you do not speak and are not learning
Detrimental — this is where capability goes
- Having an argument constructed on a topic you are supposed to understand
- Asking which option to choose, rather than asking for the options
- Generating an opinion you will then adopt as yours
- Debugging by pasting the error without reading it
- Writing the thing you are known for writing
Genuinely ambiguous
- Drafting something you then heavily rewrite. Depends entirely on whether you had a position first.
- Explaining a concept you half-know. Can be excellent learning, or can substitute for building the model yourself.
- Code review. Catching what you missed is beneficial; not reading it yourself is not.
The ambiguous cases are the ones worth attention, because they are most of real work and they resolve differently depending on how you approach them rather than what they are.
Why detrimental offloading is hard to catch
Three properties conspire.
It does not feel like a loss. It feels like efficiency, and by any immediate measure it is. Your output is better and faster.
The output quality is genuinely fine. Nothing in the result signals that you skipped the thinking. If the work were visibly worse you would have corrected years ago.
The feedback that would tell you is the thing removed. Struggling, being wrong, revising — that is how you learn something was hard, and it is precisely what got delegated.
This is the loop called metacognitive laziness: the more fluent the output, the less it invites scrutiny, and the capacity to scrutinise decays through the same disuse as everything else. The signal that would break the cycle degrades alongside it.
The one thing that makes it visible
You need an external record, because introspection is compromised here in a specific way: your memory of your own former capability is itself degraded by the process. You are asking a witness that has been tampered with.
The fix is unglamorous. Keep a fixed, dated sample of your own unassisted work. Compare against it, not against your impression of yourself.
That is all a cognitive baseline is, and you can do a serviceable version with a text file and a calendar reminder. IMPRINT does it systematically and produces a score from the comparison, but the mechanism is not complicated — the discipline is capturing the sample before you need it, which is the part almost nobody does.
The takeaway
Offloading is not the problem. Offloading judgement while believing you have offloaded execution is the problem.
The distinction is available to you in the moment, for the cost of one question before you prompt. That is a genuinely low price for the only intervention here that reliably works.
The underlying research, with what each study does and does not establish, is on the research page.