I design for complexity. Not the kind that impresses designers — the kind that frustrates users.

I became a designer because i’m obsessed with one specific problem: how do you take something genuinely complicated and make it feel simple to the person who needs it most?

Ten years of B2B design — four of them at Unum — have given me a very specific specialty: making complicated things navigable for people who don't have time to be confused — HR professionals managing compliance law, benefits administrators handling complex products, and field teams explaining insurance to clients who just want to understand what they're covered for. The subject matter changes. The core design problem doesn't.

SELECTED WORK

  • Designed conditional UX logic across 3 HRIS platforms (Workday, UKG, ADP) with dual deployment modes and a mid-project pivot that validated the modular architecture. B2B SaaS product design.

  • Built an enterprise component library from scratch: XD → Figma migration, component governance, Do/Don't documentation, and a developer-first handoff approach that eliminated manual redlines.

  • Designed end-to-end experience for a 6-episode webinar series — 26,290 registrants, 39% avg attendance rate. Journey map covering pre/live/post touchpoints across 5 deliverable types.

  • Visual identity and template system for a newsletter that reached 23,870 subscribers — 3.4× its goal — and became an organic sales enablement tool for field partners.

  • 21-day multivariate research sprint: 5 content hypotheses tested in parallel with live data. Data-driven pivots. YPP monetization eligibility in under 14 days. 0-to-1 product design.

I think in systems before I think in screens

〰️

I think in systems before I think in screens 〰️

MY PROCESS

Before I design a component, I want to understand how it fits into everything else. Before I design a page, I want to map the journey that brought the user there and where they're going next.

That's not perfectionism — it's how I avoid solving the wrong problem elegantly. A design system no one uses is just organized clutter. A template no one follows is just a pretty file. I build things that work downstream: for the developer implementing the component, the designer who inherits the file, and the user encountering it six months after launch.

OUTSIDE THE WORK

When I'm not in Figma, I'm usually thinking about the same things through a different lens — how information is organized, how stories are told, how systems remain coherent over time. Apparently, it's just how my brain works.

CURRENTLY

Open to senior UI/UX/product design roles — preferably in B2B, enterprise software, or mission-driven organizations where design has a real seat at the table.

EXPERIENCE