02 / selected work — 2019–2026
03 case studies
01 — product ux at scale
2025
Contributed to a 15% reduction in research time spent finding information and a 20% decrease in chatbot-related usability tickets by improving conversational flows, readability, and information discoverability.
01 — product ux at scale
2024
Re-architecting the UX of a mission-critical platform during a full AngularJS → React migration. Same workflows, no retraining, better outcomes.
03 — design systems
2024
Establishing a single source of truth across three product teams that had been designing past each other for four years.
04 — research-driven ux
2024
Reworking a notification pattern the team had stopped noticing; a research-driven UX change that lifted task completion 20%.
05 — B2B/B2C SaaS ux
2020
Usability testing a live-recording B2B/B2C SaaS mobile app to fix first-impression drop-off rates.
04 / the approach
04 principles
01
Ask questions earlier than feels comfortable.
Most design problems are actually problem-definition problems. I spend the first stretch of a project interviewing people, reading the tickets no one wants to read, and turning ambiguity into something clear and actionable.
02
Design the system, not just the screen.
A good component is invisible; a good system is inevitable. I work at the token, pattern, and page level, so that what gets shipped holds up as the product grows past the team that made it.
03
Talk to engineers like partners, not clients.
The best design decisions I've made have come out of workshop sessions with front-end leads. I build in constraints from the beginning so the handoff isn't a handoff, it's just the next step.
04
Measure what the research promised, then tell the truth.
If a hypothesis got me the green light, that hypothesis gets tested after launch. This is how 20% task-completion lifts get written down instead of rounded off into resume copy.
05 / contact
available · SPRING/summer 2026






