Publié le — Un commentaire

Who Should Govern AI at Universities? Faculty Rights, Human Oversight, and Academic Work

University faculty members discussing AI governance and academic policy at a meeting

As of 11 October 2026, negotiations at several universities show that the debate over artificial intelligence in higher education is expanding beyond classroom use. The emerging question is who gets to shape the rules when AI affects academic work, employment decisions, privacy, and institutional accountability.

This is not evidence of a single global consensus. The cases discussed here are specific, ongoing negotiations in Australia and Canada, and the parties involved disagree about both the substance of AI safeguards and where those safeguards should be written.

Why AI governance is becoming a workplace issue

Universities increasingly have to make decisions about where AI tools may be used, what information may be entered into them, whether AI contributes to decisions about employees, and how human responsibility is preserved. These questions overlap with teaching and research, but they also concern employment conditions and institutional governance.

Three recent cases illustrate different parts of this debate: negotiations at the University of Melbourne, bargaining between York University and CUPE 3903 in Canada, and the University of Sydney’s stated preference for adaptable policies and frameworks.

1. University of Melbourne: a proposed AI clause, not a settled agreement

In its 8 October bargaining update, the National Tertiary Education Union (NTEU) reported that it had tabled a principles-based AI clause and that the University of Melbourne was engaging with it. The union said it was not seeking to ban AI; it wanted basic protections as AI was already being used. The university acknowledged that AI needed to be addressed in some form, while continuing to develop its position.

The discussion became more specific around disclosure. According to the NTEU’s account, the university was concerned that the draft could require disclosure of AI use in too many decisions. The union clarified that its intended focus was human-resources decisions affecting staff across the employment cycle, including recruitment, major workplace change, promotion, discipline, and performance. The parties were still working on wording on 8 October.

What this means: the question is not simply whether AI is allowed. It is whether staff should be told when AI materially contributes to consequential employment decisions, and how a disclosure rule can be clear without becoming unworkably broad. Because the update is from the union, it should be read as the union’s account of negotiations—not as a jointly agreed summary or a final contract.

2. York University: a joint working group with a recommendatory role

At York University in Canada, CUPE 3903—which represents teaching assistants, contract faculty, graduate and research assistants, and other workers—reported on 4 October that AI had been a major subject in collective bargaining. The union’s bargaining team report says the employer proposed replacing an ad hoc AI committee with a Joint Working Group on the Use of AI in the Workplace.

According to CUPE 3903, the group’s role would be to make recommendations, not implement changes directly, and its work would be deferred until well into the next collective agreement. The union’s report argues that meaningful safeguards should address consent, accountability, information security, academic freedom, and the role of human labour in teaching and research. Those are the union’s stated priorities; they should not be mistaken for agreed university policy.

York’s own labour-relations updates confirm that bargaining has been underway and that the parties have been pursuing conciliation. The university’s public account provides useful context, while the union report offers detail about its interpretation of the AI discussions. Reading both helps distinguish the existence of a negotiation from either side’s preferred outcome.

What this means: creating a working group can bring expertise and consultation into the process, but its practical influence depends on its mandate, timing, access to information, and what decision-makers must do with its recommendations. A committee is not equivalent to a binding safeguard.

3. University of Sydney: policies may be more adaptable than a three-year agreement

The University of Sydney has articulated a different emphasis. In its 2 September statement on industrial action, the university said it supported a human-centred approach to ethical AI and argued that AI should be governed through policies and frameworks that can be updated as technology changes, rather than placing all such rules in an enterprise agreement covering a three-year term.

This is the university’s stated position, not proof that policy-based governance is always more effective. Policies can be revised more readily, which may help institutions respond to fast-changing tools. But their practical strength depends on transparency, consultation, enforcement, and whether staff and students have meaningful ways to challenge decisions. Conversely, putting a principle into a collective agreement may give it a more formal status, but drafting broad language can be difficult and can create questions about scope and implementation.

Policy or collective agreement? The real issue is enforceability

These cases should not be reduced to a simple contest between innovation and resistance. They reveal a governance design problem: how can institutions preserve room to adapt while ensuring that AI use is transparent, proportionate, and accountable?

  • Define high-impact uses. Institutions should distinguish low-stakes support—such as brainstorming—from AI that materially informs hiring, promotion, discipline, performance evaluation, grading, or other consequential decisions.
  • Require meaningful human responsibility. Where an AI system informs a consequential decision, a named human decision-maker should be able to scrutinise its contribution, explain the decision, and correct errors. Human oversight should not be a rubber stamp.
  • Make disclosure specific. Clear rules should identify when AI use must be disclosed, to whom, and what information is needed. Requiring disclosure for every minor use can create noise; providing no disclosure for high-impact use can undermine trust.
  • Protect data and intellectual work. Rules should address confidential student and staff information, research materials, intellectual property, and the limits of uploading sensitive content to third-party systems.
  • Give people a route to challenge outcomes. Students and employees need an accessible process to question an AI-assisted decision and request meaningful human review.
  • Review rules on a schedule. Because systems and practices change, policies and agreements should include consultation, monitoring, and review mechanisms rather than assuming that a single document will answer every future question.

These are recommendations for institutional design, not a claim that any one university has already adopted all of them.

What educators and university leaders should watch next

The important evidence will be the text and implementation of any final agreements or policies—not headlines suggesting that a university has “settled” the AI question. Readers should look for precise definitions of covered AI uses, the scope of disclosure, the role of human decision-makers, data-protection responsibilities, consultation requirements, and review or appeal mechanisms.

For education leaders, the lesson is practical: AI governance should not be treated only as a question of student rules or classroom integrity. It also concerns the conditions under which teaching, research, and institutional decisions are carried out. For faculty and students, the key test is whether the rules create understandable responsibilities and meaningful avenues for accountability.

Conclusion

The current discussions at Melbourne and York, alongside Sydney’s publicly stated approach, show different institutional choices still being debated. They do not establish a settled international trend, and the negotiations may change. They do, however, offer a useful way to examine the central governance question: who sets the limits, who is informed when AI is used, and who remains accountable for the outcome?

Universities do not need to choose between adaptability and safeguards as if only one were possible. The stronger approach is to make the rules transparent, define high-impact uses clearly, preserve meaningful human responsibility, and create processes that can be reviewed as the technology and its educational consequences evolve.

Sources and further reading

Editorial note: This article reflects publicly available information reviewed as of 11 October 2026. The Melbourne and York bargaining accounts include statements from the union parties; proposals and negotiating positions are not final agreements. Readers should consult later official updates for changes after this date.

Publié le — Laisser un commentaire

Is Prompt Engineering Still a Skill Worth Learning?

In March 2024, IEEE Spectrum ran a headline that still gets cited today: ‘AI Prompt Engineering Is Dead.’ It was based on real research, not speculation. VMware and Intel Labs researchers systematically tested hand-crafted prompts against automatically generated ones and found the automated prompts won. Two years later, the debate that headline started is still unresolved, and the honest answer is more useful than either side of it.

The research behind the original claim

The IEEE Spectrum piece, by Dina Genkina, reported on work by Rick Battle and Teja Gollapudi testing prompt engineering strategies on grade-school math problems. Their systematic finding: prompts generated automatically by another AI model consistently outperformed prompts carefully hand-crafted by humans, including some of the specific wording tricks prompt-engineering guides recommended at the time. That is a real, testable result, not an opinion, and it undercut one specific claim: that hand-tuned wording is where the skill’s value lives.

What replaced it in industry conversation: context engineering

Through 2025, a new term gained traction among AI practitioners, popularized in part by researcher Andrej Karpathy: context engineering, the practice of deciding what information, documents, examples, and tool access a model has available, rather than focusing narrowly on how a single instruction is phrased. Gartner reportedly advised enterprise AI leaders to shift investment accordingly, and Shopify CEO Tobi Lutke publicly said he preferred the term context engineering to describe what skilled AI practitioners actually do day to day. The shift in terminology reflects a shift in where practitioners say the leverage is: not the clever phrase, but what the model can see and use.

A second, separate technical finding worth knowing

Chroma Research’s Context Rot study adds a distinct finding: model performance measurably degrades as input length grows, even well within a model’s advertised context window. This matters for the same reason the VMware finding does. It suggests skill is shifting away from wordsmithing a single prompt and toward managing what and how much you feed a model at once, a different and more structural kind of judgment call.

The debate is real, not settled

It would be inaccurate to present this as resolved. Microsoft’s 31,000-person, 31-country workforce survey reportedly ranked Prompt Engineer near the bottom of new roles companies planned to add over the next 12 to 18 months, which suggests the narrow version of the skill has limited durable demand as a job title. But public commentary continues in both directions: Forbes contributor Bernard Marr argued in January 2026 that prompt engineering is no longer the most valuable skill, while fellow Forbes contributor Dan Fitzpatrick published a direct rebuttal in June 2026 titled Prompt Engineering Is Not Dead. Sam Altman also predicted back in 2022 that prompt engineering would not still be a discipline in five years, a prediction whose timeline is now close to being tested. We present this spread deliberately: the technical evidence points one direction, informed opinion remains split.

What this means for teaching and training: our judgment

This section is our interpretation, not a settled fact. The narrow version of prompt engineering, memorizing specific magic phrases or formatting tricks, looks weaker as something to teach as a standalone skill; the VMware research and the Microsoft survey both point that way. What still looks durable, and worth building into any AI literacy curriculum, is the broader judgment underneath it: understanding what information a model needs to do a task well, recognizing when an answer is weak because the model lacked context rather than because the task is impossible, and iterating deliberately instead of hoping a clever wording will fix an underspecified request. That is closer to what context engineering describes, and it connects to the evaluation habits in our framework for evaluating an AI tool and to what AI literacy actually means as a durable competency rather than a tool-specific skill.

Key takeaways

  • Real 2024 research from VMware and Intel Labs found automatically generated prompts outperformed hand-crafted ones, undercutting the narrow, wording-focused version of prompt engineering.
  • Industry conversation has shifted toward context engineering: managing what information and tools a model can access, not just how an instruction is phrased.
  • Chroma’s Context Rot study separately found performance degrades with input length even inside the advertised context window.
  • Public commentary remains split, even as a Microsoft workforce survey reportedly found limited demand for prompt engineer as a job title.
  • Our judgment: teach the underlying skill of judging what a model needs to succeed, not memorized wording tricks.

Sources: Genkina, D., IEEE Spectrum (March 2024), reporting on Battle, R. and Gollapudi, T. (VMware/Intel Labs); Chroma Research, Context Rot study; Microsoft workforce survey; Forbes (Bernard Marr, January 2026; Dan Fitzpatrick, June 2026). Attributions to industry figures reflect public statements as reported and should be verified against the original sources.

Publié le — Un commentaire

Why Computer Science Enrollment Is Falling in the AI Era

Abstract bar chart illustration in cobalt blue representing declining enrollment

Enrollment in computer and information science programs at U.S. four-year universities dropped 8.1% in the 2025-2026 school year, the steepest decline of any field of study, with computer science specifically down 11.2%, according to National Student Clearinghouse data reported by Built In. For a field that spent over a decade as the default “safe” major, that is a striking reversal, and it is not happening for one simple reason.

The entry-level fear, specific to this field

Roughly 30% of code at major tech companies is now AI-generated, and AI tools now handle boilerplate code and basic debugging faster than most junior developers. This connects directly to the broader pattern we covered in the entry-level jobs fear: students are not imagining the shrinking junior-developer market, a Computing Research Association survey of 130 universities found 62% of participating institutions already reporting employer concern about this shift. What is specific to computer science is that the discipline’s own entry point, writing basic code, is the exact task AI has gotten disproportionately good at first.

“Cognitive surrender”: a term from MIT itself

In August 2026, an MIT faculty committee reported that its own students reach for AI at the first hint of struggle, and named the pattern cognitive surrender. This is not an outside critique of student behavior, it is one of the world’s leading technical institutions naming a problem in its own classrooms. The concern is specific: computer science, more than most fields, is learned by struggling through a bug or a broken proof, and that struggle is precisely what a fast, capable AI assistant removes if a student reaches for it too early.

What the newest international data shows

The OECD’s PISA 2025 results, released in September 2026, put a number on this. Across OECD countries, 46% of 15-year-olds use AI chatbots at least weekly for schoolwork. But students who used AI for specific tasks like summarizing or drafting scored roughly 20 points lower on science assessments than students who did not, a gap roughly equivalent to a full year of schooling. This is population-scale evidence, not an anecdote from one classroom, and it lands specifically on science and technical literacy, the exact domain STEM students are trying to build.

Why this isn’t simply “don’t use AI”

Learning science has described this mechanism for decades under the term desirable difficulties: retrieval practice, spaced repetition, and unresolved struggle are not obstacles to learning, they are the process itself. The OECD’s own 2026 review of classroom data across 14 countries reaches the same conclusion, echoing the pattern we found in our own piece on AI and critical thinking: the damage isn’t from AI use in general, it’s from using it to skip the specific struggle a skill is built on. For a CS student, that means the honest question isn’t “should I use AI,” it’s “which parts of this problem am I letting AI solve before I’ve actually tried.”

Key takeaways

  • U.S. computer science enrollment fell 11.2% in 2025-2026, the steepest drop of any major, driven largely by fear of a shrinking entry-level developer market.
  • MIT’s own 2026 faculty committee named a real pattern in its classrooms, “cognitive surrender”, reaching for AI before attempting a problem independently.
  • OECD PISA 2025 data found weekly-AI-use students scoring roughly 20 points lower on science assessments, about a year of schooling, than non-users.
  • The evidence points to a specific mechanism, skipped struggle, not AI use in general, which is a solvable, structural problem, not a reason to avoid the field.

Sources: National Student Clearinghouse data via Built In (2026); MIT faculty committee report, August 2026, via University 365; OECD PISA 2025 results (released September 2026); Computing Research Association employer survey, 2026.

Publié le — Laisser un commentaire

Multimodal AI Explained (Without the Jargon)

Abstract illustration in cobalt blue representing overlapping AI modalities

A multimodal AI model can look at a photo of a whiteboard, understand a diagram on it, write code that implements what the diagram shows, and explain that code back to you in plain language, all in one conversation. By 2026, this kind of cross-modal understanding has become the standard for frontier AI models, not a special feature. For teaching and training, the practical shift is simple: you can now hand a model a document, an image, or a recording directly, instead of manually converting everything to text first.

What “multimodal” actually means

A single-modality AI model handles one kind of input and output, usually text: you type a question, it types back an answer. A multimodal model processes and connects several types of content, text, images, audio, and increasingly video, within one system. The key technical difference is integration: the model doesn’t just run a separate image tool and a separate text tool side by side, it reasons across them together, which is what lets it explain how a diagram and a paragraph of text relate to each other, not just describe each one in isolation.

What this actually enables for teaching and training

  • Document understanding. Upload a scanned worksheet, a handwritten problem set, or a slide deck directly, no separate OCR or transcription step required first.
  • Diagram and image feedback. A student can photograph a hand-drawn diagram, chart, or lab setup and get feedback on the content itself, not just a text description of what’s in the photo.
  • Voice-based interaction. Natural, real-time voice conversation with an AI assistant, useful for language practice or for learners who process speech more easily than text.
  • Recorded lecture and meeting analysis. Audio or video of a class session or training module can be processed directly for summarization or Q&A, connecting to the practical comparison in our AI writing assistants piece, since several tools in that space now combine transcription with multimodal understanding rather than offering transcription alone.

What it does not solve

Multimodal capability is an input and output improvement, not a reasoning or accuracy improvement on its own. A model that can now read a photograph of a math problem is not automatically more reliable at solving that problem correctly than it was before; the underlying accuracy and hallucination risks discussed in our piece on AI and critical thinking apply just as much to multimodal output as to text-only output. Treat a multimodal tool’s confidence about what it “sees” in an image with the same verification habit you’d apply to anything else it generates.

A practical way to think about it

The useful question isn’t “is this tool multimodal” by 2026, most capable tools are. The useful question is which specific modality combination actually matches your task: text-plus-image for marking handwritten work, text-plus-audio for transcribing and summarizing a session, or text-plus-document for working directly with PDFs and slides instead of retyping their content. Matching the modality to the task, rather than defaulting to typing everything out as plain text, is where the actual time savings come from.

Key takeaways

  • Multimodal AI integrates text, image, audio, and video understanding within one model, rather than chaining separate single-purpose tools together.
  • By 2026 this is the baseline for frontier models, not a differentiator between them.
  • Practical education and training uses include document understanding, diagram feedback, voice interaction, and recorded-session analysis.
  • Multimodal capability improves what a model can take as input, not its underlying accuracy, so the same verification habits still apply.

Based on a synthesis of 2026 technical overviews of multimodal AI systems and their applications; specific model capabilities change frequently and are best verified directly with each vendor.

Publié le — 2 commentaires

AI Agents, Explained for People Who Teach and Train

Abstract network diagram in cobalt blue representing AI agents

An AI agent is software that can take a goal, break it into steps, and carry those steps out on its own, searching, writing, checking its own work, and adjusting, rather than just answering one prompt at a time the way a chatbot does. For teachers and trainers, that distinction matters more than the terminology suggests: it is the difference between a tool you have to operate at every step, and one you can hand a task to and check on later. This article explains what actually separates a chatbot, an AI assistant, and an AI agent, what that difference looks like in a classroom or training program, and where human oversight still genuinely matters.

Chatbot, assistant, or agent: what is actually different

These three terms get used almost interchangeably in casual conversation, but they describe genuinely different levels of autonomy. The clearest way to separate them is by what happens between your instruction and the finished result.

TypeWhat it doesWhat you still have to do
ChatbotAnswers one message at a time; no memory of taking action, only of the conversationRe-prompt for every step; assemble the pieces yourself
AI assistantCarries context across a task, can use a tool or two (search, a document), but generally completes one bounded action per requestDirect each major step; review each output before moving on
AI agentPlans a multi-step sequence, uses several tools, checks its own output against a goal, and revises without being re-prompted at each stageSet the goal and constraints up front; review the finished result before it reaches anyone else

The practical marker of an agent is not intelligence, it is persistence: it keeps working toward a goal across multiple steps without you re-engaging at each one. A chatbot that drafts one paragraph when asked is not an agent. A tool that takes “build a two-week unit plan on this topic, aligned to these three learning objectives,” researches the topic, drafts the sequence, checks it against the objectives you gave it, and revises the weak parts on its own, is functioning as an agent, regardless of what the vendor calls it.

Anthropic’s 2026 State of AI Agents report, based on real usage data rather than survey opinion, found that agents have moved from experimental novelty to production infrastructure inside organizations: over 57 percent of surveyed organizations are now running multi-step agent workflows, not just single-action assistants. The report also found that model capability is no longer the main bottleneck to adoption; integration with existing systems is, cited by 46 percent of organizations as their top challenge. That second point is the one worth sitting with: the hard part of using agents well is not the AI, it is fitting the workflow around it.

What this actually looks like in a classroom or training program

Strip away the enterprise framing, and the practical version for education and training looks like this:

  • Research and drafting agents that can be given a topic and a set of constraints (grade level, learning objectives, length) and return a structured first draft of a lesson plan or training module, not a single paragraph you then have to assemble yourself. A trainer building a compliance module, for instance, could set the required topics and pass criteria, and let the agent draft the sequence, checking its own draft against the pass criteria before handing it over.
  • Multi-step feedback tools that check a piece of student or trainee writing against a rubric, flag specific issues, and draft suggested comments, then wait for a human to approve before anything goes back to the learner. The agent behavior here is the multi-pass checking: reading the rubric, checking the draft against each criterion, and only then producing comments, rather than a single generic pass.
  • Administrative agents that can be pointed at a messy task, such as reformatting a slide deck, compiling attendance data, or drafting a parent or manager email from bullet notes, and asked to complete it end-to-end.

None of this requires a technical background to use. It does require a workflow decision: what are you comfortable handing over completely, and what needs a human checkpoint before it reaches a student or employee? That question is worth answering deliberately, not by default; see our framework for evaluating an AI tool before adopting one for exactly this reason.

What agents actually change, and what they do not

What changes: the amount of multi-step work you can delegate without babysitting every stage. A lesson-planning agent does not just draft a paragraph when asked, it can research the topic, structure the plan, check it against a rubric you provide, and revise itself, then hand you something closer to a finished draft. That is a genuinely different capability from last year’s single-turn AI tools.

What does not change: judgment. An agent can execute a plan; it cannot tell you whether the plan serves your actual students or trainees, whether the tone is right for your specific group, or whether a shortcut it took quietly undermined the learning goal. This is the same caution that applies to generative AI in education generally; see our piece on what the research says about AI and critical thinking. Handing a multi-step task to an agent does not remove the need for a human to check the outcome; if anything, because agents complete more steps unsupervised, the final check matters more, not less.

Current limitations worth knowing before you rely on one

Agents fail differently than chatbots do, and it is worth understanding how before you hand one a real task. A chatbot that misunderstands a prompt produces one visibly wrong answer you catch immediately. An agent that misunderstands a goal can complete several plausible-looking steps built on that misunderstanding before anyone notices, because each individual step looks reasonable in isolation, it is the cumulative direction that is wrong. This is sometimes called compounding error, and it is the main practical risk of increased autonomy.

Agents also still depend heavily on how clearly a goal and its constraints are specified. Anthropic’s own reporting on integration being the top adoption barrier, ahead of raw capability, reflects this: an agent given a vague goal will confidently fill the gaps with its own assumptions, which may not match yours. And because an agent can use multiple tools and take multiple actions, the surface area for something to go wrong, a wrong data source, an outdated reference, a misapplied rule, is larger than with a single-turn tool.

None of this is an argument against using agent-based tools. It is an argument for treating the final review as a required step, not an optional one, and for being explicit and specific about goals and constraints rather than assuming the agent will infer what you actually meant.

If you are in a corporate learning and development role weighing whether agent-based tools are worth adopting yet, that decision connects directly to a broader pattern we cover in the AI adoption gap in L&D: enthusiasm for AI in L&D is high, but structured, trained, checkpoint-driven adoption is still rare, and that gap is exactly where agent-based tools can go wrong if adopted without a workflow to match.

Key takeaways

  • The functional difference between a chatbot, an assistant, and an agent is persistence across multiple steps without re-prompting, not raw intelligence.
  • The practical uses in education and training are drafting, feedback-checking, and admin work, not replacing instructional judgment.
  • Agents fail through compounding error, several plausible steps built on one wrong assumption, which is why the final human check matters more with agents, not less.
  • Integration into an existing workflow is the actual adoption bottleneck, not the technology itself.

For another current shift worth understanding alongside agents, see multimodal AI explained.

Source: Anthropic, 2026 State of AI Agents Report.

Publié le — 7 commentaires

Does AI Really Hurt Critical Thinking? What the Research Shows

Abstract layered arcs in cobalt blue representing cognitive processes

The honest answer is: it depends what you offload, and what happens to the thinking time that gets freed up. A growing body of research from 2025 and 2026 links heavy AI use to weaker independent thinking, but the more recent and more careful studies are converging on a sharper point: the danger is not AI use itself, it is AI use with no structure for what stays human. Getting this right requires separating several concepts that casual discussion of this topic tends to blur together.

Six terms that are not interchangeable

TermWhat it actually means
Cognitive offloadingUsing an external aid to reduce mental demand, a neutral mechanism, the same one behind a grocery list or a calculator
DelegationA deliberate choice about which specific task to hand over, made consciously rather than by default
LearningBuilding durable skill or understanding you can access without the external aid present
Independent reasoningThe capacity to work through a problem unaided, which is what atrophies if the wrong tasks are chronically offloaded
MetacognitionAwareness of your own thinking process, including noticing when you are offloading and whether that is appropriate
VerificationActively checking an AI’s output rather than accepting it, the specific behavior most research finds declining with heavy trust in AI

Most of the public debate about “AI and critical thinking” is really only about two of these six: whether offloading is happening, and whether learning suffers as a result. The more useful and more evidence-backed version of the question involves all six, especially metacognition and verification, which is where the research below actually locates the risk.

What the evidence actually shows

A 2025 study published in the journal Societies (Gerlich, 2025) surveyed and interviewed 666 people across age groups and education levels, and found a significant negative correlation between frequent AI tool use and critical thinking scores, with cognitive offloading as the mechanism connecting the two. Younger participants showed the strongest effect.

A separate 2025 MIT study (Kosmyna et al.) used EEG to measure brain activity while participants wrote essays using ChatGPT, a search engine, or no tool. The ChatGPT group showed the weakest neural engagement while writing, and when later asked to write without any AI assistance, showed reduced brain connectivity and struggled to recall their own earlier work, a pattern the researchers termed cognitive debt.

A third study, from Microsoft and Carnegie Mellon researchers presented at CHI 2025 (Lee et al.), surveyed 319 knowledge workers about 936 real AI use cases and found that the more a person trusted the AI’s output, the less critical thinking, meaning verification, in the framework above, they reported applying to it, while trusting their own judgment correlated with more thinking, at a higher mental cost. This study is the clearest evidence that the actual mechanism at risk is verification specifically, not reasoning capacity in general.

Important caveat: correlation, not proof

None of this evidence establishes that AI use causes declining critical thinking in a strict sense. The Gerlich study is explicitly correlational: it is equally possible that people who already think less analytically reach for AI assistance more often, or that a third factor, such as time pressure, drives both patterns at once. The MIT EEG study, while methodologically distinctive, involved a small sample (54 participants) and measured a specific task, essay writing, that may not generalize to every kind of AI-assisted work. These findings are a real and statistically significant signal worth taking seriously, not a settled verdict that AI use damages cognition across the board.

Where the research moved next: not all offloading is equal

This is the part most coverage of this topic misses. Cognitive offloading itself is not new or inherently harmful, as the table above makes explicit, it is the same mechanism behind writing a grocery list. It becomes a problem specifically when it offloads work that would otherwise build or maintain a skill you need, in other words, when delegation happens without metacognitive awareness of what is being given up. A March 2026 synthesis from the University of Technology Sydney frames the real question as what happens to the freed-up mental effort, not whether offloading happens at all.

A concrete intervention study supports this distinction directly. 240 university students learning English essay writing were split into two groups over 12 weeks. One group was explicitly taught to delegate lower-order tasks to AI, such as brainstorming, grammar checking, and initial co-revision, while deliberately keeping higher-order work, analysis, evaluation, and reflection, for themselves. The other group received standard instruction. The group with the explicit offloading structure showed significantly greater critical thinking gains, not smaller ones. The intervention did not restrict AI use; it made the boundary between what to hand over and what to protect explicit, which is precisely the metacognitive step the correlational studies above found generally missing.

What educators and learners can practically do

Translating this research into practice comes down to making two things explicit that usually happen invisibly:

  • Name the boundary before the task starts. Decide in advance which parts of an assignment or project are meant to be AI-assisted (brainstorming, formatting, first-pass grammar) and which parts must stay unaided (the actual analysis, the argument, the final judgment), rather than letting the boundary drift by default.
  • Build in a verification step deliberately. Since the CHI 2025 findings point specifically to verification declining with trust, not general reasoning, the most targeted fix is requiring a check step, asking a student or trainee to identify what they would need to confirm before accepting an AI-generated answer, rather than banning AI use outright.
  • Treat the freed-up time as the actual variable. The UTS synthesis and the 12-week intervention both point the same direction: offloading is beneficial when the time it frees up gets redirected to higher-order thinking, and harmful when it is simply time saved with nothing redirected. That redirection has to be designed in, it does not happen automatically.

This is the same structural principle the OECD’s 2026 education research points to independently; we cover that in more detail in our analysis of the OECD’s 2026 report. It also directly informs how to think about AI agents, which by design take on more multi-step work with less human involvement at each stage; the more a tool offloads, the more deliberate the boundary and the verification step both need to be.

Key takeaways

  • Multiple 2025-2026 studies link heavy, unstructured AI use to weaker independent thinking; the evidence is real but correlational, not proof of causation.
  • The specific mechanism most consistently affected is verification, checking AI output, not reasoning capacity in general.
  • Cognitive offloading itself is not the problem; it becomes one when it offloads a skill you still need, without metacognitive awareness of that trade-off.
  • A 12-week intervention study found that explicitly defining what to delegate and what to protect produced greater critical thinking gains, not smaller ones.
  • The practical takeaway is structure, not restriction: name the boundary, build in verification, and make sure freed-up time gets redirected somewhere.

Sources: Gerlich, M. (2025), Societies, 15(1), 6; Kosmyna et al. (2025), MIT Media Lab; Lee et al. (2025), presented at CHI 2025; University of Technology Sydney synthesis (March 2026).