<![CDATA[Community Assistant .ai]]>

You got into community for the people, not the busywork.

Community managers are being squeezed from two directions: executives asking why humans are needed at all, and AI eating the search traffic that once proved community value. This show makes the affirmative case, not by rejecting AI, but by getting precise about what it can and cannot do. AI can answer most questions, store collective memory, and scale parts of the work. It cannot build trust, read a room, mediate conflict, or create the relational fabric that makes communities matter. AI supports answers. Humans build trust.

Each week, host Chris Heuer (30+ years building communities online, offline and in global enterprises) and co-host Marius Ciortea talk with practitioners, builders, and skeptics about which parts of the work belong to AI agents, which stay irreducibly human, and how to tell the difference. The show is supported by the Work Map, an open inventory of nearly 300 community management jobs classified as Human, Agent, or Hybrid.

Topics include AI tools for community managers, agents and automation, member engagement, trust and moderation, community strategy, proving community value, and the future of the profession. If you manage a community and you're deciding what to hand to AI and what to keep, this show is for you.

Sponsored by Higher Logic. Every episode includes actionable tactics you can use. Explore the Work Map and join us at communityassistant.ai.

]]>https://communityassistant.ai/Riverside.fm (https://riverside.com)Fri, 11 Sep 2026 07:46:29 GMTWed, 08 Jul 2026 15:41:36 GMT60Chris Heuer with Marius Ciortea<blockquote><p>You got into community for the people, not the busywork.<br /></p><p>Community managers are being squeezed from two directions: executives asking why humans are needed at all, and AI eating the search traffic that once proved community value. This show makes the affirmative case, not by rejecting AI, but by getting precise about what it can and cannot do. AI can answer most questions, store collective memory, and scale parts of the work. It cannot build trust, read a room, mediate conflict, or create the relational fabric that makes communities matter. AI supports answers. Humans build trust.<br /></p><p>Each week, host Chris Heuer (30+ years building communities online, offline and in global enterprises) and co-host Marius Ciortea talk with practitioners, builders, and skeptics about which parts of the work belong to AI agents, which stay irreducibly human, and how to tell the difference. The show is supported by the Work Map, an open inventory of nearly 300 community management jobs classified as Human, Agent, or Hybrid.<br /></p><p>Topics include AI tools for community managers, agents and automation, member engagement, trust and moderation, community strategy, proving community value, and the future of the profession. If you manage a community and you're deciding what to hand to AI and what to keep, this show is for you.<br /></p><p>Sponsored by Higher Logic. Every episode includes actionable tactics you can use. Explore the Work Map and join us at <a rel="noopener noreferrer nofollow" href="http://communityassistant.ai" target="_blank">communityassistant.ai</a>.</p></blockquote><p></p>episodicChris Heuer with Marius Ciorteachris@adhocnium.comno<![CDATA[What Is AI Slop and What Does It Cost a Community?]]>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.
]]>8de1c094-0c87-43d2-8d33-03bb2b361418Wed, 09 Sep 2026 23:00:00 GMT<p>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.</p><p></p><p><b>TC Chapter</b></p><p>00:00 Cold open: human slop, and why we're talking about it</p><p>00:25 Welcome</p><p>01:37 The pilot correction</p><p>02:18 Preferring AI answers, not trusting them</p><p>02:35 What's at stake is trust</p><p>03:19 What is AI slop? Too long to find the useful part</p><p>04:07 Bloated, off, or wrong, and the easy button</p><p>05:08 Can AI writing not be slop?</p><p>05:16 Code is poetry; slop is in the eye of the beholder</p><p>06:39 The Druckenmiller op-ed: written by AI</p><p>08:55 The PR-firm defense</p><p>09:17 Your personal intelligence system</p><p>12:22 Where AI writing helps a community: the expert who can't write</p><p>14:04 Where it breaks: "make me look good"</p><p>14:42 Low effort, low quality, and intent: the LinkedIn problem</p><p>16:10 Communities self-police</p><p>17:51 "I failed English": provenance, process, intent</p><p>19:17 The verification loop</p><p>20:44 The evidence under the answer</p><p>21:43 Show your work</p><p>22:05 The 15-minute conversation was the prompt</p><p>22:50 The 8,000-word wall of text</p><p>~23:40 Where is AI actually best deployed in a community?</p><p>24:00 Sponsor MidRoll - Higher Logic</p><p>24:47 Accessibility, enablement, discoverability</p><p>25:53 Accessibility runs both ways</p><p>28:38 Bad answers proliferate</p><p>28:52 The community managers who refuse AI</p><p>29:33 "I want a bot that answers all questions." Then what do you have the community for?</p><p>31:41 LinkedIn's slop button</p><p>33:08 The leaderboard, flipped</p><p>33:59 Monday: automated moderation and the Work Map</p><p>34:49 Write your community's AI policy, with your community</p><p>37:36 Community managers are enablers</p><p>39:20 Human-written, AI-backed</p><p>40:31 What is a community for? Answers or connection?</p><p>41:16 Uniquely human: built on experience</p><p>42:28 Revisit your mission, your values, and take your stand</p><p>~44:30 Set what the garden should look like<br /><br />Key takeaways</p><ul><li>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.</li><li>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.</li><li>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.</li><li>Trust now requires provenance, process, and intent. Readers can't tell from the text alone, so show the evidence under the answer.</li><li>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.</li><li>Accessibility runs both ways: AI reading the community feeds support, product, and sales. A wrong answer in the community proliferates through all of them.</li><li>Human-written and AI-backed keeps trust. AI-written with human backing loses it.</li><li>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.</li><li>Communities exist for the questions AI can't answer: "I'm in this situation, do you agree?" Experience is not replicable.</li><li>The same failure produces human slop: a person stopped deciding. Our own pilot is the worked example.</li></ul>no00:47:1611What Is AI Slop and What Does It Cost a Community?full<![CDATA[SEO Lived in Marketing. GEO Lives in Community.]]>Community managers spent a decade proving their value in page views and then in engagement. Those numbers are going the wrong way now, and they aren't coming back.

Marius Ciortea thinks that's an opening rather than a loss. In this episode, he makes the case that generative engine optimization is a community job: SEO lived in marketing, and GEO will live in or next to the community team, because your community is usually the only user-generated content your brand actually owns and can influence.

He and host Chris Heuer work through what that means for the person with a queue of unanswered posts and a metrics deck due Friday. How AI systems read a community thread. Which signals make an answer legible to a model: recognized author authority, employee and support attribution, community endorsement, answers marked correct, content that isn't stale. Why the highest-leverage work here isn't a file format but the practice of recognizing authority and retiring outdated material. And what you put in front of your executives when traffic stops being the story.

Chris also introduces the Work Map, an open inventory of the jobs community managers actually do, and identifies GEO as a gap it doesn't yet cover. That one will be getting built in public, with your help.

If the only way you justify your existence has been traffic, you're already in trouble. This episode is about the other way.

Sponsored by Higher Logic and supported by Inflection Point.

Chapters

00:00 Cold open: GEO belongs to community
00:57 Welcome, and why this show exists
03:01 Amplification, not replacement
04:32 Underfunding and the business case problem
05:48 Bots now outnumber humans on the web
07:14 The support question that never reached the forum
08:12 How AI reads a community thread
09:51 Authority signals: badges, staff attribution, upvotes
12:00 Temporality, llms.txt, and ontologies
13:17 The prediction: do the community work, not the file format
15:23 What replaces traffic as the metric
16:26 "If traffic is your only ROI, you're already in trouble"
16:49 Citations, bot-versus-human data, and GEO dashboards
18:11 Why GEO belongs to the community team
20:28 Attribution, and the ad model that's coming
21:34 The Work Map, and owning its gaps
23:51 Why Marius is doing this
26:47 "I've always been lazy": outcome-driven automation
28:54 Translation, humans don't scale, and the reframe
33:09 AI slop, and why the brand doesn't care
35:15 Close

Key takeaways

GEO is a credibility opening for community teams. Community is usually the only user-generated content a brand owns and can influence, which makes the community team the natural home for it.

The signals that make an answer legible to a model are things community managers already control: who answered, their standing, whether the community endorsed it, whether it was marked correct, and whether it's current.

The highest-leverage GEO work is not a technical file. It is about recognizing authority, consistently marking correct answers, and retiring stale content.

More of the web is now crawled by bots than browsed by humans, which breaks the page-views story community managers have been telling executives.

Citation and bot-traffic data is starting to appear in platform back ends, which gives community managers a replacement metric for the traffic they're losing.

Automation in community is not new. Profanity filtering, unanswered-question queues, and translation each moved work off the plate. AI is the next turn of that wheel, not a break from it.

The brand's interest is that the member got a correct answer and can use the product. Insisting that the answer come from the community is the wrong hill to die on.

]]>d2caeea8-be5a-47f7-8b3f-34cc751a9541Wed, 09 Sep 2026 07:15:00 GMT<p>Community managers spent a decade proving their value in page views and then in engagement. Those numbers are going the wrong way now, and they aren't coming back.<br /><br />Marius Ciortea thinks that's an opening rather than a loss. In this episode, he makes the case that generative engine optimization is a community job: SEO lived in marketing, and GEO will live in or next to the community team, because your community is usually the only user-generated content your brand actually owns and can influence.<br /><br />He and host Chris Heuer work through what that means for the person with a queue of unanswered posts and a metrics deck due Friday. How AI systems read a community thread. Which signals make an answer legible to a model: recognized author authority, employee and support attribution, community endorsement, answers marked correct, content that isn't stale. Why the highest-leverage work here isn't a file format but the practice of recognizing authority and retiring outdated material. And what you put in front of your executives when traffic stops being the story.<br /><br />Chris also introduces the Work Map, an open inventory of the jobs community managers actually do, and identifies GEO as a gap it doesn't yet cover. That one will be getting built in public, with your help.<br /><br />If the only way you justify your existence has been traffic, you're already in trouble. This episode is about the other way.<br /><br />Sponsored by Higher Logic and supported by Inflection Point.<br /><br />Chapters<br /><br />00:00 Cold open: GEO belongs to community<br />00:57 Welcome, and why this show exists<br />03:01 Amplification, not replacement<br />04:32 Underfunding and the business case problem<br />05:48 Bots now outnumber humans on the web<br />07:14 The support question that never reached the forum<br />08:12 How AI reads a community thread<br />09:51 Authority signals: badges, staff attribution, upvotes<br />12:00 Temporality, llms.txt, and ontologies<br />13:17 The prediction: do the community work, not the file format<br />15:23 What replaces traffic as the metric<br />16:26 "If traffic is your only ROI, you're already in trouble"<br />16:49 Citations, bot-versus-human data, and GEO dashboards<br />18:11 Why GEO belongs to the community team<br />20:28 Attribution, and the ad model that's coming<br />21:34 The Work Map, and owning its gaps<br />23:51 Why Marius is doing this<br />26:47 "I've always been lazy": outcome-driven automation<br />28:54 Translation, humans don't scale, and the reframe<br />33:09 AI slop, and why the brand doesn't care<br />35:15 Close<br /><br />Key takeaways<br /><br />GEO is a credibility opening for community teams. Community is usually the only user-generated content a brand owns and can influence, which makes the community team the natural home for it.<br /><br />The signals that make an answer legible to a model are things community managers already control: who answered, their standing, whether the community endorsed it, whether it was marked correct, and whether it's current.<br /><br />The highest-leverage GEO work is not a technical file. It is about recognizing authority, consistently marking correct answers, and retiring stale content.<br /><br />More of the web is now crawled by bots than browsed by humans, which breaks the page-views story community managers have been telling executives.<br /><br />Citation and bot-traffic data is starting to appear in platform back ends, which gives community managers a replacement metric for the traffic they're losing.<br /><br />Automation in community is not new. Profanity filtering, unanswered-question queues, and translation each moved work off the plate. AI is the next turn of that wheel, not a break from it.<br /><br />The brand's interest is that the member got a correct answer and can use the product. Insisting that the answer come from the community is the wrong hill to die on.</p>no00:36:371SEO Lived in Marketing. GEO Lives in Community.bonus