I design products.
I think in systems.
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 and always asking how one decision ripples across the whole.
How I Approach Work
Good design isn't just how something looks. It's how well you understood the problem before you touched a tool.
I break things down until they're clear
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 stay in the room with engineers
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.
Every detail has a downstream effect
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.
I think at the product level
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.
Selected Work
Figma Integration: Replacing Embeds with a Real Design Data Model
How I designed a structured way to connect Figma files to Knapsack documentation, replacing heavy iframe embeds with stable references to design content and creating a direct link between Figma components and their coded counterparts.
Cloud Authoring: Replacing PR Handoffs with a Real Publishing Workflow
How I designed a branch-based authoring workflow that gave non-engineers the ability to publish directly without asking engineers to give up control.
Vivid Seats App 3.0: Replacing a Purchase Flow with a Reason to Return
Redesigning a ticket marketplace app to drive engagement beyond the moment of purchase
Regulation Manager: Replacing Per-Team Compliance Builds with a Shared Requirements Layer
How I designed an internal tool that gave the legal team a structured way to manage compliance requirements, so individual product teams didn't have to rebuild compliance UI from scratch every time a new law passed.
Areas of Expertise
Design Leadership
- Team building & mentoring
- Design team standards
- Cross-functional collaboration
- Stakeholder communication
User Experience
- Information architecture
- User research & testing
- Journey mapping
- Accessibility
Visual & Systems
- Design systems
- Native app design
- Responsive web design
- Component libraries