The Hidden Causes of AI Workslop—and How to Fix Them

What It Covers

Stanford professor Jeff Hancock and BetterUp chief scientist Kate Niederhofer examine "AI workslop" — low-effort, AI-generated workplace content that appears to fulfill tasks but doesn't. Research across organizations reveals structural causes, measurable financial costs, and specific leadership strategies to build cultures where AI genuinely enhances productivity.

Key Questions Answered

• •Workslop Prevalence: In surveys, 53% of respondents admitted sending AI-generated work they considered sloppy — and because social desirability bias typically suppresses self-reported bad behavior, researchers treat this figure as an undercount. The scale suggests workslop is a systemic organizational condition, not isolated individual laziness.
• •Financial Cost Calculation: Each workslop incident costs recipients roughly two hours to detect, evaluate, and resolve. For a 10,000-person company, researchers calculated this translates to approximately $9 million annually in lost productivity — a direct financial drain from the same AI tools organizations purchased to reduce costs and improve efficiency.
• •Root Cause — Dual Mandate Problem: Workslop spikes when organizations combine two conditions: broad AI-use mandates ("you must use AI") with increased workload expectations ("AI means you can do more"). Leaders should replace general mandates with team-level AI workflow redesign, where teams collaboratively determine how AI fits their specific tasks and processes.
• •Pilot Mindset Training: Organizations reducing workslop pair AI literacy training with mindset development — specifically building high agency and high optimism toward AI tools. Researchers call this the "pilot mindset," where workers take ownership of AI outputs, actively edit content, and apply their own voice rather than passively accepting generated results.
• •Psychological Safety as Workslop Reducer: Teams with high trust and constructive feedback cultures produce measurably less workslop. When team members feel safe receiving critique, they invest more in output quality. Managers should respond to workslop with compassion first — asking what pressures are driving shortcuts — then build regular constructive feedback as standard team practice.