Checklist: making a brief that can't produce generic slop

Checklist: making a brief that can't produce generic slop

My writers kept turning in Wikipedia-flavored mush. Added these 4 lines to every brief and it stopped:

— One first-hand detail required per section (a number, a screenshot, a quote, a result).
— Name 2 specific tools/products by name. No "various solutions."
— Include one contrarian take on the topic. Disagree with the consensus somewhere.
— Ban these words: "in today's digital landscape," "unlock," "navigate," "delve."

Forcing specificity at the brief stage beats editing slop at the draft stage every single time.

Steal the 4 lines. Paste into your template.