Microcopy Template for Product Managers

If your team has a UX writer or content designer, they own it. If not (most teams do not), the PM and designer share ownership. The PM defines the terminology glossary and ensures consistency. The designer writes screen-level copy as part of the design deliverables. Engineering reviews for implementation feasibility (e.g., string length constraints).

Start with the Terminology Glossary. Translators need context, not just strings. For each term, provide the definition, the UI context, and the maximum character length. Store all microcopy in a string resource file (i18n), never hardcoded in components. Mark strings that should not be translated (brand names, feature names). The [design system documentation template](/templates/design-system-documentation-template) can include localization guidelines alongside component specs.

Pick one and use it everywhere. Sentence case ("Create project") is the current industry standard. It feels more natural and conversational. Title Case ("Create Project") is common in enterprise software. The choice matters less than consistency. Record the decision in the Copy Conventions section and enforce it in design reviews.

A tooltip should be one sentence, under 15 words. If you need more than that, the UI element needs a redesign, not a longer tooltip. Tooltips are for quick hints ("Archive moves this project out of your active list"), not documentation. If the feature needs explanation, link to a help article instead. ---