Language Guidelines

Table of contents of language guidelines
Table of contents of language guidelines

Language Guidelines

Table of contents of language guidelines
Table of contents of language guidelines

Prototype

Journey Maps

Other Artifacts

Language Guidelines

Table of contents of language guidelines

Due to NDA restraints, I am unable to host identifying information publicly. For prototypes or other artifacts, please contact me at abby.brams@gmail.com.

TLDR: I created a standardized content process to improve language consistency across the Enterprise UX team. This included a Figma template, review workflow, intake form, and centralized language guidelines. The system reduces duplication, supports alignment with brand voice, and enables scalable, efficient content creation across the enterprise.

Situation

As content contributions across the company grew, it became clear there was no consistent standard or centralized process guiding how content was written, reviewed, or published. Designers and teams were creating content independently, often duplicating efforts or producing inconsistent language and tone across experiences. This fragmentation created confusion for associates using our tools and inefficiencies for teams building them. Without a shared set of guidelines or a clear intake and review process, it was difficult to ensure quality, alignment, and reuse.

The business objective was to improve clarity, consistency, and efficiency in how product and UX content were created and shared across teams. A standardized process would reduce rework, enable better cross-functional collaboration, and support more scalable content practices across the enterprise. It would also help teams better align with brand voice, reduce inconsistencies in associate-facing tools, and ultimately deliver more cohesive, intuitive user experiences.

The Problem

There was no centralized process or standard for creating and reviewing content across teams, which led to inconsistent language, duplicated efforts, and slower workflows. Designers and product teams often create similar content in isolation without clear guidance or visibility into existing work. This lack of alignment introduced inconsistencies across app experiences, impacting both associates and customers. While teams wanted to create high-quality content, they lacked the infrastructure and tools to do so efficiently and at scale.

Solution

To address the lack of content consistency and infrastructure, I led the creation of a scalable content standards system that could be adopted across teams. I started by developing a project plan to define goals, align stakeholders, and identify the core elements needed to support content contributions.

I created a reusable Figma template that anyone could use to submit content proposals, making it easy for contributors to participate without needing to start from scratch. I also designed a review process to ensure submitted content met brand and UX standards, enabling quality control while encouraging collaboration. To centralize intake, I launched a Slack channel with an embedded request form, giving teams a clear, accessible way to share content needs or proposals.

All finalized content guidelines were published in a dedicated Figma file, serving as a single source of truth that teams could reference and build upon. This system not only provided clarity and structure but also laid the foundation for more consistent, scalable content practices across the enterprise.

Evaluation

The new content standards system has been well-received and is already helping teams align on voice, tone, and terminology across tools and experiences. By providing clear entry points—a Figma template, a centralized Slack intake form, and a shared guidelines file—contributors now have the structure they need to work efficiently and consistently. Teams that previously worked in silos are now referencing the same standards, which is reducing duplication and improving the quality of associate- and customer-facing content.

The process is also scalable. As more teams adopt the framework, we’re seeing stronger alignment across the enterprise and a more unified user experience. Looking ahead, the system can evolve to include additional documentation, training materials, or governance models to support long-term sustainability. This foundational work sets the stage for more strategic content operations, enabling better collaboration, faster delivery, and more coherent digital experiences.

Other work