← Insights Hub
AI IntegrationAugust 10, 2026 · 4 min read

Everyone Is Tired of AI Slop. Here Is What They Are Actually Tired Of.

Nobody is angry that a machine helped write something. They are angry that nothing was risked.

Two minutes of scrolling and you can spot it. Same opening hook. Same stack of three word fragments arranged for drama. Same list of five lessons that could apply to a food bank, a fintech startup, or a dog groomer. Same closing question nobody actually wants answered.

That is AI slop. And the sector is tired of it.

Worth getting precise about the complaint, though. Nobody is angry that a machine helped write something. People are angry that nothing was risked. No experience. No position. No detail that could only have come from the person whose face sits on the profile. The output is fluent and empty, and everyone can feel the difference.

WHAT SLOP ACTUALLY COSTS YOU

In nonprofit operations, credibility is the entire currency.

An executive director deciding whether to trust you with their programs is running one test. Does this person know what a compliance finding feels like at 4pm on a Friday. Have they ever had to tell a site coordinator the delivery is not coming. Do they understand what happens to a backpack program when one school contact leaves in October.

Generic content fails that test silently. Nobody comments to tell you. They just stop reading, and you never learn why the pipeline went quiet.

I spent 25 years building programs where the details were the whole job. Kids Cafe at 28 sites. Food 4 Kids, grown to 360 schools and 12,000 kids a week. Federal compliance across 13 counties. None of that ran on general principles. It ran on specifics, and specifics are exactly what copy and paste content strips out.

THE OTHER HALF OF THE STORY

Here is what gets lost in the backlash.

A large group of people are using these same tools carefully and saying almost nothing about it. They are not producing slop. They are moving faster on work that used to eat their week.

That group includes me.

My analytics come out of LinkedIn as raw exports. AI parses them in minutes and tells me Monday is my weakest day and that two posts on the same day cannibalize each other. That is a real finding that changed a real decision.

When a framework feels shaky, AI gets pointed at it as an adversary. Argue against this. Find where it breaks. Tell me what an executive director would push back on. The framework that survives is stronger than the one that never got tested.

Research that used to take two days of reading now takes an afternoon, and the time saved goes into the part only a human can do, which is deciding what any of it means for a specific organization with a specific budget and a specific board.

Free tools on my site got built in hours instead of weeks. The thinking behind them still took the same 25 years.

None of that is copy and paste. Every one of those uses starts with my own position and ends with my own judgment.

THE COSTS ARE REAL AND WORTH NAMING

The data centers are not imaginary. Neither is the water draw, or the pressure on a grid that Texas already knows is fragile. Anyone in Houston who has lived through a summer of conservation notices understands the tradeoff is not theoretical.

Pretending that away would be dishonest.

So would pretending the technology is going to reverse itself. It is not. This is the same shape as every operational shift the sector has already been through. Spreadsheets replaced ledger pads. Donor databases replaced index card files. Route software replaced the dispatcher with a whiteboard and a good memory. Every one of those had real costs and real holdouts, and every holdout organization eventually paid more to catch up than it would have paid to adapt.

The question is not whether to engage. The question is whether you engage with your judgment intact.

WHERE THE LINE SITS

Use it to extend your thinking. Never use it to replace your thinking.

The thing you own is pattern recognition built from failure. The audit that almost went sideways. The partner that looked strong on paper and collapsed in month four. The staff structure that worked in a $2M organization and broke at $6M. No model has that. It has read about it. You lived it.

There is a second line, and it matters more.

This sector runs on trust that gets built in rooms. In a partner agency parking lot. On a call where somebody finally admits the program is underwater. At a conference table where two directors figure out they can share a truck.

None of that survives being outsourced. Efficiency is worth something. Connection is worth more, and the people who forget that will build very fast operations that nobody wants to work with.

WHAT TO DO WITH THIS ON MONDAY

  1. Start with your own take, not a blank prompt. Write three messy sentences of what you actually believe, then bring the tool in.
  2. Feed it your material. Your program data, your board packet, your last three failures. Generic input produces generic output every time.
  3. Make it argue with you. The most useful prompt in my rotation is some version of tell me why this is wrong.
  4. Protect the specifics. Numbers, program names, the thing that happened in October. That is the part readers trust.
  5. Read it out loud before it ships. If it does not sound like something you would say to a peer across a table, it is not ready.

Then close the laptop and call somebody.

WHERE THIS FITS

My practice is built on operations work that does not scale by volume. Systems that outlast my involvement. Compliance that holds under review. Structures that let a program run without the executive director in the room.

AI makes parts of that work faster. It does not make the judgment, and it never will. The organizations I work with are not paying for output. They are paying for somebody who has already seen the failure they are walking toward.

Tie it together

AI makes parts of operations work faster. It does not fix operations running on institutional memory. The Operations Audit shows what is documented, what is not, and what to fix first.

This edition is also published in the Run The Mission newsletter on LinkedIn.

Running on memory instead of systems?

The writing names the problem. A call is where we size yours. Thirty minutes, no pitch.

Book a Call

30 minutes · No obligation · Houston and remote engagements welcome

HomeHow I HelpResourcesInsightsAboutBook Call