My title has always been in design, but my thinking has never stayed there. I work at the intersection of design, engineering, and product — comfortable in every conversation, always asking how one decision ripples across the whole.
"Good design isn't just how something looks. It's how well you understood the problem before you touched a tool."
When a problem feels overwhelming, that's usually a signal the framing is wrong. I slow down, map the system, and find the one thing that actually matters. That clarity tends to unblock everyone around me too.
I've spent enough time in codebases and sprint reviews to understand how engineers think. I write specs they can actually use, and I ask questions that don't waste their time. That trust makes a real difference in what ships.
A small UX decision can create a data modeling problem. A component choice can constrain a product decision six months later. I try to hold that context while still moving fast — and speak up when something feels off.
Even when I'm deep in a flow or a component, I'm thinking about the broader experience and the business behind it. Design is where I work. Product is how I think.
A full redesign of the ticketing experience — rethinking not just the UI but the underlying information architecture to simplify how millions of fans find and buy tickets.
Restructured the core event detail page around actual user intent rather than assumed intent — a diagnosis-first approach that led to measurable improvements in conversion.
Took a compliance tool that frustrated everyone who touched it and rebuilt the workflow system from the ground up — clearer, faster, and actually usable without a training manual.
I'm always happy to talk — whether that's a potential role, a collaboration, or just a conversation about design and where it's heading.