-
Notifications
You must be signed in to change notification settings - Fork 16
Create ux-writer-role.md #202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Susanne254
wants to merge
3
commits into
main
Choose a base branch
from
UX-writer-role
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
102 changes: 102 additions & 0 deletions
102
docs/guidelines/language/support-and-resources/ux-writer-role.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,102 @@ | ||
| --- | ||
| sidebar_position: 3 | ||
| sidebar_label: UX writer role | ||
| title: UX writer role | ||
| doc-type: 'banner' | ||
| component-tabs: [''] | ||
| no_single_tab: true | ||
| description: UX writers shape the language that bring our digital products to life. Through clear, consistent and accurate microcopy (the small, functional pieces of text within a digital interface that guide, support and reassure users), UX writers help users move through complex workflows with ease. | ||
| --- | ||
|
|
||
| # | ||
|
|
||
| ## UX writer role | ||
|
|
||
| UX writers strengthen usability, reduce friction and ensure every interaction across our software feels supportive and human-centered. | ||
|
|
||
| They shape in product language that supports a clear, seamless and intuitive user experience. | ||
| They create user interface microcopy such as buttons, labels, tooltips, warnings, onboarding and chatbot messages to guide users through workflows. | ||
|
|
||
| They see UX writing as focused on interactions, are part of the design team and coordinate with multiple stakeholders. | ||
|
|
||
| ## UX writing is designing | ||
|
|
||
| UX writing is an integral part of design, not an afterthought. Writers participate throughout the design process, from early research to final implementation, shaping how users understand and interact with the product. | ||
|
|
||
| Writers collaborate closely with UX/UI designers, researchers and product teams to ensure wording supports interactions and functionality. This partnership extends to developers, who help implement terminology and microcopy accurately. | ||
|
|
||
| User research provides the foundation: understanding user terminology, mental models and pain points ensures language matches expectations. Through ongoing iteration, validated by usability testing, analytics and qualitative feedback, UX writers continuously refine the effectiveness of their wording. | ||
|
|
||
| ## UX writing scope and collaboration | ||
|
|
||
| As part of the design team, UX writers partner with other specialized teams for content. This division of responsibilities ensures each content type receives specialized expertise while maintaining consistency across the user experience. | ||
|
|
||
| ### Marketing and brand teams | ||
|
|
||
| Handle promotional language, persuasive messaging and brand storytelling that aims to engage rather than guide users through tasks. | ||
|
|
||
| ### Technical writing teams | ||
|
|
||
| Own comprehensive user documentation, detailed tutorials, help articles and extended product explanations. | ||
|
|
||
| ### Legal teams | ||
|
|
||
| Are responsible for disclaimers, terms and conditions, privacy policies and all legally binding language. | ||
|
|
||
| ### Content strategy and design teams | ||
|
|
||
| Manage narrative content, thought leadership and storytelling that doesn't directly support in-product user actions. | ||
|
|
||
| ### Development teams | ||
|
|
||
| Support writers to understand the technical processes behind the software to “translate” this to suitable and voice-aligned UI wording. | ||
|
|
||
| ## Design systems | ||
|
|
||
| Design systems provide components, shared patterns and guidelines for consistent product language. They are used when writing microcopy, validate terminology before implementation and apply established patterns for consistency. | ||
|
|
||
| ### What’s included | ||
|
|
||
| * Voice and tone framework | ||
| * Component guidelines (menus, dialogs, buttons, warnings, notifications) | ||
| * Standardized terminology and approved terms | ||
| * Content templates and patterns | ||
| * Common writing issues reference | ||
|
|
||
| ## UX writing governance | ||
|
|
||
| ### Ownership | ||
|
|
||
| Senior UX writers maintain the content design system and approve terminology changes. The team owns the style guide, terminology database and component guidelines. | ||
|
|
||
| ### Review process | ||
|
|
||
| Teams submit content proposals to the UX writing team. Proposals are reviewed and evaluated for consistency, accessibility and brand alignment. Approved changes are documented in the design system and communicated to relevant teams. | ||
|
|
||
| ### Quality standards | ||
|
|
||
| All product microcopy must follow the style guide and use approved terminology. Teams conduct content reviews during design critiques and before release to ensure compliance. | ||
|
|
||
| ### Maintenance | ||
|
|
||
| The design system is dynamic and reacts to changing requirements, feature requests, etc. Reviews incorporate user research findings, team feedback, product evolution and accessibility updates. Ad-hoc updates occur when critical issues are identified. | ||
|
|
||
| ### Conflict resolution | ||
|
|
||
| When teams disagree on terminology or microcopy, UX writers facilitate a review session with stakeholders. Decisions are based on user research and brand guidelines. If consensus cannot be reached, the UX writers make the final decision. | ||
|
|
||
| ### Onboarding and training | ||
|
|
||
| New UX writers should complete an onboarding program covering the style guide, design system and review processes. Ongoing training should also include workshops on best practices. All UX writers should have access to self-paced learning resources. | ||
|
|
||
| ## UX writing in agile projects | ||
|
|
||
| Integrate UX writing throughout all Scrum phases to allow product language to evolve with the design. | ||
|
|
||
| * Sprint planning: Identify content needs and terminology early in ideation | ||
| * Daily standups: Stay aligned on interaction changes that affect microcopy | ||
| * Refinement: Collaborate with designers and product owners on wording decisions | ||
| * Development: Ensure accurate implementation and consistency | ||
| * Retrospectives: Refine the writing process based on team feedback | ||
|
|
||
| Continuous collaboration prevents terminology gaps, reduces rework and improves clarity throughout the product. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.