Establishing UX writing foundations for a multi-product design system
Design system
Consistency at scale
Overview
As our team managed multiple products, maintaining consistency became increasingly challenging. To support collaboration and scale efficiently as a small team, we began establishing a design system that included components, patterns, and content foundations.
My role & Design focus
Owned UX writing foundations for the design system, defining Japanese tone of voice and scalable writing rules to ensure consistent content quality across products in a multilingual team.
Outcome
Established clear and consistent writing standards
Enabled smoother collaboration within a multilingual team
Background
How can we work efficiently across multiple products with a small team?
Problem
As the business expanded, inconsistencies in tone, grammar, and writing style began to appear across platforms. Content was being produced by designers, content writers, and developers - each with different writing habits and levels of linguistic knowledge.
Solution scope
To resolve these inconsistencies and contribute to our design system, I independently created 2 core content foundations:
Tone of voice guidelines
Grammar & Mechanics rules
Goal
Ensure that Japanese products maintain a consistent brand voice and high writing quality while enabling efficient collaboration within a multilingual team
Tone of voice
Defining a tone of voice grounded in brand values
Tone of voice is not only part of UX writing - it is the brand. I translated our brand values into practical writing principles with examples.
Because tone in Japanese shifts depending on context (politeness, friendliness, formality), I created tone variations for each platform:
Website (base tone)
Promotion (email & social media)
Customer support
This enabled non-Japanese teammates to maintain quality even without deep cultural or linguistic knowledge.
Grammar & Mechanics
Making Japanese writing consistent and accessible for a multilingual team
Japanese grammar differs fundamentally from English. Localization is not just translation - it requires structural and stylistic adaptation.
As the only Japanese team member and a writing specialist, I created a shared rule set that helped the entire team (including non-Japanese teammates) produce consistent and natural content for Japanese users.
The guide included
Character types & spacing
Punctuation rules (full-width vs half-width)
Number format (date, time)
Common mistakes and corrected examples …etc.
Guideline: Punctuation & Symbols
Documentation & Team integration
Turning guidelines into a shared team resource
To make the guidelines actionable and accessible to the whole team, I created a documentation page on our team’s Confluence space.
This helped ensure consistency and allowed any team member (even non-Japanese or new members) to produce quality Japanese content without needing direct Japanese language support.
Confluence: Guide page top
Retrospective
Creating a writing system reinforced several principles that now guide my design approach:
Clarity is scalable. When rules are explicit and easy to use, quality becomes repeatable.
Language is part of the design system. Consistent microcopy shapes perception just as much as colors or components.
Good documentation empowers teams. A well-structured guide bridges skills, languages, and roles - especially in multilingual teams.
Cultural nuance matters. Japanese tone, politeness, and writing conventions strongly influence trust and usability.
This experience strengthened my interest in design systems and showed me how language, structure, and UX design come together to create cohesive product experiences.
