Hiiii. I'm Maddy, a content designer in Raleigh, NC. The short version of what I do:
I build the content systems other people's work runs on.
The systems exist because I care (probably an unreasonable amount) about how every string reads. But one person's care doesn't scale... Systems do.
My copy standards are checked on every PR. My AI tools are what PMs, designers, and engineers draft with. And I know the product from both sides—I started as a Pendo customer; now I ship its UI copy.
The release-docs pipeline I built is what PMs now draft and approve docs through, and I build the evals that decide whether AI output is actually good.
I ship copy in code. Pull requests straight to the frontend and component repos, everything from a one-line sentence-case fix to a 2,300-line overhaul of the design system's copy guidance. Those guidance files are now the declared source of truth for the automated copy checks that run on every frontend PR.
I push fixes upstream. Help docs shouldn't be a bandaid for a confusing interface. When the team that manages our in-app guides planned 20 more help-focused guides, I flagged which "guide opportunities" were actually product problems better solved with UI copy fixes. The team's process changed to screen for that.
I turn judgment into systems. Custom AI skills, a machine-checkable copy ruleset, a framework for when a copy fix is a PR vs. a ticket. Good standards shouldn't need me in the room to work. Two of the custom GPTs I built are among the ten most-used at the company.
all pages