---
id: "claim-management-failure"
type: "claim"
source_timestamps: ["§ Intro", "§ Why People Create Workslop"]
tags: ["leadership", "accountability"]
related: ["concept-workslop", "contrarian-workslop-blame", "concept-fundamental-attribution-error-in-ai", "quote-management-failure"]
speakers: ["Kate Niederhoffer", "Alexi Robichaux", "Jeffrey T. Hancock"]
confidence: "high"
testable: false
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"
---
# Workslop is a management failure, not an employee failure

The authors assert that the proliferation of [[concept-workslop-d38]] is fundamentally a **management failure**, not an employee failure. It is the direct result of leaders issuing vague directives to use powerful AI tools without clear instructions, while simultaneously overburdening those employees. The environment often lacks the psychological safety required for employees to admit uncertainty or ask for help, leading them to produce low-effort AI work just to survive the pressure. This is the thesis-level claim, grounded in the [[concept-fundamental-attribution-error-in-ai]] and stated bluntly in [[quote-management-failure]]; its contrarian framing is [[contrarian-workslop-blame]].

- **Confidence:** high · **Testable:** no (an attribution / framing claim)

**Enrichment.** BetterUp/Stanford state plainly: 'The problem isn't underperforming AI, but broken incentives and unnecessary busywork that AI is exposing.' Worklytics cites 'adopting AI without guidance,' poor training, and absent AI policies as root causes. Verdict: **strongly supported** — but see [[counter-individual-skill-matters]] for the case that individual accountability is not fully absolved.