Editorial · Insights
A style guide nobody reads is just décor
The difference between a guide that shapes the work and one that gathers dust isn't the writing. It's the governance around it.
Almost every team we meet has a style guide. A handsome document, often, with a lovingly chosen typeface and a tone-of-voice section full of adjectives. And almost none of it shows up in the actual work. The guide exists; it just doesn't govern. It's décor — proof that someone once cared, gathering dust in a shared drive.
The problem is rarely the content of the guide. It's that writing the guide was treated as the finish line, when it's really the starting one. A standard only matters if it's present at the moment a decision gets made — and a PDF in a folder is never present.
Put the standard where the work happens
The guides that work are the ones woven into the workflow. The key rules live in the editing template, not a separate document. Examples sit next to the brief. The thorny calls — “do we say customer or user,” “do we use the Oxford comma” — are decided once and enforced in review, so they're never argued again at 6pm on a Friday.
A rule that isn't enforced isn't a standard. It's a suggestion with good production values.
Govern lightly, but actually govern
Governance sounds heavy; it doesn't have to be. It means three small things: someone owns the guide, the guide is short enough to actually read, and there's a clear moment in the process where it gets applied. Get those right and a one-page guide will shape your work far more than a fifty-page one that nobody opens. The test of a style guide isn't how complete it is. It's whether you can see it in last week's output.
