Episode #70: Writing UX Copy Around User Needs with Grace Berry

Grace Berry's route to UX copywriting began with English literature, cosmetology, salon work, and freelance writing. She initially studied English at Temple University with teaching in mind, then earned a cosmetology license and spent years in an industry she describes as a large user-experience experiment. Salon work required empathy, personal communication, and custom solutions shaped through choices about color and texture.

When the pandemic interrupted that work in 2020, Grace increased her freelance writing and repeatedly encountered terms such as user experience, UX copy, and microcopy. Curiosity led her into UX and visual design study. She discovered that her writing background could work alongside interface design, then took freelance projects for small businesses, ecommerce, and decentralized finance. A contact later brought her into a cable provider's loyalty program, where the work combined engaging content with clear instructions for redeeming benefits.

What you'll learn

• How salon work helped Grace practice empathy and custom problem solving

• Why a written source of truth reduces cross-functional confusion

• How hierarchy keeps user needs visible when stakeholders have different priorities

• Why accessible conventions for details such as dates belong in a content style guide

• How to balance line-level precision with the coherence of an entire page

Build alignment from a written source of truth

Grace's work begins with tickets in Jira, conversations with designers, and a review of how copy and interface must support each other. Stakeholder meetings test whether the language represents the product correctly and aligns with broader marketing and UX strategies. Legal reviews can require examining copy line by line to avoid creating risk. The role is collaborative because approved words must satisfy user needs while moving through design, product, marketing, legal, and development.

Her practical recommendation is to establish a written source of truth. First, the writer becomes clear about the plan. Then writer and designer agree on how text and layout work together. They take that shared direction to stakeholders and continue alignment as the work moves toward implementation. A documented decision gives each group something concrete to inspect instead of relying on different memories of a meeting.

Copywriters may not always participate in development conversations, since implementation can be treated as visual design work after text is approved. Grace stays available to support designers when the built result creates friction. Her knowledge of written accessibility can help explain why a choice matters, while a shorter phrase or lower character count can sometimes preserve meaning and fit the technical constraint. Alignment is not rigid attachment to one sentence. It is a shared understanding of what the sentence must accomplish.

Put user needs above the fold

Grace's central hierarchy principle is blunt: people do not reliably read every word. The most important information should appear near the top, and the order of content should follow what the user needs to do. This is particularly important in cross-functional work because every group brings a valid but different priority. Marketing may want a promotion emphasized, product may focus on a feature, and developers may care about implementation constraints.

The UX writer's responsibility is to keep the user's task visible. A person should be oriented to where they are, what they can do, and what information matters before encountering lower-priority additions. This does not mean refusing every business request. It means explaining why a promotional message cannot displace the instruction or context required to complete the experience.

Grace points to content style guides as another safeguard. Her organization has specific conventions for dates because numeric date formats can be interpreted differently across cultures. Writers can miss such details when they do not realize a scenario has an established rule. A comprehensive guide reduces guesswork, but only if contributors know to consult it and discuss exceptions. The guide should make repeat decisions easier, not replace conversation.

Her examples of LinkedIn and Microsoft Teams show how small labels and icons can create recurring friction. Saved items in LinkedIn were difficult for her to retrieve on mobile. In Teams, icons and actions for adding someone to a group chat did not match the path she expected. These are not merely aesthetic complaints. They demonstrate that interface language includes labels, symbols, placement, and the sequence a person must infer.

Protect the whole experience from tunnel vision

Grace identifies detail orientation as both necessary and risky. Correct grammar, sentence construction, accessibility, and consistent conventions are non-negotiable. Yet a writer handling many products can spend too long chasing two awkward words on one button and lose sight of the page around them.

Her lesson is to review at two levels. At the component level, ask whether the CTA, label, or instruction is accurate and usable. At the experience level, check whether information is repeated, whether sections make sense together, and whether the page supports one coherent task. A locally polished phrase can still fail if it weakens the hierarchy or conflicts with nearby content.

Grace also encourages conversations with people beyond one's immediate professional circle. Listening to workers and strangers in everyday settings expands a writer's understanding of professions, routines, and ways people interpret information. For UX work, that habit supports empathy without pretending that one writer's perspective represents every user.

Listen to Episode #70 for Grace Berry's full conversation about hierarchy, accessibility, collaboration, and detail in UX copywriting.