How to Explain AI-Assisted Work to a Boss Who Doesn’t Trust It

Two things carry the sentence: the specific check you ran, and where your manager can see it. Everything else, including which AI tool you used, is optional. Say it in that order, and a skeptical manager gets the one proof they’re listening for, instead of a vague reassurance that you ‘reviewed’ it.

What should you say first?

Say the specific check you ran and where your manager can see it, before you say anything else about the tool you used. Skip the brand name unless someone asks. Slack’s Workforce Lab found in its Fall 2024 Workforce Index that 48 percent of desk workers would be uncomfortable telling their manager they used AI on a task, which means most people default to silence instead of a structured answer. Silence is what makes a manager suspicious later. Try this: “I used AI for the first pass of the competitor summary and checked every number against the source filings myself; my markup is in the shared doc.” That sentence gives a skeptical manager the one thing they want to know: a human looked at this before it reached them.

Why does ‘I used AI’ backfire?

“I used AI” backfires on its own because people distrust a machine’s mistakes more than they distrust a human’s, even when the machine is right more often overall. Wharton researchers Berkeley Dietvorst, Joseph Simmons and Cade Massey found in 2015 that once someone watches an algorithm make an error, their confidence in it drops faster and further than their confidence in a human forecaster who makes the identical error, a pattern they named algorithm aversion and later explored in a 2018 Management Science follow-up. That same wariness shows up at work, not just in lab studies: Slack’s research on how employees feel about AI describes it as a social-context problem, not just a productivity one. Announcing the tool without announcing your check reads as “trust the machine,” and the research says most people won’t, no matter how good the output turned out to be. Lead with your check instead, and the tool becomes a footnote.

Five questions to expect, ranked by frequency

Managers who are wary of AI tend to ask the same five follow-up questions, roughly in the order they come up during project reviews. Prepare answers before you bring up AI at all, since exposure to AI at work is now broad enough, per Pew Research Center’s 2025 mapping of which workers use AI, that most managers have already seen these questions asked of someone else on their team.

1. What did you personally check? Name the specific step: recalculated the totals, called the source, reread every citation.
2. Where did the AI’s information come from? Name the source documents or data you fed it, not just “the internet.”
3. What would have happened if you hadn’t caught a mistake? Answer honestly about the stakes; a low-stakes internal draft needs a lighter answer than a client-facing document.
4. Did you use this on the parts that need judgment, or just the mechanical parts? This tracks the “jagged frontier” finding from Harvard Business School’s 2023 field study of 758 BCG consultants, later published in Organization Science: AI improved quality on tasks inside its competence and hurt quality on tasks outside it.
5. Could you have done this without it? The honest answer is often yes, more slowly; say so.

Should you name the AI tool?

Naming the AI tool by brand doesn’t build credibility on its own, and can invite more scrutiny than it resolves. Microsoft and LinkedIn’s 2024 Work Trend Index found 78 percent of AI users bring their own tools to work rather than company-approved software, and a companion release of the same report put overall AI use among knowledge workers at 75 percent, so most managers now assume some AI touched the work whether you name the brand or not. The same index found 52 percent of AI users are reluctant to admit using it on their most important tasks, and 53 percent worry it makes them look replaceable. Those numbers describe fear of the disclosure itself, not evidence that disclosure damages careers. A manager’s read changes on the specific check you can point to, not on the tool’s name. Save the brand for when someone asks a follow-up question about process.

Does disclosure hurt your reputation?

Disclosure alone rarely damages your reputation. Reputation slips when disclosure arrives without any evidence of checking behind it. Pew Research Center’s April 2023 survey found most Americans are uneasy about employers using AI to monitor or evaluate workers, and a related Pew 2023 survey found 66 percent would not want to apply for a job at a company that used AI to help make hiring decisions. Both describe discomfort with AI making decisions about people, a different question from whether a person disclosing their own AI use looks bad. A February 2025 Pew survey found U.S. workers are more worried than hopeful about AI’s future role at work, so caution is the prevailing mood. Walking into that caution with a specific verification story, rather than a vague admission, is what keeps the conversation short.

What if AI got something wrong?

If AI got something wrong, say what you caught and what you changed in your process, before your manager has to ask. The clearest lesson on the cost of skipping this step comes from law, not office work: in Mata v. Avianca, a New York federal court sanctioned two lawyers and their firm $5,000 in 2023 after they filed a brief citing court cases that ChatGPT had invented and that neither lawyer had checked against a legal database. Their error was filing the output unverified, then defending the fake citations once a judge asked for copies of the cases. Frameworks like NIST’s AI Risk Management Framework put the same idea in formal terms: human review of AI output is a control step, not an optional extra. Bring a mistake to your manager before they find it, describe the fix you put in place, such as a citation-by-citation check or a second reviewer, and treat it as a process update, not a confession.

What’s the exact sentence to use?

Use a version of this: “I checked [specific verification] before this went out, and here’s where you can see it: [document or link].” Mention which AI tool did the drafting only if someone asks about process or tooling. Fill in specific details every time; a template with no details reads as evasive. If your workplace has a written no-AI or restricted-AI policy, change the sentence: name the policy, confirm what you did against it, and if you’re unsure whether a step crossed a line, ask before you ship rather than after. Slack’s Fall 2024 research found nearly half of workers stay quiet about AI use specifically to avoid this conversation, but the conversation gets easier every time you have it with evidence in hand, and harder every time a manager finds out on their own.

You are a workplace communication coach helping me prepare a short, specific script to tell my manager I used AI on a piece of work. Before you write anything, ask me: (1) what the task was, (2) exactly what AI did versus what I did, (3) what I personally checked or verified, and (4) where the evidence of that check lives (a doc, a diff, a comment thread). Once I answer, write exactly two to three sentences I can say out loud or paste in a message: one naming my specific check, one pointing to where the evidence lives, and only mention the AI step if it adds context. Do not use the tool's brand name unless I tell you my manager already knows or asks about tooling. Keep the tone plain and confident, not apologetic, and avoid hedging words like 'I think' or 'probably'.

You are a skeptical senior reviewer for [type of deliverable, e.g. a market analysis memo, a code change, a client email]. Before answering, ask me what AI was used for in this deliverable and what format it's in. Then generate a numbered checklist of everything a careful human should manually verify before this goes out, specific to this type of work, for example: source citations, calculations, named facts about specific people or companies, dates, and anything that could be defamatory or legally binding if wrong. For each checklist item, note whether it needs a second person to check it or whether I can verify it alone. Do not include generic advice like 'proofread carefully'; every item should be specific enough that I could tick it off.

Roleplay as my manager, who is skeptical of AI-generated work and has been burned before by a report that turned out to have unverified information in it. I'll describe a piece of work I did with AI assistance. Ask me the follow-up questions a genuinely skeptical manager would ask, one at a time, waiting for my answer before asking the next. Push back if my answer is vague. After five questions, tell me plainly which of my answers were strong and which ones would still worry a careful manager, and why.