Some regular AI users notice that starting a task unaided feels harder after repeatedly asking a model to produce the first draft. That observation does not prove permanent skill loss, and this article does not claim it does. It is a reason to check whether the workflow still includes practice for abilities the user wants to maintain.
This is not an argument against using AI for writing, coding, or analysis. It is a way to notice which specific tasks are quietly outsourcing the part of the work where learning actually happens, so you can keep an unaided rep in the loop for the handful of skills you care about protecting.
What the evidence actually shows
In June 2025, MIT Media Lab researchers published Your Brain on ChatGPT, a preprint describing 54 participants writing essays under three conditions: using an LLM, using a search engine, or writing unaided. The authors reported differences in EEG connectivity across the conditions, with the unaided group showing the strongest connectivity in their analysis and the LLM group the weakest (Kosmyna et al., MIT Media Lab, 2025). They use “cognitive debt” as an interpretive metaphor. The study does not establish a clinical condition, permanent impairment, or a dose-response law in which harm necessarily compounds with every use.
The LLM group reported less ownership of their essays and had difficulty quoting them just after writing (full preprint, arXiv:2506.08872). An optional fourth session included only 18 participants, nine switching from each of the LLM and unaided conditions to the other. They selected from topics they had written about before. The authors reported increased connectivity for the unaided-to-LLM group on a familiar topic and weaker connectivity for the reverse sequence. This small follow-up does not separate tool order from topic familiarity, and EEG connectivity is not a direct measure of lasting skill or learning quality.
This lines up with a broader idea in the automation-bias literature: the “cognitive miser” pattern, where people default to whatever costs the least mental effort available to them in the moment (What is Wrong With Automation Bias?, Philosophy & Technology, 2026). A fluent draft can make it easy to skip an attempt. Check whether that is appropriate for the specific task and learning goal.
The common misconception
The misconception is not “AI makes you dumber”; that framing is both unproven as a permanent, universal claim and not what the research actually says. The MIT study is a single preprint with 54 participants over four months, and its fourth-session result (the one with the most practical implications) rests on the 18 who chose to come back, nine per condition; it is real evidence of a measurable short-term pattern, not proof of irreversible cognitive decline, and the researchers themselves describe their findings as raising questions that need “deeper inquiry,” not as a settled verdict.
Skipping an unaided attempt removes that opportunity to practise the task yourself. Whether attempting first helps learning depends on the task, prior knowledge, feedback and support. The audit below keeps selected practice opportunities visible; it is not a universal claim that struggling first outperforms studying a worked solution.
The skill-preservation audit
For any recurring task, ask four questions before deciding how to use AI on it:
- Is this a skill I am actively building, or a task I just need finished? Drafting a recurring status update is a task to finish. Learning to structure a persuasive argument is a skill to build. The same tool gets used differently for each.
- What does an honest, unaided attempt look like, and can I timebox it? Choose a task-appropriate interval. Record what the attempt reveals; no fixed number of minutes guarantees a useful baseline.
- What does the assisted phase add that the unaided attempt could not? Feedback, a counterargument, a faster second draft, exposure to phrasing you wouldn’t have generated; assistance should add something specific, not just replace the labor.
- How will I check, later, that I can still do the unaided version? An independent check can reveal a gap that assisted output conceals; interpret it alongside task difficulty, time, support and previous attempts.
| Task type | Baseline (unaided attempt) | Assisted phase | Independent check | Review cadence |
|---|---|---|---|---|
| Writing a persuasive argument | Short rough outline, no tool | Ask AI to strengthen weak points and offer a counterargument | Periodically write a full argument unaided and compare with a prior attempt | Cadence chosen by learner |
| Debugging your own code | Attempt to isolate the bug before requesting hints | Ask AI to review your isolation and suggest causes you missed | Debug a comparable issue with the tool switched off | Cadence chosen by learner |
| A foreign language sentence | Write your own attempt first | Ask AI to correct and explain the correction | Hold a short unaided conversation and note new gaps | Cadence chosen by learner |
| Arithmetic for a work estimate | Do the calculation by hand | Verify with a calculator or independently checked formula | Redo a comparable estimate unaided | Cadence chosen by learner |
The full skill-preservation AI use audit gives you this table blank, with space to log your own tasks, baselines, and review dates.
Do not apply this discipline to tasks that carry real safety, legal, medical, or financial consequences by treating an unaided first attempt as good enough to act on. The audit is about preserving a skill through deliberate practice, not about avoiding verification on a task where a wrong first attempt could cause harm before you get to the assisted phase.
Where the order of operations matters most
The MIT study’s fourth-session finding (nine participants going unaided-first then assisted, on a topic they had already written about) is too small and too confounded to settle the comparison, but it points at a habit cheap enough to adopt anyway: when you are learning something new, do a rough attempt before you ask for help, even if the attempt is bad. When you already have the skill and are producing output at scale (a professional writer drafting their fiftieth similar email, a developer writing routine boilerplate), the calculus changes, but whether another unaided attempt is useful still depends on the skill and goal. Deliberate practice with AI covers the full feedback-loop workflow (attempt, rubric, feedback, retry) for turning this principle into a repeatable habit rather than a one-off resolution.
This also connects directly to delegation decisions more broadly. If you have not already, run new recurring tasks through the six-dimension check in what not to delegate to AI; the “skill” dimension there is this exact question, applied task by task rather than as a general worry.
A check you can actually compare
Invented example: before assistance, a learner explains a loop using a three-line program and misses what happens when the input is empty. They ask for one hint, revise the explanation, then later try a different program with an empty input. The record says whether the second explanation handled that case; it does not say “AI improved cognition.” Keep task difficulty, available time and any usual accommodations visible. One disappointing result is a reason to investigate, not proof of lasting decline.



