An observation: many government content style guides exist, but they’re rarely used in practice
Not because the guidance isn’t good, but because no one actually uses them.
They sit quietly in a Google Drive folder or on a website for others to see, written once and rarely revisited. Meanwhile, the website itself suffers from inconsistencies. This can be due to many factors.
Talk more, write less strategies
A much better approach is to make content patterns and standards an active team practice. You can do this by running regular sessions where you look at real pages and talk about links, words you use, buttons, components – the small stuff.
Consistency is what creates a good user experience. When patterns and language are predictable, users learn how a service works and move through it with confidence.
Once patterns exist, it also allows your team to work more efficiently because you stop reinventing the wheel. New people joining the team also have a practical library to work from rather than starting from scratch.
More importantly, it turns standards and strategies into something real because you are actively questioning and debating them. It also allows you to bring user feedback and data into the conversation.
Content pattern sessions can also strengthen your team when it comes to pushback
I get it – implementing standards is hard. More than often I see services and stakeholders pushing back on how something looks, the words used, or how a component behaves.
But when you investigate these patterns and standards together as a team regularly, you give yourself something solid to debate with. It moves the conversation from opinion to evidence. Evidence you can use when engaging with services. This in turn can give your team more confidence saying no (with evidence) when engaging with services.
Content patterns are content strategy in motion
They showcase strategy in a practical way. If your strategy says things like “we ensure our content is accessible and user-friendly” or “we write for all users with a clear heading structure” — show it on your website, consistently.
I often feel like strategies and principles are written for people in the organisation to read. But really, they should be for the content team to demonstrate through the work they produce.
At the end of the day, users and services are not reading your strategy documents. They just want a better experience. And for services, that might mean fewer calls, fewer complaints, and fewer people getting stuck.
It’s fine to point to your strategy, but make sure the actions it describes are actually visible in the content you publish.
Why simply pointing to other organisations' standards and patterns isn't enough
Yes, pointing to standards and patterns that already exist elsewhere, like the GOV.UK style guide or the NHS Design System, can be helpful when engaging with stakeholders. But that's not really the point.
Standards need to be discussed, challenged and revisited regularly by the team. Simply pointing to external guidance risks becoming a bit of a shortcut, especially when we may not know how recently it has been updated or whether everyone feels confident to apply it in practice.
For a team to really understand standards and patterns and use them in their everyday work, there needs to be an open forum. This cannot just be a static document or webpage. It should be living space for debate so that the standards are properly understood, tested and improved over time.
It is always good to remember that once your content is live on your website, it's a living thing. User behaviour changes. Expectations change. Services evolve. Your patterns should evolve with them.
Let me know your thoughts
If you’re interested in content patterns or how to run these kinds of sessions in your team, feel free to message me. Or share your approach to keeping standards and consistency alive in your team. I'd be keen to hear them.
