---
type: "synthesis"
tags: ["workslop", "term-migration", "output-quality"]
articles: ["a038", "a042", "a079"]
id: "cross-workslop-genealogy"
sources: ["adoption"]
sourceVaultSlug: "hbr-seg-adoption"
originDay: 9
articleStem: "hbr-seg-adoption"
sourceUrl: "(unified vault: 11 sources)"
sourceTitle: "HBR — People Ⅲ-A · Adoption / trust / literacy / psych-safety"
---
"Workslop" is the corpus's signature traveling term — it appears in three articles with subtly evolving meaning, a rare chance to watch a concept mature across an author community.

- **A038 (Niederhoffer/Robichaux/Hancock)** is the term's home base: [[concept-workslop-d38]] — polished-looking, low-substance AI output that offloads cognitive burden onto the recipient. Crucially framed as a **management failure, not laziness** ([[claim-management-failure]]), produced by [[concept-performative-ai-use]] under vague mandates. It has a social-media cousin in [[lit-ai-slop]].
- **A042 (Zaki)** *coins/attributes* it (see [[quote-workslop-d9]]) and casts it as a **symptom of unaddressed FOBO** — a defensive productivity theater in low-trust, zero-sum rollouts.
- **A079 (Seth/Edmondson)** narrows it to a **relational/team-dynamics toxin**: [[concept-workslop-d79]] is AI output that fails to advance the project and dumps rework and *emotional labor* onto colleagues, corroding interpersonal trust.

The throughline: all three treat workslop as a *relational externality* and a downstream *symptom* of a systemic condition (overload, fear, or low trust) rather than an individual defect. The divergence: A038 blames vague mandates, A042 blames unempathetic leadership, A079 blames the black box's disruption of sense-making. Read together, workslop is the corpus's clearest evidence that AI *exposes* pre-existing organizational strain (see counterpoint [[counter-ai-exposes-not-causes]]).