AI-generated work can look polished yet leave colleagues hours of extra decoding — what makes that failure impossible to ignore?

This explores what turns AI-assisted, low-effort work from something nobody notices into something that visibly costs the sender their colleagues' trust. The corpus points to a clear answer: using AI is not what does the damage. The damage comes when the work moves effort onto the recipient. In a BetterUp Labs and Stanford survey, more than half of desk workers admitted sending AI-generated work that looked finished but lacked substance ("workslop"). Receiving it cost colleagues about 3.4 hours a month of decoding, checking and redoing How much do desk workers actually suffer from AI workslop?. That cost is what makes it visible. About half of recipients then rated the sender as less creative, capable and reliable, 42% saw them as less trustworthy, and nearly a third were less willing to work with them again Does receiving AI-written work change how we judge the sender?.

Compare that with what happens when AI use is simply disclosed. Readers rated a news article lower when it carried an AI disclosure, but by less than 0.15 points on a 7-point scale Does disclosing AI assistance make readers trust articles less?. So the label "AI was involved" costs very little. Being handed something you then have to fix costs a lot. Trust erodes when people experience the shortfall, not when they learn which tool was used. Another study shows the same thing from the other direction: people avoid AI partners at first, but that bias reverses once they see a track record of good results Does revealing AI identity help or hurt user trust?. Outcomes shape judgment more than labels do.

This creates a paradox. Workers expect to be seen as less competent and diligent for using AI Do people fear judgment when they use AI at work?, so most of them hide it. In Anthropic's interview study, 69% of workers mentioned the stigma of using AI at work despite large time savings Why do workers hide productivity gains from AI use?. Some remove AI traces specifically to look like experts Why do knowledge workers hide signs of using GenAI?. But hiding AI use means hollow work arrives looking polished and finished. The recipient finds the gap only after starting to rely on the work, which is the moment it feels most like a betrayal. There's also a blind spot on the sender's side. The "LLM Fallacy" describes people crediting AI output to their own ability How does AI-assisted work reshape how people see their own abilities?, so senders may honestly not see their work as low-effort.

The work can also be detected without anyone confessing. Wholesale handoffs to AI leave a recognizable trace in writing and coding activity logs: concentrated bursts of output that don't match the author's normal rhythm. Genuine back-and-forth collaboration with AI leaves no such trace and looks like ordinary work Can process data distinguish AI delegation from ordinary collaboration?. That matches the trust data. What gets exposed, both in activity logs and in colleagues' opinions, is handing off the thinking, not using help.

One alternative: in shared editors, writers said they preferred being able to see each other's AI prompts. That visibility helped them follow a collaborator's reasoning and check AI-written text, though full sharing felt intrusive to some Do writers want to see each other's AI prompts in shared editors?. This suggests that showing your process early could protect trust better than hiding it and hoping the gap isn't noticed. The corpus does not directly test that idea in a workplace, so treat it as an open lead.