About

Principal Product Designer for Complex Systems

I'm a Principal Product Designer who partners with product leaders and executive teams to turn complex business challenges into clear product direction and trusted experiences across SaaS, FinTech, Healthcare, and AI-driven systems.

Based in Washington DC, I've spent my career working where ambiguity meets scale—setting the vision, aligning teams, and carrying the work through to production.

Here is what you can rely on me for:

  • Own the outcome. I set direction, craft the experience, and follow it all the way to production. I know when something isn't right, and I can name the reason before any research says so.
  • Simplify the complex. I turn business goals, user needs, and complex data into intuitive products that reduce churn and get users onboard faster. I talk to users directly and let their contradictions reshape my thinking.
  • Build for the long term. I architect 0-to-1 visions and scalable design systems that cut development cycles, most recently reducing launch cycles from 3 months to 3 weeks. I optimise existing systems as much as I build new ones.
  • De-risk the unknown. I navigate multi-stakeholder environments and strict regulatory frameworks so you can innovate without breaking things. I've built where the brief was incomplete and the roadmap was a guess. I ship, learn, and iterate.
  • AI as infrastructure. I set the boundaries AI generates within, then validate the output. I use AI to compress concept-to-test cycles from weeks to days and design interfaces users actually trust, where consistency and reliability matter as much as innovation.

Available for: Principal Designer roles • Strategic Design consulting • Fractional Design Leadership

How I Use AI in My Design Work

The shift I care about is not using AI to go faster on individual tasks. It is setting up the system so quality stays consistent across everything the team produces.

Research

  • I feed interview transcripts, survey data, and behavioural analytics into Claude Projects to spot patterns I might otherwise miss
  • I create the structure myself first -- AI drafts from that framework, not from nothing

Ideation

  • I use AI to brainstorm IA and flows, then pressure-test the options before committing
  • I connect Figma to Claude directly, turning prompts into flow diagrams in FigJam and having conversations with my design files to audit structure and brainstorm variations

Prototyping

  • I generate layout variations in Figma Make straight from our design system tokens, so I can test fast without breaking consistency
  • When I need something working quickly, I build components or whole pages directly in Claude Code and skip Figma entirely

Design System

  • When a system exists, I connect tokens end to end so the prototype, the spec, and the code all reference the same values
  • When starting from scratch, I use AI to generate and iterate on the system itself
  • The tokens repo doubles as a playground where designers can experiment before integrating into production

Accessibility

  • I check contrast, touch targets, and focus order in Figma using Stark
  • For complex screens I share designs with Claude to validate WCAG AA compliance against my tokens

Persistent Workspace

  • I run a Claude Project as a standing design workspace, with platform context, component inventory, and design rules loaded once
  • Saved shortcuts handle recurring work like spec generation, token checks, and accessibility audits

Specification & Handoff

  • I generate structured PRDs from prototypes covering states, acceptance criteria, edge cases, and behaviour notes, so engineering builds from a clear source of truth

Current Stack: Claude Code · Figma · Figma Make · Stark · GitHub

Let's Work Together

Interested in collaborating on your next project?