Product Designer · Los Angeles Metro, CA
I design for complex B2B systems — CTI, sales enablement, and the workflows teams depend on every day. From user research to shipped interface, backed by data at every step.
Selected work
01
Call Flow Setting UI Redesign
Replacing an unreadable flowchart with a clearer, collapsible call-flow configuration experience.
02
Design System / Admin Component Cleanup
Turning 52 untracked grays into an accessible, reusable foundation for 100 Admin pages.
03
AI-Assisted Frontend Implementation
Using Claude Code and reviewed pull requests to move from design handoff into real frontend implementation.
04
A Booking App, Designed and Shipped Solo
A case study on designing, building, and shipping a full-stack booking app solo — from Supabase schema to a Row-Level-Security bug — using AI as a coding partner.
How I work
The best decisions are the ones you can defend with evidence.
I don’t start from the screen. I start from the people who deal with the current one every day — support teams, CS, the engineers maintaining it — and let their friction points set the priorities.
From there, I lean on real usage data — BigQuery, accessibility audits, and support ticket trends — to test whether a design decision actually worked, not just whether it looked right in Figma.
01 — Start with who’s stuck, not what’s broken
Example: Interviewed 5 Customer Success reps before touching the call-flow UI — the flowchart itself wasn't "broken," but the people maintaining and explaining it to customers were.
02 — Make the trade-off explicit, then choose
Example: Found 52 untracked gray values buried in the codebase. Rather than patching each one, chose to migrate to a semantic token system — more upfront work, but it closed the door on the same problem recurring.
03 — Close the loop with data, not opinion
Example: Support tickets tied to call-flow configuration dropped roughly threefold after the redesign shipped — the proof wasn't a stakeholder's approval, it was the ticket count.