Content was created by different roles
Designers, product teams and other contributors could all influence the words users encountered in an interface.
UX Writing · Content Design · Design Systems
Creating a shared approach to clear, consistent and user-centred product language across enterprise digital experiences.
01 · Context
As digital products expanded across the organisation, interface content was being created by people with different roles, writing experience and levels of UX knowledge.
A shared UX writing approach was needed to help teams make better content decisions and create more consistent experiences across products.
02 · Challenge
UX writing needed to work beyond individual screens and individual writers.
Designers, product teams and other contributors could all influence the words users encountered in an interface.
Without shared guidance, terminology, instructions and actions could vary between products.
The framework needed to be practical enough for people who were not professional UX writers.
The goal was not to prescribe every sentence. It was to give teams enough guidance to make better writing decisions independently.
03 · Approach
Instead of treating UX writing as a collection of individual copy decisions, the guideline organised recurring writing problems into principles and reusable patterns.
Define how product content should behave.
Provide guidance for recurring interface situations.
Show how the principles translate into actual writing.
Help teams apply the guidance consistently in their own products.
04 · Principles
The framework focused on a small set of principles that could be applied across different products and user journeys.
01
Make the next step clear.
Use specific language that helps users understand what they can do and what will happen next.
See an exampleUse “Save changes” instead of a generic “Submit” when that is the outcome.
02
Give users what they need at that moment.
Prioritise essential information and remove content that does not help users understand or complete the task.
See an examplePlace supporting detail beside the decision it explains, rather than at the start of the journey.
03
Use the same words for the same things.
Consistent terminology and interaction patterns make interfaces easier to learn and navigate.
See an exampleChoose one term for an action and use it across labels, instructions, and confirmation messages.
04
Give clarity where users are most likely to hesitate.
Pay particular attention to unfamiliar actions, errors, consequences, permissions and other moments where users may need additional reassurance or context.
See an exampleBefore a consequential action, explain what will change and whether the user can undo it.
05 · Coverage
Principles alone can be difficult to apply. The guideline translated them into practical guidance for common interface situations encountered by product teams.
06 · Reconstructed pattern
Error messages
Help users understand what happened and what they can do next.
Less helpful
More useful
Why
The message identifies what failed and gives the user a clear recovery action.
07 · Decision framework
What is the user trying to do?
What does the user need to know now?
What action should be clear?
What could cause hesitation or error?
Can anything be removed?
This shifts the conversation from
“What should this sentence say?”
To
“What does the user need in order to move forward?”
08 · User confidence
Content becomes particularly important when users hesitate: before committing to an action, after something goes wrong, when information is unfamiliar, or when the consequences of a decision are unclear. These moments often need more context than the happy path.
Before an action
What will happen?
During a decision
Which option should I choose?
After an error
How do I recover?
After completion
Did it work, and what happens next?
Design the content for the moment of doubt, not only the happy path.
09 · Scale
A guideline becomes useful when teams can apply it without needing a UX writer to rewrite every interface. The framework was designed to provide enough structure for consistency while leaving room for teams to adapt content to the context of their product and users.
10 · Contribution
My contribution focused on turning UX writing principles into practical guidance that multidisciplinary product teams could understand and apply.
This involved structuring guidance around recurring interface problems, defining writing principles, developing examples and considering how the guidance could support more consistent content decisions across digital products.
Key takeaway
The value of a UX writing guideline is not simply consistency in wording. It creates a shared way of thinking about content — helping teams consider user intent, context, clarity and action before deciding what appears on the screen.