Context
Compliance content on the platform was being written question-by-question, by different people, with no shared model for voice, tone, or structure. The result was inconsistency, the same concept phrased differently depending on who wrote it, guidance notes with no fixed shape, and no clear line between what belonged in a question versus what belonged in the content around it.
This became a priority when the company shifted its wider brand strategy from a house of brands to a single branded house, several previously distinct products and voices needed to consolidate into one consistent identity. Content was one of the clearest places that inconsistency showed up, and one of the hardest to unify without a system behind it. I designed and led the content framework that made that consolidation possible.
Approach
Rather than writing a list of style rules, I modelled content as layers, each dependent on the one above it:
This layering meant designers didn't need to re-decide tone or voice from scratch for every new question, brand, or region, they had a decision tree instead of a blank page.
Key deliverables
Voice definition: rather than abstract adjectives, I defined voice through paired examples : "we say / we don't say" for each trait (clear, direct, precise, respectful), making the voice testable rather than subjective, and portable across previously separate brands.
Tone-by-context matrix: a single reference table mapping tone to situation, neutral and instructional for question labels, reassuring and non-judgemental for sensitive disclosures, direct and blame-free for validation errors, so tone decisions became lookups, not debates.
The Guidance Block: a fixed, ordered set of content slots (definition line, key terms, steps, common mistakes, source link, note) that every piece of surrounding content is built from. This gave designers and reviewers a shared structure to check content against, and stopped guidance sprawling into inconsistent shapes across the platform.
Accessible, living documentation: the framework is hosted online rather than living in a static document, so any designer, reviewer, or stakeholder can access the current standard directly, see it evolve, and apply it consistently without relying on someone else's institutional knowledge.
Impact
Why this mattered