At 2:53 a.m. on August 11, 2026 (Korea time), Fav (@Favwontmiss), an ordinary user account, posted a short anecdote on X. "Today I finished a PowerPoint for a company training course in 20 minutes. A male colleague in my group asked if I used Copilot. I just said, 'No, I don't use AI.' That should have been the end of the conversation." The post drew 640,000 views, 20,000 likes, 194 reposts, and 28 comments and spread quickly. As the short last sentence, "That should have been the end of the conversation," implies, the nuance that it actually didn't end seems to have drawn the resonance. But it's worth noting first that this account is a nearly anonymous individual, not an official outlet or organization, and the post is not a verified news report but one person's subjective account of an experience.
Why Did This One Line Collect 20,000 Likes?
It's reasonable to think the response was big not because this anecdote is a special event but because many people have experienced a similar scene. Being asked "did you use AI?" when you produce good work can be neutral in itself, but the context this post summoned is the asymmetry of that question. The moment work finished through skill is immediately credited to a tool, the person being asked is put in the position of having to prove their ability all over again. This is an eyewitness account rather than verifiable statistics, but together with the recent studies below, it explains why this short sentence was shared so widely.
The Asymmetry of "Suspected of Using AI," Seen in Data
Related research published in 2026 supports that this anecdote may not be mere personal coincidence. According to research by Zehra Chatoo, founder of Code For Good Now, when the same code was submitted, men who used AI got 6% lower competence scores, and women got 13% lower. In particular, male evaluators who don't use AI themselves judged female engineers 26% more harshly than male ones on the same output, and evaluators tended to presume that "AI did more of the work" when they perceived the coder as a woman. This result, summarized in Forbes's report, is context that can help in understanding why the "did you use Copilot?" question in the original post was directed at a woman author.
A Culture Where Saying You Used AI Is Itself a Loss
Seen in a broader frame, the problem isn't only women's. It also connects to trust structures across organizations. In Anthropic's survey, 69% of workers said a stigma around AI use exists at work, and 48.8% hide their AI use to avoid judgment. The share was actually higher, 53.4%, among C-level executives, who use AI the most. In a separate survey Atlassian cited, even for identical output, once evaluators learned that "AI was used," they were more likely to describe the author as lazy, and the probability of recommending them for high-difficulty work fell by 24 percentage points. The table below summarizes the three sets of results.
| Survey | Key figures | Source |
|---|---|---|
| Chatoo study (2026) | Same code, with AI use: women -13% / men -6% competence rating; male non-AI evaluators judged women 26% more harshly | Forbes |
| Anthropic survey (2026) | 69% of workers "AI stigma exists at work," 48.8% hide AI use (C-level 53.4%) | Final Round AI |
| Survey cited by Atlassian (2026) | Disclosing AI use raises "lazy" perception, lowers probability of being recommended for high-difficulty work by 24 points | Atlassian |
Layer the three surveys, and one picture emerges. Disclosing that you used AI can bring a penalty, and women carry more of that penalty. The short answer in the original post, "I don't use AI," can also be read as a defensive statement to protect one's own work under this double pressure. Of course, this causal link can't be asserted. A single post can't prove the causes and effects of those statistics, and conversely those statistics don't vouch for the authenticity of this post. But it's clear the two threads are worth reading together as circumstances that explain each other.
What Teams and Organizations Can Take Away in Practice
Studio Huuush would suggest three things to organizations from this case. First, it's worth checking the team habit of questions that automatically link the polish of an output to whether a tool was used. Curiosity like "how did you do this so fast?" is natural, but you need to ask yourself whether that curiosity is repeatedly directed only at certain members. Second, it's better to put in writing evaluation criteria under which disclosing AI use doesn't cost you. As these surveys show, a "culture of hiding" makes it hard to see an organization's real AI usage and ends up distorting tool adoption strategy itself. Third, managers need to keep reaffirming the principle that output is judged on the output itself. A collaborative culture built on trust holds only when the polish and practical fit of the work, rather than whether a tool was used, are the evaluation standard.
What This Case Doesn't Tell Us
Finally, there's a limitation to state clearly. The post that started this article is the anecdote of a single, nearly anonymous individual user, and there's no way to verify outside the original when, at which company, and what exactly was said. The colleague's intent and the surrounding context also come only through the author's telling. The three surveys cited earlier also don't cover this specific incident. They're separate studies with different samples and methodologies, so you can't equate "this post is therefore a fact proven by statistics." This article takes one personal account as an occasion to look at existing discourse and data together, and isn't meant to pass judgment on any specific person or organization.