Making sure
it is not slop
Ask people what is wrong with AI output and you get one answer more than any other: it is generic. Bland writing that could have been about anyone. Designs that look like every other template. The word for it is slop, and producing it at scale is the default failure mode of every tool in this course. This chapter is the fix, and it is a discernment skill, the ability to look at output and see that it is average, before you ship it as if it were yours.
Here is why slop happens, because understanding it is half the cure. A model, asked plainly, gives the average answer to the average question, because the average is what it was trained to produce. That is not a flaw you prompt away with one clever instruction. It is the gravity of the thing, and the only way to beat gravity is a deliberate pass afterward that drags the output off the average and toward something that is actually yours.
Written slop has a fingerprint, and once you can see it you cannot unsee it. The giveaway phrases, the tidy lists of three, the "it is not just X, it is Y" shape, the breathless adjectives that describe nothing, and, the tell this whole brand refuses, the em-dash sprinkled everywhere as a rhythm crutch. None of it is wrong exactly. It is just what the average sounds like, which means it sounds like no one.
The fix is a set of editing passes, each hunting one kind of slop, run after the draft exists. We have built these and give them away: a humanizer that strips the AI tells and generic phrasing, a copy-editing pass of sequential sweeps that each fix one thing, and the voice audit that flags any sentence that could have been written about anyone. You do not run them all every time, but knowing they exist and running the right one is what separates shipped-average from shipped-yours.
Notice the last card, because it is the half people forget. Removing the slop leaves you with clean, correct, still-generic text. The output is not yours until you put yourself back in: the specific detail only you know, the real example, the slightly odd phrasing a committee would have smoothed out. Stripping the tells and adding the truth are two moves, and you need both.
Design slop is the same disease in a different medium. The default AI layout is competent and utterly forgettable: the same centred hero, the same three feature cards, the same rounded everything, the look that says a machine made safe choices. It is not broken. It is just the visual average, and the average is invisible.
The cure is the same shape as for text, and we build design skills that give it away too: front-end design guidance, web-design guidelines, and a library of real, distinctive design systems to learn from rather than defaulting past. The single most useful instruction inside them is this: take one real aesthetic risk you can justify. Not ten, not zero. One considered choice that a template would never have made, that you can explain, that makes the thing look like a decision instead of a default.
The discipline is precisely one risk, justified. Ten risks is chaos, another kind of slop. Zero risks is the forgettable default. One choice you can defend, with everything else kept clean and calm around it, is how a design stops looking machine-made. And it ties back to the beginning of the course: you bring the taste and the point of view, the tool brings the execution. Design slop is what you get when you let the tool bring the taste too.
The way to build this into how you work is to always look at the before and after. Run the pass, and hold the average version next to the specific one. Seeing the two side by side trains your discernment faster than any rule, because you feel the difference between forgettable and yours, and after a while you start catching the slop in the draft before you even run the pass.
That is the whole chapter in two sentences. The first could be any company selling anything, which means it sells nothing. The second could only be one shop, which is exactly why it lands. The passes exist to get you from the first to the second, reliably, on purpose, every time you are about to ship something a machine drafted.
Take one real thing you drafted or designed with AI recently, a piece of copy, a page, a layout. Run the matching anti-slop pass: for text, strip the tells then put yourself back in; for design, name the one justified risk you would take and what you would keep clean around it. Keep the before and after side by side. The win is a specific, yours version next to the generic one, and the trained eye that comes from seeing the gap.
Show the worked solution
- Slop, the generic templated quality, is the default output of every AI tool, because the model produces the average and the average sounds like no one.
- You beat it with a deliberate pass after drafting, not a cleverer single prompt. We build and give away the passes: a humanizer, a copy-editing sweep set, and a voice audit.
- Text has two moves: strip the tells (generic phrasing, tidy triples, empty adjectives, em-dashes), then put yourself back in with concrete, true, specific detail.
- Design slop is the same disease: beat it by taking exactly one justified aesthetic risk and keeping everything else clean, so it looks like a decision, not a default.
- Train the eye by comparing before and after every time, until you catch the slop in the draft and stop shipping the average as if it were yours.
Run one real AI output through the matching anti-slop pass this week, and keep the before and after side by side. You now have the discernment that separates shipped-average from shipped-yours. One chapter left, the honest one: where all of this breaks at scale, and what stays yours no matter how much power you have.
The tool will always hand you the average first, because the average is what it knows. Slop is not it failing, it is it defaulting. The work, the only work it cannot do, is dragging the output off the average and putting the specific, true, unmistakably-you thing back in. That refusal to ship the generic is taste, and taste is the part that stays yours.