Case Study: Writing VENU

Role: UX writer and content designer (solo project) · Scope: Product copy, terminology, error states, user guide · Tools: Figma, Astro/Starlight, Vale, Claude Code

Why this project exists

VENU is a speculative ticketing product I designed in Figma, with a user guide and release notes written for that prototype. I published it because the healthcare apps I worked on in Oracle Design are not mine to show. The content problems are the same ones I solve at work: naming things consistently, breaking a purchase into steps a stranger can follow, writing the screen that appears when something goes wrong, and telling people what changed when the product moves.

Building the prototype first was the point. Writing UI copy against a real layout forces decisions that a copy deck lets you postpone — how long a button label can be before it wraps, what the empty Resale balance says before a user has sold anything, whether “Transferred” and “Sold” are distinct enough to be separate tabs.

What’s here

User Guide Task documentation for the prototype: account setup, search, purchase, and resale.

Release Notes Launch notes for the prototype, written in the register a shipped product would use.

Try the Prototype