Skip to Content
ReferenceAbout ClaudeWatch Out for Workslop

Watch Out for Workslop

Workslop — the act of passing AI output directly to colleagues or clients without reviewing it.

A term coined by Jason Fried, CEO of 37signals, in 2025. “Work” + “slop” = careless dumping of AI output that degrades work quality.

Why It Matters

  • 95% of organizations can’t measure the ROI of their AI investments (Gartner, 2025)
  • Copy-pasting AI output forces the recipient to review and fix it
  • “It made my job easier” often means the team’s total workload increased

Common Patterns

What you’re doingWhat’s actually happening
Sending AI-written emails as-isRecipients sense something is off, trust erodes
Sharing AI meeting notes without reviewWrong decisions get recorded as facts
Submitting AI reports via copy-pasteYour manager has to review and fix everything
Committing AI code without checkingReviewers catch all the quality issues

The common thread: your effort decreased, but the team’s total effort increased.

Passenger vs Pilot

People who use AI output as-is are Passengers. People who review and refine are Pilots.

Passenger:  Ask AI → Copy output → Send
Pilot:      Ask AI → Review → Request changes → Re-review → Send

Passengers seem faster, but they steal time from the recipient. Pilots take a bit longer, but improve the team’s overall productivity.

How to Prevent Workslop

1. Always review AI output before sharing

This is the most important rule. When you receive output:

  • Fact-check: Are numbers, dates, and names correct?
  • Tone-check: Is it appropriate for the audience and context?
  • Completeness-check: Is anything missing? Is anything unnecessary?

2. “AI wrote it” is not an excuse

Whether AI generated it or you wrote it yourself, you’re responsible for what you send. There’s no scenario where you can blame “the AI.”

3. Prompt quality = output quality

Vague instructions produce vague results. The more specific context, purpose, and constraints you provide, the less review you’ll need.

4. Use Claude Code’s confirmation cycle

Claude Code asks for confirmation before actions. This confirmation IS the Pilot moment.

  • Before sending a Slack message → “Does this look good?”
  • Before creating a calendar event → “Should I create this?”
  • Before registering a task → “Register these tasks?”

Take 3 seconds to think before pressing “y”. That alone prevents workslop.

References

Last updated on
TipsEnvironment Basics