Designing with Words
Crafting clear, consistent, and human-centered UX writing guidelines to simplify complex product experiences at scale.
Insights
3 minutes
Building UX Writing Guidelines for a Global Design System
When we think about design systems, we often focus on components, layouts, and visual consistency. But one of the most powerful—and often overlooked—elements is language.
As part of the Honeywell Forge design system, I worked on defining UX writing guidelines that ensure every interaction across products feels clear, consistent, and human.
Why UX Writing Matters in Complex Products
Honeywell’s products operate in high-stakes, industrial environments where clarity isn’t just helpful—it’s critical.
Users rely on interfaces to make decisions quickly and confidently. Poorly written content can lead to confusion, delays, or even errors. The goal was to create a system where:
Information is easy to understand at a glance
Users know what’s happening and what to do next
Language reduces cognitive load instead of adding to it
This meant moving away from technical, jargon-heavy communication to something far more intentional.
Defining a Clear and Consistent Voice
We established a tone of voice that could scale across products while still adapting to context.
The voice is:
Clear and concise → prioritising readability and quick scanning
Warm and natural → conversational without being casual
Helpful and supportive → guiding users without overwhelming them
A key principle was simple:
Say more with less—and say it clearly.
This translated into writing that gets straight to the point, avoids unnecessary complexity, and always prioritises user understanding.
Writing for a Global Audience
Designing for a global organisation brought an additional layer of complexity.
While we standardised on American English, the guidelines also accounted for:
Localization and cultural sensitivity
Avoiding idioms and colloquialisms
Using simple grammar and neutral language
Ensuring content is easily translatable
The challenge wasn’t just consistency—it was clarity across cultures and contexts.
From Principles to Practice: Writing in Interfaces
To make the guidelines actionable, we translated principles into real UI patterns.
Error Messages
Instead of vague or technical errors, we structured messages into:
What happened
Why it happened (if known)
What the user can do next
The focus was on being clear, calm, and actionable, especially in critical scenarios.
Forms and Inputs
Forms are often friction points, so clarity here is essential.
We emphasised:
Direct, descriptive labels
Helpful placeholder and helper text
Clear error feedback with guidance
Every word in a form should answer a simple question:
“What do I need to do here?”
Designing for Clarity at Scale
One of the biggest challenges was ensuring consistency across multiple products, teams, and use cases.
The guidelines were designed not just as rules, but as a framework teams could build on, encouraging:
Consistent terminology
Scalable writing patterns
Alignment between design, product, and engineering
This helped create a shared language across the ecosystem.
Key Takeaways
This project reinforced a simple but powerful idea:
UX writing is not just content—it is design.
The right words can:
Reduce friction
Build trust
Guide decisions
Improve overall usability
And in complex systems like Honeywell’s, they can make all the difference between confusion and clarity.
Want to read more?
Whether it's a quick chat or a deep dive, I'd love to hear from you.
More to Discover
Designing with Words
Crafting clear, consistent, and human-centered UX writing guidelines to simplify complex product experiences at scale.
Insights
3 minutes
Building UX Writing Guidelines for a Global Design System
When we think about design systems, we often focus on components, layouts, and visual consistency. But one of the most powerful—and often overlooked—elements is language.
As part of the Honeywell Forge design system, I worked on defining UX writing guidelines that ensure every interaction across products feels clear, consistent, and human.
Why UX Writing Matters in Complex Products
Honeywell’s products operate in high-stakes, industrial environments where clarity isn’t just helpful—it’s critical.
Users rely on interfaces to make decisions quickly and confidently. Poorly written content can lead to confusion, delays, or even errors. The goal was to create a system where:
Information is easy to understand at a glance
Users know what’s happening and what to do next
Language reduces cognitive load instead of adding to it
This meant moving away from technical, jargon-heavy communication to something far more intentional.
Defining a Clear and Consistent Voice
We established a tone of voice that could scale across products while still adapting to context.
The voice is:
Clear and concise → prioritising readability and quick scanning
Warm and natural → conversational without being casual
Helpful and supportive → guiding users without overwhelming them
A key principle was simple:
Say more with less—and say it clearly.
This translated into writing that gets straight to the point, avoids unnecessary complexity, and always prioritises user understanding.
Writing for a Global Audience
Designing for a global organisation brought an additional layer of complexity.
While we standardised on American English, the guidelines also accounted for:
Localization and cultural sensitivity
Avoiding idioms and colloquialisms
Using simple grammar and neutral language
Ensuring content is easily translatable
The challenge wasn’t just consistency—it was clarity across cultures and contexts.
From Principles to Practice: Writing in Interfaces
To make the guidelines actionable, we translated principles into real UI patterns.
Error Messages
Instead of vague or technical errors, we structured messages into:
What happened
Why it happened (if known)
What the user can do next
The focus was on being clear, calm, and actionable, especially in critical scenarios.
Forms and Inputs
Forms are often friction points, so clarity here is essential.
We emphasised:
Direct, descriptive labels
Helpful placeholder and helper text
Clear error feedback with guidance
Every word in a form should answer a simple question:
“What do I need to do here?”
Designing for Clarity at Scale
One of the biggest challenges was ensuring consistency across multiple products, teams, and use cases.
The guidelines were designed not just as rules, but as a framework teams could build on, encouraging:
Consistent terminology
Scalable writing patterns
Alignment between design, product, and engineering
This helped create a shared language across the ecosystem.
Key Takeaways
This project reinforced a simple but powerful idea:
UX writing is not just content—it is design.
The right words can:
Reduce friction
Build trust
Guide decisions
Improve overall usability
And in complex systems like Honeywell’s, they can make all the difference between confusion and clarity.
Want to read more?
Whether it's a quick chat or a deep dive, I'd love to hear from you.
More to Discover
Designing with Words
Crafting clear, consistent, and human-centered UX writing guidelines to simplify complex product experiences at scale.
Insights
3 minutes
Building UX Writing Guidelines for a Global Design System
When we think about design systems, we often focus on components, layouts, and visual consistency. But one of the most powerful—and often overlooked—elements is language.
As part of the Honeywell Forge design system, I worked on defining UX writing guidelines that ensure every interaction across products feels clear, consistent, and human.
Why UX Writing Matters in Complex Products
Honeywell’s products operate in high-stakes, industrial environments where clarity isn’t just helpful—it’s critical.
Users rely on interfaces to make decisions quickly and confidently. Poorly written content can lead to confusion, delays, or even errors. The goal was to create a system where:
Information is easy to understand at a glance
Users know what’s happening and what to do next
Language reduces cognitive load instead of adding to it
This meant moving away from technical, jargon-heavy communication to something far more intentional.
Defining a Clear and Consistent Voice
We established a tone of voice that could scale across products while still adapting to context.
The voice is:
Clear and concise → prioritising readability and quick scanning
Warm and natural → conversational without being casual
Helpful and supportive → guiding users without overwhelming them
A key principle was simple:
Say more with less—and say it clearly.
This translated into writing that gets straight to the point, avoids unnecessary complexity, and always prioritises user understanding.
Writing for a Global Audience
Designing for a global organisation brought an additional layer of complexity.
While we standardised on American English, the guidelines also accounted for:
Localization and cultural sensitivity
Avoiding idioms and colloquialisms
Using simple grammar and neutral language
Ensuring content is easily translatable
The challenge wasn’t just consistency—it was clarity across cultures and contexts.
From Principles to Practice: Writing in Interfaces
To make the guidelines actionable, we translated principles into real UI patterns.
Error Messages
Instead of vague or technical errors, we structured messages into:
What happened
Why it happened (if known)
What the user can do next
The focus was on being clear, calm, and actionable, especially in critical scenarios.
Forms and Inputs
Forms are often friction points, so clarity here is essential.
We emphasised:
Direct, descriptive labels
Helpful placeholder and helper text
Clear error feedback with guidance
Every word in a form should answer a simple question:
“What do I need to do here?”
Designing for Clarity at Scale
One of the biggest challenges was ensuring consistency across multiple products, teams, and use cases.
The guidelines were designed not just as rules, but as a framework teams could build on, encouraging:
Consistent terminology
Scalable writing patterns
Alignment between design, product, and engineering
This helped create a shared language across the ecosystem.
Key Takeaways
This project reinforced a simple but powerful idea:
UX writing is not just content—it is design.
The right words can:
Reduce friction
Build trust
Guide decisions
Improve overall usability
And in complex systems like Honeywell’s, they can make all the difference between confusion and clarity.
Want to read more?
Whether it's a quick chat or a deep dive, I'd love to hear from you.