What are the key takeaways from this HBR IdeaCast episode?

Key insights include: **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.

What did Jeff Hancock and Kate Niederhofer discuss on HBR IdeaCast?

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 topics include: **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..

How long is this episode of HBR IdeaCast?

This episode is 28 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

HBR IdeaCast

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

March 10, 2026

28 min episode · 2 min read

Jeff Hancock,Kate Niederhofer

Episode

28 min

Read time

2 min

Topics

Career Growth, Productivity, Leadership

AI-Generated Summary

Published Mar 12, 2026

Key Takeaways

✓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.

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.

Notable Moment

Researchers proposed a new organizational role called an AI Collaboration Architect — someone fluent in both human collaboration dynamics and AI capabilities, tasked with embedding AI into specific workflows to solve defined problems rather than deploying tools broadly and hoping productivity follows.

Know someone who'd find this useful?

Episode Transcript

By 2030, finance could harness hindsight, insight, and foresight to elevate your function from necessary cost center to value creator. Explore Deloitte's future of finance publication to shape your team's impact. Visit deloitte.com/us/futureoffinance. A new digital reading experience from Harvard Business Review is here. It's the HBR interactive issue. Swipe through pages, search each issue, and listen to articles with audio narration. The interactive issue is available now to all HBR Print Magazine subscribers. Not yet a subscriber to the HBR Print Magazine? Subscribe today at h b r dot org slash interactive issue. I'm Allison Beard. And I'm Adi Ignatius, and this is the HBR Ideacast. Artificial intelligence promise to make us faster, smarter, and more productive at work. So why does it sometimes feel like it's doing the opposite? If you're trying to figure out how to use AI without undermining your culture, collaboration, or credibility, this episode is for you. Today, we'll explore why AI Stop. Stop. Stop. Stop. Allison, did you even write this? Good catch, Adi. No. Our producer, Mary, and I decided to give it to ChatGPT. And that's not because we were busy with other stuff that we were, but it was to try to prove the point of today's episode. That the rise of AI has also meant the rise of what our guests call AI work slop. And that is bad product that kind of passes, but actually actually creates a lot more problems than it solves. So I know who you're talking about and your guests have written a couple of articles for us on AI Workslop. They've been among the most popular things we've published in the past year. Workslop is a problem. AI is achieving a lot for us, but it is also creating content that is problematic. Exactly. And this issue is resonating. The coinage of the term work slop has really taken off. But one of the key points that we'll dive into is the idea that this isn't just laziness. There are structural pressures causing workers to use AI to create junk. Two co authors of those articles you mentioned are Jeff Hancock, a professor of communication at Stanford, and Kate Niederhofer, chief scientist at BetterUp. And they're gonna explain how this trend hurts teams and organizations and outline the changes that leaders have to make to ensure our AI use is working for us, not against us. Here's our conversation. That was really you. Right? Yes, Adi. So let's start with the basics. How do you two define work slop? I really like the definition we started with, which is it looks like it does the work, but actually doesn't advance the task. And, actually, even more, I like the word masquerade that we use to define it. So it's sort of like, masquerade captures that looks good, but actually isn't what it says it is. I think the most important part about the definition is that it is interpersonal, and it shifts the …

Get the full transcript (5,008 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all HBR IdeaCast transcripts →