How WORKSLOP sneaks into even the best product teams

If you work in a product organization right now, chances are you’ve seen it.

  • A status update that sounds confident but doesn’t say anything.
  • A roadmap narrative that could belong to literally any team.
  • A document that looks finished, reads smoothly, and somehow leaves everyone asking, “So… what are we actually doing?”

That’s called “workslop.”

The term comes from a recent article in Harvard Business Review, and it captures something many teams are feeling but haven’t named yet: low-effort, AI-generated work that looks polished enough to pass along, but quietly hands the real thinking to whoever receives it.

And before anyone gets defensive, let’s be honest.  There’s a very good chance you’ve created workslop yourself.

*wince* I definitely have.

Picture this. It’s 9:47 p.m. You’ve survived back-to-back meetings, Slack is still popping, and you just realized you owe an update to leadership “before tomorrow.” You paste a few half-formed bullets into ChatGPT, ask it to “make this sound more strategic,” skim the output, think, “Yeah, that’s… fine,” and hit send.

It sounds polished.
It sounds professional.
It sounds like something a competent product leader would write.

It also contains no real signal, no clear decision, and no insight that wasn’t already vaguely implied.

Not because you’re careless.
Because you’re human.
And because the system you’re operating in is under real strain.

That’s where the problem actually starts.

Workslop isn’t really a productivity problem. It’s a trust problem.

Most conversations about AI misuse focus on wasted time. Rework. Bugs. Bad output.  Don’t get me wrong, those are real. But they’re not what hurts the most.  What workslop actually erodes is trust between people.

The HBR research describes recipients feeling confused by vague AI-generated output, frustrated by jargon-heavy updates, and undervalued when their work is recycled through AI without care or context.

In their study, 41% of employees could recall a specific instance of workslop that negatively affected their work. More than half admitted to sending it themselves.

That matters because trust isn’t a soft byproduct of product work. It’s part of the operating system.

When trust drops, teams stop sharing early thinking. People hedge instead of collaborating. Alignment slows, even as output increases.

In product organizations, trust is a leading indicator of delivery health. When it erodes, outcomes follow.

AI didn’t invent this dynamic.
It just speeds it up.

The workslop pressure cooker we’re all inside.

One of the most important points in the HBR article is also the least comfortable: workslop is not about bad people. It’s about bad conditions.

Look at the pressures converging right now.

  • AI mandates arriving faster than clarity.
  • Roles expanding without redesign.
  • Fewer people carrying more responsibility.
  • Ongoing burnout, uncertainty, and cognitive load.

In this environment, people aren’t trying to deceive anyone. They’re trying to keep up.

AI becomes a coping mechanism. A way to show progress. A way to keep things moving when there’s no space to slow down and think deeply.

The article’s data shows that 53% of respondents admitted to sending AI-generated work they knew was lower quality at least some of the time. Not because they thought it was good, but because they were stretched thin and unsure what “good” even meant anymore.

This is a system-level issue.
Leaders feel pressure from their leadership and board to “use AI.”
Teams feel pressure to deliver more with less.  Somewhere in the middle, judgment gets quietly squeezed out.

That’s how workslop emerges.

Not from carelessness. From compression.


How teams and leaders reduce workslop by changing what gets rewarded

This is where the conversation often goes sideways.  Either we moralize and assume people are being lazy, or we overcorrect and try to clamp down with stricter AI rules.

Neither works.

The teams making progress do something simpler and harder at the same time. They adjust signals, not intentions.

First, they shift from “are you using AI?” to “did this improve the decision?”  When AI usage becomes the goal, workslop is inevitable.

Instead, strong teams look for quality signals. Did this output clarify a decision? Did it surface new insight or tradeoffs? Did it reduce ambiguity for the next person?

Rule of thumb: if the recipient has to do more thinking because of the AI output, the system failed them.

Second, they make AI assistance visible and normal.

Workslop thrives when AI use is invisible and expectations are implicit.

Teams do better when they can say things like, “This was AI-assisted and still needs review,” “These conclusions are directional,” or “Here’s what’s assumed versus validated.”

This isn’t about disclosure theater. It’s about restoring shared understanding.

Research shows that trust within teams reduces workslop by more than 60 percent. Psychological safety isn’t a culture slogan here. It’s a quality control mechanism.

Third, they’re explicit about where human judgment still matters.

AI is excellent at generating options. It is terrible at owning consequences.

Teams that avoid workslop are clear about where humans stay firmly in the loop: problem framing, customer interpretation, tradeoffs under uncertainty, and decisions that affect users, revenue, or trust.

If no one can explain why an AI-generated answer is right or wrong, the problem isn’t the model. It’s the absence of a decision owner.

Finally, they treat workslop as a signal, not a failure.

Every instance of workslop is information. Context was missing. Expectations were unclear. Someone was overloaded. Incentives were misaligned.

The question isn’t “who messed up?”
It’s “what made this the easiest path?”

That’s how teams improve without burning people out or turning AI into the villain.


The takeaway.

Workslop is feedback from a system under pressure.

The organizations that will benefit most from AI won’t be the ones that mandate it hardest. They’ll be the ones that protect judgment, trust, and clarity as first-class inputs.

AI will accelerate whatever system you give it.

The real work is making sure that system supports thinking, not just output.


 Want help putting this into practice?

At Product Rebels, we work with product leaders and teams navigating exactly this shift: using AI to accelerate delivery without losing product discipline or customer trust.

Is your team experiencing challenges in implementing AI into your product operating model or struggling in establishing the practices that enable the best outcomes from AI product building?  

Schedule 30 minutes with us to learn a little bit about you and explore how we can help. 

 About Product Rebels

Product Rebels helps product leaders take their teams from good to great. We work with established product organizations that already know the basics of product management but want to operate at a higher level. Our focus is not Product Management 101. It’s helping teams build strong customer foundations and outcome-oriented ways of working that consistently translate into better results; for customers and for the business.

We partner with leaders and teams to change how product work actually happens day to day: how customer insight is gathered and shared, how problems are framed, how tradeoffs are made, and how learning compounds over time. AI is infused throughout these practices as an accelerator, helping teams synthesize learning faster, explore more options, and move with greater confidence without sacrificing judgment or customer connection.

The result is product teams that don’t just ship more, they build the right things, make better decisions under pressure, and deliver meaningful, sustained impact.


Sources and further reading

 

 

Ready To Transform Your Product Team?