---
id: "contrarian-workslop-blame"
type: "contrarian-insight"
source_timestamps: ["§ Intro", "§ Why People Create Workslop"]
tags: ["contrarian-insight", "management-theory", "blame-culture"]
related: ["claim-management-failure", "concept-fundamental-attribution-error-in-ai", "counter-individual-skill-matters"]
speakers: ["Kate Niederhoffer", "Alexi Robichaux", "Jeffrey T. Hancock"]
challenges: "The assumption that poor AI outputs are the result of individual employee laziness or incompetence."
sources: ["adoption"]
sourceVaultSlug: "hbr-seg-adoption"
originDay: 9
articleStem: "hbr-edu-38-ai-workslop"
sourceUrl: "https://hbr.org/2026/01/why-people-create-ai-workslop-and-how-to-stop-it"
sourceTitle: "Why People Create AI “Workslop”—and How to Stop It"
---
# Contrarian: Workslop Is Caused by Bad Management, Not Lazy Employees

**Conventional view:** receiving low-effort, AI-generated work means the sender is lazy, incompetent, or untrustworthy.

**The authors' challenge:** workslop is a *rational* employee response to being overworked, psychologically depleted, and forced to comply with vague, top-down AI mandates. This directly challenges the assumption that poor AI outputs stem from individual laziness. It is the reframe that powers [[claim-management-failure]] and rests on the [[concept-fundamental-attribution-error-in-ai]].

**Challenges:** the assumption that poor AI outputs are the result of individual employee laziness or incompetence.

**Counter-counter view (hold both):** [[counter-individual-skill-matters]] argues individual craft and professional standards still matter even under bad mandates — workslop may be *both* systemic and an individual-skill issue.