AI slop reached facilitation. The fix is knowing which half of the work to hand over.

There is a thread on r/agile this month called "Anyone Having AI Slop Issues?". It has 36 upvotes and 35 comments, and almost none of them are about agile. They are about what happens when a team gets very good at generating things and no better at judging them.

One reply came from an executive at a large product development company. Engineering productivity tripled, he wrote, and then the bottleneck simply moved: "you can release 100 features, but..." The sentence trails off because everyone in the thread already knows the ending. More output, same amount of judgment, worse outcomes.

Facilitators and L&D teams are arriving at the same place from a different road. You can now generate a workshop agenda in nine seconds. What you cannot generate in nine seconds is the reason activity three exists.

Slop is not bad writing. It is missing rationale.

When people call AI output slop, they are rarely complaining about grammar. The prose is usually fine. What is missing is the structural logic underneath, the thing an experienced facilitator carries in their head and a generic model does not have.

Ask a general-purpose AI for a half-day team session on trust and it will produce something that reads well: an icebreaker, a discussion, a reflection, a closing. Try to run it and the questions start. Why is the icebreaker twenty minutes? What is the debrief actually meant to surface? Why does the trust exercise come before the conflict exercise instead of after?

There are real answers to those questions. Lencioni's Five Dysfunctions model says trust has to precede conflict, because a team that does not trust each other will not argue productively. Kolb says a concrete experience needs a reflective observation phase or the experience does not convert into anything. These are not decorations. They are load-bearing.

Generic AI output does not know it is skipping them. It produces the shape of a session without the skeleton, and the gap only becomes visible in the room, in front of twelve people, at 10:40 in the morning.

What the same communities are angry about

The pattern repeats wherever practitioners gather. On r/instructionaldesign this month, a 43-point thread asks why Articulate Rise shipped an "AI tutor" before it shipped a working search function. The most-upvoted verdict is blunt:

Rise is the poor child that several others do better.

Read that thread carefully and it is not anti-AI. Nobody is arguing that AI has no place in learning design. They are angry about AI as a feature checkbox, bolted on to a tool that has not solved its basic job, aimed at a buyer rather than a user.

Meanwhile the most upvoted L&D thread of the month, at 47 points, argues that anonymised AI chat logs may be the most interesting data source in the field right now, because they show what people actually get stuck on. Its top comment names the real problem: "there's a gap between what IDs design training for and what learners actually need."

That is the honest version of the AI conversation in this field. Not "will it replace us." Rather: it is very good at production and very bad at judgment, and most tools have the split backwards.

Which is why facilitation just got more valuable, not less

The trade press has landed on the same conclusion from the top down. Training Industry's 2026 outlook argues AI is moving past content generation into facilitation itself, and that success will be decided by culture, trust and human capacity rather than by model quality. Inclusivv went further and called facilitation training one of the most important skills of 2026. The World Economic Forum, writing about how to actually scale AI skills inside organisations, landed on in-person workshops with trained facilitators and mentors at every table.

Notice what all three have in common. As generating content approaches zero cost, the scarce thing is not content. It is the person who can read a room, sequence an experience, and hold a group through a difficult conversation.

If you facilitate for a living, that is the best news you will get this year. It also comes with a bill: the market will pay for the judgment, and it will stop paying for the production hours around it. Nobody is going to fund three days of building worksheets when the alternative costs nine seconds.

The useful split

The way through is not "use AI" or "don't use AI." It is being precise about which half of the work you are handing over.

Production is safe to delegate. Laying out worksheets, formatting slides, assembling a facilitator guide, writing the client brief, turning your agenda into a participant workbook, keeping fifteen documents consistent when activity four changes. This is the work that eats evenings and bills to nobody.

Judgment is not. What this group actually needs, which method fits this outcome, what order the experiences go in, when to break, when to abandon the plan because the room went somewhere better. This is what people hire you for.

The tools that will survive this period are the ones built along that line rather than across it:

• Grounded in real methods, so the sequence has a reason behind it
• Generating the full materials stack, so production actually disappears instead of moving
• Leaving the judgment where it belongs, with the facilitator

That is the bet we made building METODIC: a curated library of 700+ facilitation methods and 168 learning frameworks underneath the generation, so a session comes out with a spine and not just a shape. You describe the session; it designs the agenda on real methods and produces every material to match. You stay the facilitator.

The r/agile thread ends without resolution, which is honest. But one comment gets close, and it is a good rule for anything you let AI touch:

It's always based on my input + reviewed after.

That is the whole discipline. Bring the judgment. Delegate the production. Review the result before it meets a real room.

---

Marco van Hout is a facilitator and the founder of METODIC. You can design a full session free at metodic.io.