Skip to content
Shows/Human + Machine
Human + Machine·Episode 1·Series

AI Slop Is Your Fault

Bad output is usually a bad-input problem

Jan 29, 2026·31:20·Daniel Rodriguez, Paul Maxwell

Video coming soon

No YouTube video has been added yet.

Your browser does not support the audio element.

About this episode

Paul and Daniel make an uncomfortable case: most AI slop comes from lazy prompting and missing context, not the model. They show how to take responsibility for quality and get dramatically better results.

Key ideas

  • 01Most AI slop is a context and prompting failure, not a model failure
  • 02A prompt is a specification, not a wish
  • 03Brief the model like a capable new hire
  • 04Review is non-negotiable; the model drafts, you edit

Show notes

What we covered

It's easy to blame the model when AI gives you garbage. Paul and Daniel argue the garbage is usually a mirror. This episode is about owning the input side of AI quality, from context to review, and treating the model like a capable collaborator you have to brief properly.

In this episode

  • Why most AI slop is a context and prompting failure
  • The difference between asking and actually briefing
  • Building a review habit instead of shipping first drafts
  • Prompts as specifications, not wishes
  • A quality worksheet for reviewing AI output

Links & resources

  • AI Quality Review Worksheet (downloadable)
  • Paul's context-first prompting notes
  • Daniel on treating the model like a new hire

Timestamps

Chapters

  1. —The slop is a mirror
  2. 5:20Asking vs. briefing
  3. 12:40Prompts as specifications
  4. 20:40You're still the editor
  5. 26:40Building a review habit

Quotable

“The model wrote a draft. You're still the editor.”

— Daniel Rodriguez

“If you're vague, the model fills the gaps with plausible nonsense.”

— Paul Maxwell

Full transcript

Transcript~1 min read

Show transcriptHide transcript

Paul: People show me terrible AI output and say the model is dumb. Then I look at the prompt and it's one vague sentence with zero context. That's not the model failing. That's you failing to brief it.

Daniel: Right, we'd never hand a new hire a one-line request and expect brilliance. But we do exactly that with the model and then act surprised when it guesses wrong.

Paul: A prompt is a specification. If you're vague, the model fills the gaps with plausible nonsense. If you're specific and you give it the real context, the quality jumps immediately.

Daniel: And then actually review it. Slop ships because nobody reads the output before sending it. The model wrote a draft. You're still the editor.

Mentioned

  • Claude
  • Anthropic

Related links

  • Context-first prompting

Hosts

  • DR
    Daniel Rodriguez

    Host

    RevOps Director, RevOps HQ

  • PM
    Paul Maxwell

    Host

    CEO, RevOps HQ

Topics

  • AI Tooling
  • Artificial Intelligence
  • Context Engineering

Downloads & resources

  • AI Output Quality Review WorksheetWorksheet

Subscribe to Human + Machine

  • YouTube
  • Spotify
  • Apple Podcasts

Related episodes

Human + MachineGiving AI the Context It NeedsThe gap between mediocre and remarkable AI output is almost always context. Paul and Daniel dig into context engineering: what to include, what to leave out, and how to build reusable context that pays off every session.
Human + MachineHow We Use Claude in Our WorkNo theory this time. Paul and Daniel open up their actual day-to-day: where Claude saves them hours, where they deliberately keep it out, and the habits that keep the work high quality.
Human + MachineThe Limits of Claude's HubSpot ConnectorConnectors make AI-to-CRM feel seamless, but every integration has edges. Paul and Daniel map what Claude's HubSpot connector handles gracefully and where you still need custom tooling.
Human + MachineUsing Claude with HubSpotPaul and Daniel walk through concrete ways they use Claude alongside HubSpot, from drafting to analysis to cleanup, and the context pack that makes the results reliable instead of hit or miss.