Here's an overview of the style guide.
Style guide homepage
The first section of the style guide spoke about voice and tone, including a persona to consider while writing.
The tone sections explains a range of appropriate tones and when to use them.
The UX writing standards were referenced by designers and writers from different teams to maintain consistency across the product. If there were overlaps with the brand writing guide (like punctuation), links were provided.
The style guide was written to be a quick read, including examples and screenshots when insightful.
I audited the product and found over 50 terms that needed to be defined in the initial terminology section. Terms were continually added if they required specific defintions within Brex or when we needed to establish the consistent use of one word over its synonyms.
I worked with the design system lead and we identified 11 components that needed content standards. New components would be added later as they were published to the Figma library.
Examples of UI standards
The content style guide also included standards for all Brex product communication channels: email, SMS, and mobile push notifications.
The SMS/WhatsApp notification standards included guidance on international messaging.
The style guide also included other articles I'd written about content design, including thoughts on writing notifications consistently across multiple channels and how to improve content to avoid workflow errors.
Working alongside a designer outside of my core teams, Simran Jassal and I produced a framework for the Reporting experience at Brex.
