Bloated, off, or wrong. Chris Heuer and Marius Ciortea build a working test for AI slop, then go looking for its edges: the deep expert who cannot write in English, the member who prompts an AI to make him look good, and the community manager who wants a bot to answer every question. What is at stake is trust.

TC Chapter

00:00 Cold open: human slop, and why we're talking about it

00:25 Welcome

01:37 The pilot correction

02:18 Preferring AI answers, not trusting them

02:35 What's at stake is trust

03:19 What is AI slop? Too long to find the useful part

04:07 Bloated, off, or wrong, and the easy button

05:08 Can AI writing not be slop?

05:16 Code is poetry; slop is in the eye of the beholder

06:39 The Druckenmiller op-ed: written by AI

08:55 The PR-firm defense

09:17 Your personal intelligence system

12:22 Where AI writing helps a community: the expert who can't write

14:04 Where it breaks: "make me look good"

14:42 Low effort, low quality, and intent: the LinkedIn problem

16:10 Communities self-police

17:51 "I failed English": provenance, process, intent

19:17 The verification loop

20:44 The evidence under the answer

21:43 Show your work

22:05 The 15-minute conversation was the prompt

22:50 The 8,000-word wall of text

~23:40 Where is AI actually best deployed in a community?

24:00 Sponsor MidRoll - Higher Logic

24:47 Accessibility, enablement, discoverability

25:53 Accessibility runs both ways

28:38 Bad answers proliferate

28:52 The community managers who refuse AI

29:33 "I want a bot that answers all questions." Then what do you have the community for?

31:41 LinkedIn's slop button

33:08 The leaderboard, flipped

33:59 Monday: automated moderation and the Work Map

34:49 Write your community's AI policy, with your community

37:36 Community managers are enablers

39:20 Human-written, AI-backed

40:31 What is a community for? Answers or connection?

41:16 Uniquely human: built on experience

42:28 Revisit your mission, your values, and take your stand

~44:30 Set what the garden should look like

Key takeaways

• Slop is not merely "written with AI." It is bloated, off, or wrong, and usually reached for as an easy button. Define it for your community and say so publicly.
• AI writing helps the member who is an expert and a poor writer, or writing in a second language. It breaks the moment the prompt is "make me look good" on a question the poster can't answer.
• Communities self-police, because recognition is why people contribute. Negative feedback on slop either drives the poster out or makes them rewrite to be heard.
• Trust now requires provenance, process, and intent. Readers can't tell from the text alone, so show the evidence under the answer.
• If an AI can answer, let it, and send the member into the community when it can't. That enriches the community with new questions instead of repeats.
• Accessibility runs both ways: AI reading the community feeds support, product, and sales. A wrong answer in the community proliferates through all of them.
• Human-written and AI-backed keeps trust. AI-written with human backing loses it.
• Monday: write the AI policy with your team and your executive, run the draft past the community before it becomes terms, and template the removal message so it's kind and fast.
• Communities exist for the questions AI can't answer: "I'm in this situation, do you agree?" Experience is not replicable.
• The same failure produces human slop: a person stopped deciding. Our own pilot is the worked example.