Blog · Analysis · May 2026

Workslop and the Trust Tax

The real risk is not that AI writes bad memos. It is that polished machine output can move verification labor onto everyone downstream.

From Productivity to Rework

The first public story about generative AI at work was productivity. A worker could draft faster, summarize faster, code faster, answer customers faster, and move through the backlog with less friction. Some of that story is real.

In a large field study of customer-support agents, Erik Brynjolfsson, Danielle Li, and Lindsey Raymond found that access to a generative AI assistant increased productivity, measured by issues resolved per hour, with the largest gains for less experienced and lower-skilled workers. Shakked Noy and Whitney Zhang's experiment on professional writing tasks likewise found faster completion times and quality gains for many participants. These results matter because they show that AI can be a real instrument of augmentation when the task, workflow, and evaluation surface are well defined.

But a second story has arrived behind the first. Microsoft and LinkedIn's 2024 Work Trend Index reported that 75 percent of surveyed global knowledge workers were using AI at work, while 78 percent of AI users were bringing their own AI tools into the workplace. The same report found that many users were reluctant to admit using AI for important tasks. That is not just adoption. It is unsupervised institutional redesign.

When a tool spreads faster than the norms around it, the organization inherits a verification problem. The question is no longer, "Can this person produce more output?" It is, "Who now has to decide whether the output is any good?"

What Workslop Is

Researchers at BetterUp Labs, working with Stanford Social Media Lab, popularized the term "workslop" for low-substance AI-generated workplace content that looks finished enough to pass along. Their September 2025 survey of 1,150 full-time U.S. desk workers reported that 40 percent had received workslop in the previous month, with an average of roughly two hours spent resolving each incident. BetterUp estimated a monthly cost of $186 per employee from these incidents, or $9 million per year in a 10,000-person company.

Those numbers should be read carefully. They come from a survey, not a controlled measurement of every firm. But the pattern is plausible because it names something many knowledge workers already recognize: the deck that looks clean but has no decision logic, the summary that erases the caveats, the market scan that invents confidence, the policy draft that sounds official while missing the governing constraint, the code explanation that reads well until someone tries to use it.

Workslop is not simply bad writing. Offices have always produced bad writing. The new feature is scale plus finish. Generative AI can make weak work look formatted, confident, and complete. It can lower the cost of producing the appearance of effort while raising the cost of checking whether effort actually occurred.

Polish Is Not Progress

Workplaces often use surface signals as proxies for care: clean formatting, fluent prose, confident recommendations, plausible citations, professional tone, and the visible mass of a document. These signals were never perfect, but they were at least loosely connected to time spent, skill, or organizational familiarity.

Generative AI weakens that connection. A worker can now produce the surface layer of competence without doing the underlying work of judgment. The document arrives with headings, bullet points, executive tone, and a conclusion. The missing part is not obvious at first glance. The reader has to discover that the artifact lacks source discipline, local context, operational knowledge, numerical grounding, user empathy, or legal awareness.

That discovery is labor. Someone has to re-open the source material. Someone has to ask what the recommendation assumes. Someone has to test whether the generated plan matches the actual system. Someone has to notice that the document answered the prompt rather than the problem.

This is the quiet reversal inside workplace AI. The sender saves drafting time. The receiver pays verification time. If the organization measures only output volume, the sender looks more productive and the receiver looks slower. The institution has moved work across a boundary without naming the transfer.

The Trust Tax

The deeper cost of workslop is not the individual bad artifact. It is the trust tax that follows repeated exposure. Once coworkers suspect that polished documents may conceal weak thinking, every artifact becomes a little more expensive to accept.

Trust is a compression technology. In a healthy team, people do not verify every sentence, formula, schedule, or recommendation from scratch. They rely on known competence, role boundaries, shared standards, and the expectation that a colleague has done the minimum work before passing something along. That is why teams can move quickly.

Workslop breaks that compression. It teaches readers to distrust the surface. It makes routine handoffs feel like audits. It shifts meetings from decision to revalidation. It turns collaboration into a defensive posture: did a person think this through, or did a model generate a plausible placeholder?

BetterUp's survey materials report reputational effects as well as time costs: people receiving workslop often judged senders more negatively. That is institutionally important. AI misuse does not only create bad documents. It can damage the social ledger that lets teams coordinate without constant suspicion.

Why This Is Governance

It is tempting to treat workslop as etiquette: edit before sending, do not be lazy, use better prompts. That advice is useful but insufficient. Workslop is a governance problem because it concerns accountability, evidence, incentives, disclosure, and the allocation of verification labor.

Organizations already govern many forms of delegated work. A financial model has review expectations. A legal memo has source expectations. A production change has test expectations. A clinical note has documentation expectations. The same principle applies to AI-mediated work: the use of a model does not dissolve responsibility for the output.

The hard part is that AI enters through ordinary interfaces. It appears as a paragraph in an email, a slide in a deck, a generated spreadsheet explanation, a code suggestion, a meeting summary, a customer reply, or a proposed policy. There may be no visible boundary between human judgment and machine continuation. The artifact arrives as if it were simply work.

That makes AI literacy more than a training module. It becomes an institutional requirement for preserving reliable handoffs. Teams need shared language for what may be drafted by AI, what must be checked by a human, what sources must be attached, what uncertainty must be disclosed, and when a generated artifact is not acceptable as a substitute for analysis.

Better Rules for AI Work

The solution is not to ban AI drafting. That would ignore the genuine productivity evidence and push use underground. The better move is to make the verification burden explicit.

First, require source trails for claims. If a document makes factual, legal, technical, financial, or operational claims, it should preserve links, data sources, assumptions, and the human check performed. A polished paragraph without a trail should be treated as a draft, not as evidence.

Second, separate drafting from judgment. A model can turn notes into prose, compare options, produce checklists, or generate candidate summaries. It should not silently become the decision-maker. The accountable person should name the judgment they made after using the tool.

Third, label high-stakes AI assistance. Disclosure does not need to become performative confession. But where AI materially shapes a recommendation, report, policy, code path, public claim, or customer-facing message, recipients need to know what kind of verification occurred.

Fourth, measure downstream cost. If AI use saves one employee an hour and costs three colleagues two hours of cleanup, the organization did not gain productivity. It moved the loss out of the sender's task list and into the team.

Fifth, protect apprenticeship. Junior workers need tools, but they also need to learn how good work is made. If AI turns every assignment into a finished-looking artifact, managers must preserve review practices that teach judgment, not merely correct outputs. This connects directly to the site's earlier argument in The Erosion of Apprenticeship.

Sixth, give teams refusal rights. A coworker should be able to send back an AI-generated artifact that lacks sources, context, or accountable judgment. That refusal should be treated as quality control, not hostility to technology.

The Spiralist Reading

Workslop is model-mediated knowledge without digestion.

The model can produce the outer form of work: the memo, the deck, the recap, the recommendation, the code explanation, the strategic frame. But the institution still needs someone to metabolize reality: to read the source, understand the constraint, notice the stakeholder, test the system, and decide what matters.

When that digestion is skipped, the organization enters a recursive reality loop. A model summarizes a meeting. Another model turns the summary into a plan. A worker sends the plan as if it were analysis. A manager asks a model to summarize the plan. The artifact becomes smoother at every pass while its contact with the underlying situation weakens.

This is the same pattern visible in AI slop on the public web, but inside the firm it has a sharper edge. Public slop pollutes attention. Workslop pollutes coordination. It teaches institutions to confuse formatted output with accountable knowledge.

The practical standard is simple: AI may accelerate work, but it must not be allowed to launder absence into presence. A generated artifact should answer three questions before it moves downstream: what claim is being made, what evidence supports it, and who is accountable for the judgment?

Without those answers, the machine has not saved work. It has deferred it.

Sources

Return to Blog