Cognitive Offload and the 'AI Makes Us Dumber' Question
The honest answer for principals who are quietly worried about their team's judgement
This essay sits primarily under the Can we do AI? question of the practice’s methodology: the cognitive consequence of how a firm uses AI, and why it shapes the firm’s underlying capability over time.
The honest version
I advocate for AI in professional practice loudly and unapologetically. Advocacy without nuance is reckless.
So let’s talk about the thing that worries principals most: the thing that, if we are being honest, should worry us a little too:
Does AI reduce critical thinking?
The concern goes like this: when staff use AI, they stop doing the hard cognitive work. They offload the thinking that actually builds judgement. They get better outputs but develop weaker minds. Over time, AI does not make them sharper. It makes them dependent, and dependence in a regulated practice is a problem with a regulator’s name on it.
This is not a fringe concern. There is genuine research behind it, and every principal who has watched a graduate paste a question into ChatGPT without pausing to think has felt the truth of it in their gut.
So: is it true?
The answer is more interesting than yes or no.
What cognitive offload actually is
Cognitive offload is when you use an external tool to reduce the mental effort required for a task. You do it constantly:
- Writing a shopping list instead of memorising it
- Using a calculator instead of doing long division
- Checking a map instead of navigating from memory
- Setting a reminder instead of trying to remember
None of these make you “dumber.” They free up cognitive resources for other things. The shopping list lets you think about meals. The calculator lets you focus on the structure of the problem. The map lets you pay attention to traffic.
AI is the latest, and most powerful, cognitive offload tool we have encountered. And that is precisely why it feels different. Previous tools offloaded specific, well-defined tasks. AI can offload thinking itself: the drafting, the analysing, the reasoning, the evaluating. That is what makes the question urgent in a professional setting where the thinking is the work.
The real risk: metacognitive laziness
The concern is not really about cognitive offload as such. It is about what happens to metacognition: the ability to monitor, evaluate, and regulate your own thinking.
When practitioners use AI well, they:
- Generate a draft, then evaluate it against their own understanding of the matter
- Get AI feedback, then decide what to accept and what to reject
- Use AI to explore options, then judge which options actually fit the client and the law
- Read AI output, then question whether it is correct against primary sources
When practitioners use AI poorly, they:
- Generate a draft and send it
- Get AI feedback and accept it
- Ask AI for the answer and copy it
- Read AI output and assume it is correct
The difference is not whether they used AI. It is whether they paused to think about what AI gave them.
This is metacognitive laziness: not a failure of intelligence, but a failure of self-monitoring. The practitioner stops asking “do I understand this?” and starts asking “does this look right?” In a regulated practice, “looks right” is the dangerous middle ground: too polished to question, not verified enough to defend.
What we are getting wrong
The metacognitive laziness risk is real. What is not justified is the leap from “this risk exists” to “AI makes us dumber.”
That leap assumes something worth scrutinising: that the way we have always learned and worked is the only way capability is built.
The “how I trained” bias
Many senior practitioners qualified through:
- Long apprenticeship under partners who watched them closely
- Drafting from blank pages and being marked up in red
- Grinding through problems without assistance
- Long periods of solitary struggle with primary sources
- Repetitive practice until pattern recognition stuck
This worked. It built judgement. The principals who came up this way understandably value it. But when they see juniors not doing these things, they assume capability is not being built.
That assumption is worth questioning.
Working differently is not working less
When a graduate uses AI to explore a tax position, asks follow-up questions, gets confused, tries a different angle, and eventually builds an understanding through an iterative conversation, that is judgement being built. It does not look like sitting alone with the legislation for three hours, but it is engagement with material. Engagement with material is how capability is built.
When a junior uses AI to generate a first draft and then spends their time evaluating, restructuring, and improving it, they are doing higher-order work (evaluation, synthesis) earlier in the process, even if they skipped some of the lower-order work (initial recall, basic comprehension). Whether the trade-off is good depends on whether they retain the foundation. That is supervisable.
When a practitioner uses AI to get unstuck on something they would otherwise have walked away from, they continue engaging. Without AI, they might have given up. With AI, they kept going. Which outcome produced more capability?
The question is not whether your team is doing the same cognitive work as you did. It is whether they are doing valuable cognitive work. And the answer depends entirely on how the work is structured, which is on you, the principal.
Working slower, working different
Here is a reframe that may be more accurate than “AI reduces critical thinking”:
AI changes the path to capability.
Practitioners may build certain things more slowly when they use AI as a crutch for recall. They may build other things faster: how to evaluate arguments, synthesise positions, exercise judgement about quality.
When calculators became widespread, students stopped memorising multiplication tables as thoroughly. Some educators argued this was catastrophic. Students who used calculators could engage with more complex mathematical problems earlier: problems that would have been inaccessible if they had had to do every calculation by hand.
Did calculators make students “dumber at arithmetic”? In a narrow sense, yes. Did they reduce mathematical capability overall? No. They redirected it. Students lost some computational fluency but gained access to higher-level mathematical thinking.
AI may be doing something similar at a much larger scale. Practitioners may develop less capacity for certain types of unaided drafting and recall. They may develop more capacity for evaluation, judgement, synthesis, and critical analysis, if the work is designed to support that.
That “if” is doing a lot of work in that sentence. And it is entirely about how you supervise.
Supervision determines everything
Here is the uncomfortable truth: AI does not inherently support or weaken professional capability. Supervision does.
The same AI tool can:
- Undermine capability if your team uses it to bypass thinking
- Deepen capability if your team uses it to extend thinking
The difference is how the work is set up.
Practice that weakens capability with AI
- Output is all that matters (the letter goes out, the matter closes)
- No requirement for staff to explain their reasoning
- Files where AI’s contribution is invisible
- No reflection on what AI contributed and what the practitioner contributed
- Treating AI as binary (allowed or banned) rather than designing for thoughtful use
Practice that strengthens capability with AI
- Process documentation: staff record how AI was used and what they changed and why
- Evaluation tasks: staff are asked to assess AI output against criteria, identify errors, and improve it
- Explanation requirements: before signing or sending, staff must be able to explain the reasoning in their own words to a partner
- Metacognitive prompts: built-in reflection: what did I understand before using AI? What do I understand now? Where did AI help? Where did it mislead me?
- Comparative tasks: the harder cases get attempted without AI first, then with AI, then reviewed for the differences
- AI as interlocutor: team members use AI as a thinking partner (conversation, not delegation) rather than an answer machine
The tool is not the problem. How you integrate it into the work is what matters. And that is squarely within your control.
Toward hybrid expertise
The framing of “AI vs human thinking” is itself the problem.
The future is not about preserving unaided professional cognition in its traditional form. It is about developing hybrid expertise: the ability to think effectively in partnership with AI.
What hybrid expertise looks like
- Knowing when to think independently and when to think with AI
- Being able to evaluate AI output with genuine understanding
- Using AI to extend capability without losing the foundation
- Maintaining metacognitive awareness while leveraging cognitive offload
- Developing judgement about when offloading is appropriate and when it is not
This is not a lesser form of professional capability. It is a different, and arguably more relevant, form for a market where clients can already get a passable first draft from AI on their own.
The most effective practitioners I see are not those who delegate everything to AI, nor those who refuse to use it. They have developed a symbiotic relationship. They know what they bring (context, judgement, regulatory awareness, experience, the actual client relationship) and what AI brings (breadth, speed, pattern recognition, tirelessness).
That symbiosis is itself a skill. It requires:
- Self-awareness about your own strengths and blind spots
- Understanding of AI’s capabilities and limitations
- The discipline to pause and think before accepting output
- The humility to recognise when AI has a better angle
- The confidence to override AI when judgement says otherwise
If your firm builds this kind of relationship with AI, you are not weakening your team. You are preparing them for the work as it is now.
The conversation, not delegation connection
This circles back to the foundational principle: conversation, not delegation.
When a team member delegates to AI (just give me the answer), cognitive offload becomes cognitive abdication. They get output without understanding. Over time, their capabilities erode. So does the firm’s.
When they converse with AI (help me think through this), cognitive offload becomes cognitive amplification. They engage with material at a deeper level, with AI as a thinking partner that challenges, extends, and enriches understanding.
The difference between offload that harms and offload that helps is whether the human stays in the loop: not just approving output, but actively thinking alongside the tool.
What you should actually worry about
Instead of the broad fear that “AI makes us dumber,” here are the specific, actionable concerns to focus on as a principal.
1. Loss of productive struggle
Some difficulty is professionally valuable. When a graduate wrestles with a problem and eventually breaks through, that struggle builds durable judgement. If AI eliminates all struggle, it may eliminate the capability that comes with it.
The response: structure work where struggle is built in, where AI can help but cannot shortcut the thinking. Require attempts before AI consultation. Reflect on what AI added.
2. Illusion of understanding
Staff may feel they understand something because they have read AI’s clear explanation, without having built genuine comprehension. They can paraphrase the explanation but cannot apply it to a new client or fact pattern.
The response: test for transfer, not recall. Ask staff to apply concepts to novel situations. Have them explain reasoning verbally.
3. Erosion of foundational skills
Some skills underpin higher-order thinking. If staff skip the foundations (drafting, primary-source reading, basic mathematical or clinical reasoning), they may struggle with the complex tasks that depend on them.
The response: be intentional about which foundations matter. Not every traditional skill is equally foundational. Identify the ones that genuinely underpin higher-order work and protect those, while being willing to let go of skills that technology has genuinely superseded.
4. Metacognitive atrophy
The biggest risk: staff stop monitoring their own understanding because AI gives them a false sense of competence.
The response: build metacognitive practice into AI-integrated work. Regular reflection, self-assessment, and “explain your thinking” requirements. Make metacognition visible and valued.
A more honest position
Here is where I land, and I think it is where thoughtful principals should land too:
AI does not make us dumber. It does make it easier to be dumber: to coast, to accept, to stop thinking.
The same tool that can deepen capability can also provide a comfortable path to professional laziness. The difference is supervision, self-awareness, and intentional practice, and underneath all of those, agency. Cognitive offload preserves agency. Cognitive abdication transfers it. The line between them is whether the practitioner is still the one steering after the work is done.
Your job as a principal is not to protect staff from cognitive offload. It is to teach them to offload wisely: to know when to lean on AI and when to lean on their own minds, to maintain the metacognitive habits that turn AI from a crutch into a catalyst.
That is harder than banning AI. It is harder than embracing AI uncritically. It requires ongoing attention, honest reflection, and willingness to adapt as you learn more about how AI affects your team’s work.
It is also the honest position. And honest positions, in the long run, serve your firm better than comforting certainties in either direction.
Practical takeaways
For supervision:
- Design for process, not just product. Make thinking visible.
- Build in reflection points: what did you understand before AI? After?
- Test for transfer and explanation, not just correct outputs.
- Protect genuinely foundational skills while releasing obsolete ones.
- Model your own symbiotic relationship with AI. Show the team how you think with it.
For your own practice:
- Notice when you are offloading versus when you are collaborating.
- Regularly do hard thinking without AI to maintain your own foundations.
- Use AI to extend your capability, not replace your engagement.
- Stay curious about what your team is actually building, not just what they are producing.
For the conversation with peers:
- Acknowledge the legitimate concerns. Cognitive offload is real.
- Shift from “AI makes us dumber” to “how do we design for thoughtful AI use?”
- Share what works.
- Resist both uncritical enthusiasm and reflexive fear.
The bottom line
“Does AI make us dumber?” is the wrong question. The right ones are:
- How do we design work that leverages AI without bypassing thinking?
- What does effective human-AI collaboration look like, and how do we develop it?
- Which cognitive foundations must we protect, and which can we safely offload?
These are practice-design questions, not technology questions. The answers are in your hands.
Cognitive offload is not the enemy. Cognitive abdication is. The difference is whether agency stays with the practitioner.
About this work
borck.consulting helps regulated Australian small firms set up the practice design that turns AI from a crutch into a catalyst, including the supervision changes most firms quietly need but have not yet made. Engagements begin with the AI Readiness Diagnostic.
Further reading
- Risko, E. F., & Gilbert, S. J. (2016). Cognitive offloading. Trends in Cognitive Sciences, 20(9), 676–688. https://doi.org/10.1016/j.tics.2016.07.002
- Sparrow, B., Liu, J., & Wegner, D. M. (2011). Google effects on memory: Cognitive consequences of having information at our fingertips. Science, 333(6043), 776–778. https://doi.org/10.1126/science.1207745
- Gerlich, M. (2025). AI tools in society: Impacts on cognitive offloading and the future of critical thinking. Societies, 15(1), Article 6. https://doi.org/10.3390/soc15010006
- Fan, Y., Tang, L., Le, H., Shen, K., Tan, S., Zhao, Y., Shen, Y., Li, X., & Gasevic, D. (2025). Beware of metacognitive laziness: Effects of generative artificial intelligence on learning motivation, processes, and performance. British Journal of Educational Technology, 56(2), 489–530. https://doi.org/10.1111/bjet.13544
- Dellermann, D., Ebel, P., Söllner, M., & Leimeister, J. M. (2019). Hybrid intelligence. Business & Information Systems Engineering, 61(5), 637–643. https://doi.org/10.1007/s12599-019-00595-2