Methodology

Voice Violation

Anti-slop category for missing operator perspective, over-polished tone, or writing that sounds like a vendor pitch instead of a practitioner notebook.

Voice violations are the third layer of anti-slop detection, targeting tone and perspective failures that editorial polish alone cannot fix. Key detections: missing first-person experience ("we found that" instead of "I tested this across 3 accounts"), over-polished transitions (real operator writing has rougher edges), vendor-pitch framing (positioning features as benefits without evidence), hedging avoidance (AI models rarely write "I'm not sure" or "this might not work for you"), and absent specificity (saying "significant improvement" instead of "from 12% to 34%"). The operator edit pattern applies: cut anything serving article structure (pre-announcements, consequence enumerations), add anything proving practice (anchor numbers, dominant tool names, honest hedges). Voice violations require human review because the fix depends on the author's actual experience.

Where it shows up:

Thought leadership reviewBlog editingNewsletter voice checkConsulting deliverables

Build your Knowledge OS

90 minutes from zero to your first skill chain.