A coworker answers a question. Before the sentence is even finished landing, the other person is already typing it into an AI tool to see if it checks out.
That's the whole scenario in a r/sysadmin thread that hit 867 upvotes and 348 comments this week. No regulation, no vendor, no lawsuit. Just a very ordinary, very awkward moment that turns out to be a real governance gap.
TL;DR: A r/sysadmin thread about a coworker who verified a colleague's answer with AI seconds after hearing it struck a nerve, hundreds of comments split between "that's just due diligence now" and "that's a trust problem." The actual issue: almost no small team has a written norm for this. Shadow AI policy usually governs which tools people install, not how people are allowed to use AI on each other.
Why 867 upvotes for something this small
The original post described exactly what it sounds like: someone gives a colleague an answer, and within seconds, watches them type the same question into an AI tool, visibly, to check it. Not later, not privately. Right there.
https://www.reddit.com/r/sysadmin/comments/1uisgwl/coworker_asked_ai_if_i_was_right_seconds_after/
The comment section split roughly into two camps. One argued this is just what verification looks like now, that a second opinion from a fast, available tool is no different from looking something up used to be, and that taking offense is precious. The other argued the visibility and immediacy are the actual problem: doing it silently later is fact-checking, doing it instantly and openly is a performance of doubt, and it reads that way whether or not that's the intent.
Both camps are right about different things, which is exactly why this generated 348 comments instead of being an obviously-settled question. There's a real behavior underneath the disagreement, and it happens constantly now, in Slack threads, in meetings, in code review, wherever someone can pull up a model faster than they can have a conversation.
Shadow AI policy has a blind spot
Every shadow AI policy this site has covered focuses on the same axis: what tools are employees installing without approval, what data is leaving the company through unapproved AI products, who's pasting client information into a personal ChatGPT account. That's the right axis for data risk. It has nothing to say about this.
The r/sysadmin scenario isn't a data-security question. Nobody leaked anything. It's an interpersonal-norms question that AI access created and most teams haven't caught up to: when is it appropriate to verify a colleague's claim in real time, using a tool that's available to everyone but wasn't available to everyone five years ago, and how do you do it without it functioning as a public vote of no confidence.
Small teams especially feel this because there's no HR layer to absorb it. A 200-person company can let this play out as individual friction that never surfaces. A 12-person team where everyone hears everything has a genuine culture problem waiting to happen the first time this goes wrong in front of a client or during a disagreement that already had some heat in it.
What to actually put in writing
This doesn't need a long policy. It needs three sentences that most teams currently don't have anywhere:
Verification itself is fine. Nobody should feel like checking a technical claim against a tool is an accusation. Encourage it as a normal part of quality, the same way looking something up always was.
Do it without narrating it. The friction isn't the checking, it's the visible, immediate checking in front of the person who just answered. Open a tab later, not a phone in front of them mid-sentence.
If AI turns up a real discrepancy, raise it as a question to the person, not a verdict from the tool. "I want to double check this, can we look at it together" is a different interaction than silently trusting whatever the model says over what a colleague, who has context the model doesn't, just told you.
None of this stops anyone from verifying anything. It just moves the behavior from something that reads as a trust test to something that reads as normal diligence, which is apparently the actual disagreement 348 people were having without realizing it.
Related Reading
- Shadow AI Policy for Small Teams: 2026 Detection and Governance Guide
- AI Acceptable Use Policy Template for Small Teams
- AI Governance for Small Teams: The Complete Guide
- HR AI Governance for Hiring Decisions
- AI Adoption Metrics and Perverse Incentives
Source: r/sysadmin discussion, "Co-worker asked AI if I was right seconds after asking a question" (June 29, 2026).
