New Research: Plain-Language Microcopy in Design Systems Lowers Drop-Off for Complex Flows

Design · 3 min read

Researchers partnered with three companies to run AB tests across onboarding and checkout flows, swapping system-level component copy (button labels, helper text, error messages) from technical wording to plain-language, action-oriented variants. The plain-language copies were curated by communication specialists and validated through quick comprehension tests with diverse user groups. Across over 60,000 sessions, plain-language variants improved completion rates and reduced the need for help-center lookups.

The study highlights the role of design systems as the canonical source for microcopy. When copy is embedded in components and tokens, product teams can apply consistent, tested language across products. The researchers recommend versioned copy tokens, guidelines for localization-aware phrasing, and a feedback loop that captures edge-case language from live support interactions for token updates.

Practically, the paper suggests design systems should include a 'readability' score field, context cues for when to show expanded helper text, and personas-based copy variants for audiences like sighted users, screen reader users, and people with cognitive disabilities. Designers interviewed in the study reported fewer cross-team disputes over language once a tested token was available.