UX WRITING GUIDE

The Problem

A cloud-based software company needed to unify its voice among multiple internal teams of stakeholders. Its current state was using an inconsistent series of tenses, shifting voices, and indirect language for users.

The Process

I developed a UX Writing Guide as an internal tool, vetted the guide among executive stakeholders to gain traction and approval, and distributed it company-wide as a flexible document containing guidelines, principles, and best practices.

SG1.png

Transparency:

To enhance its impact and influence, I developed the UX Writing Guide as a reference resource and internal tool to be shared to every team that worked with product, engineering, design, and marketing.

 
SG2.png

Guiding Principles:

Incorporating high-level, brief overviews of general messaging strategy was instrumental to gathering consensus approval from executive leadership.

 
SG3.png

Granular Details:

Providing succinct, specific rules around grammatical use was a pivotal step toward building consistency across the entire UI. Although much of the UX Writing Guide is intended as a flexible, living document, it lays a specific blueprint of granular details that drive a unified voice.

 
SG4.png

Single Source of Truth: 

Additional UX Writing Guide content includes an ever-expanding wordbank that clarifies capitalization, hyphenation, and proper use of verbiage to further align cross-team writing. 

 
 
 

The Solution

My writing guide has been adopted enterprise-wide. It’s also been shared to vendors, partners, program leads, and executives to help direct initiatives and projects during the development process. It's also used by QA teams to align accurate product and feature implementation.