I make complicated products make sense.
Instant clarity. Honest language. Systems that scale.
Content design for the products with fine print — AI, licensing, security.
Words for every kind of complicated.
Pick a problem. There’s a case study for it. Interfaces below are recreations — the words are what actually shipped.
Skip ahead — read the full portfolio →
Making AI image generation feel fair, not sneaky
Getty’s AI generator lets you start creating with photos you haven’t licensed yet — on a site that sells licenses. I wrote the copy that keeps the eventual bill honest, visible, and never a trap.
Telling users the AI might change their picture
The most popular download option ran AI enhancement that could subtly alter an image — smooth a texture, shift a face. I rewrote the download copy from selling to describing, both options at equal length.
Writing the “no” for a security AI
When an AI assistant inside a security console refuses, fails, or asks permission, the wording decides whether admins keep trusting it. I wrote all thirteen of those messages.
Getting seven products to speak one language
Seven admin consoles had drifted into seven dialects — three different names for the same thing. I catalogued ~6,000 terms and built the glossary to unify them, including an AI-assisted pipeline that failed twice before it worked.
Measuring whether the AI is actually good
Everyone knew the AI support assistant was “sometimes wrong.” Nobody could say how, how often, or in which ways. I built the evaluation framework that answers exactly that — and caught the judge AI hallucinating mid-audit.
The agency years, preserved
Experience maps, personas, and content strategies for Carbon Trust, Bangor University, and Concert Properties — kept because they still argue well.
There’s also a strategy & leadership shelf — setting direction, building practices, democratizing experimentation. Four more studies →
The receipts.
Every number traceable to a project above.
I’ve been teaching AI to talk since 2018.
It started with scripting a chatbot’s lines, six years before the wave. These days it’s response systems and runtime contracts. Same lesson — smarter student.
How I work.
1. Audit the chaos
Every term, every screen, every claim — captured exactly as shipped, before fixing anything.
2. Build the system
Glossaries, taxonomies, response classes, frameworks — the structure that decides which words can exist.
3. Ship the honest version
Copy that tells the truth about what the product does — especially when the truth is complicated.
4. Leave the system behind
Glossaries, frameworks, runtime contracts — built to keep working after my engagement ends, and socialized up to the executives who fund them.
This is the short version.
The full portfolio goes deep: eleven case studies with interactive exhibits, an archive of the agency years, and a ledger of everything since 2010.
Read the full portfolio →Roughly a 12-minute read. The good details live there.