In short: When AI helps make a decision at work, responsibility can blur between the tool, the reviewer and the team, and blurred responsibility lowers attention and quality. Every significant decision should have one named owner, while leaders own the conditions those decisions are made in.
Somewhere right now, a team is shipping a recommendation that a model helped write. A manager is approving a budget built from an AI-generated forecast. An analyst is sending a client a summary of research they skimmed and a tool condensed. Most of the time, nothing goes wrong. But when something does, a new and uncomfortable question shows up in the meeting afterward: who actually made this call?
In "The Convenient Fear" I argued that AI companies benefit from a story in which the technology, not the people who built it, carries the risk. The same move happens inside organizations, at a smaller scale and with lower stakes, every day. It's worth naming, because it quietly erodes something organizations depend on.
How Does AI Blur Responsibility?
Organizations have always had ways to diffuse blame. Committees. Consultants. "The data said." "Legal signed off." Each one spreads responsibility thin enough that nobody has to hold much of it.
AI is a powerful new addition to that list, because it's always available and it sounds authoritative. "The model flagged it." "The analysis recommended it." "That's what the tool came back with." Each phrase puts a little distance between a person and a choice. None of them is quite a lie. All of them are a way of saying "not entirely me."
The danger isn't one bad decision. It's a culture where nobody fully owns anything, because there's always a system in the loop to share the weight.
Why Does Decision Ownership Matter?
Ownership isn't about blame. It's about attention.
When a person knows a decision is theirs, they look harder. They ask the extra question. They check the number that feels off. They sleep on it. That care is the real quality control in most organizations, far more than any formal review process.
When responsibility gets blurry, attention drops. If the model wrote it and my manager approved it and the client signed it, I can be a little less careful, because I'm only one of four. Multiply that by everyone involved and you get decisions that everyone touched and nobody examined.
Researchers have a name for part of this: automation bias, the tendency to over-trust a recommendation because a system produced it. It has been studied for decades in aviation and medicine, where trained professionals sometimes follow an automated suggestion even when their own information points elsewhere. The more fluent and confident the system sounds, the stronger the pull. Language models are the most fluent and confident systems most people have ever worked with.
What Are the Warning Signs?
The rubber stamp. A person reviews AI output but doesn't really engage with it. They skim, it looks reasonable, they approve. Formally, a human was in the loop. Practically, nobody was.
The laundered recommendation. Someone has a preference, asks a model to analyze the options, and the model, which tends to agree with the framing it's given, produces analysis that supports the preference. Now a personal opinion carries the weight of an objective analysis.
The orphaned error. Something goes wrong, and when the team traces it back, every step points somewhere else. The prompt was fine. The output looked fine. The review was standard. The mistake belongs to no one, so nobody learns from it.
How Do You Make Ownership Clear?
Every decision has a name on it. Not a team, not a tool. One person who will answer for it. They can use any help they want. The decision is still theirs.
Review means engaging, not glancing. If someone signs off on AI-assisted work, they should be able to explain it without looking at the screen. If they can't, they haven't reviewed it.
Say how AI was used. A simple note on significant work: what the tool did, what the person did, what was checked. It takes a minute, and it makes the line of responsibility visible.
Separate advice from decision. The model can advise. People decide. Writing that down sounds obvious, but naming it changes how people talk about outcomes. "I decided, based partly on the analysis" is a different sentence from "the analysis decided."
Treat errors as learning, not blame. If owning a decision means being punished for every mistake, people will hide behind the tool. Ownership only works in a culture where admitting a bad call is safer than disguising it.
Isn't This Just Finding Someone to Blame?
There's a risk in all of this. "Every decision has a name on it" can turn into finding someone to blame when a system fails. Some failures really are shared: a rushed timeline, an unclear process, a tool rolled out without training. Pinning those on the last person to touch the work teaches everyone to hide.
So ownership runs in two directions. Individuals own their decisions. Leaders own the conditions those decisions get made in: the time people have, the rules for review, the tools they're given and whether it's safe to say "I'm not sure this is right." If the conditions make careful ownership impossible, that's a leadership failure, not an individual one.
The Sentence That Matters
There's a test I use on myself. When something I worked on goes wrong, can I say "that was my call" without adding a qualifier? Not "the model suggested" or "the data showed" or "we all agreed." Just: my call.
If I can say it, I owned the decision. If I can't, I let something else make it for me and kept my name on it anyway.
AI can make us faster, sharper and better informed. It can't hold responsibility, because responsibility only means something when it belongs to someone who can be held to it. The tools are getting better every month. The obligation to own what we do with them hasn't changed at all.
Frequently Asked Questions
Who is responsible for an AI-assisted decision? The person who made it. AI can inform a decision, but it can't be accountable for one. Every significant decision should have one named owner.
What is automation bias? The tendency to over-trust a recommendation because a system produced it, even when other information points elsewhere. It has been studied for decades in aviation and medicine.
What does a real human review of AI output look like? The reviewer can explain the work without looking at the screen, has checked the facts that matter and has engaged with the reasoning, not just skimmed the result.
What do leaders own in AI-assisted work? The conditions: time to review, clear rules, proper training and a culture where admitting uncertainty is safe.
Evan Prout is a strategist in Grand Rapids, Michigan, who writes about how organizations think and decide with AI.
- Raja Parasuraman and Dietrich Manzey, "Complacency and Bias in Human Use of Automation," Human Factors 52 (2010).