From Craft to Systems to Leadership

I started out designing interfaces and refining interactions. The work I cared about most was making complex things feel obvious: a checkout flow that didn't lose people, a dashboard where the important number was the first thing you saw.

I worked across product design and product management, which meant I was writing briefs one week and prototyping the next. Usability testing, visual design, working shoulder-to-shoulder with engineers to get things shipped.

That foundation still shapes how I work. But I also hit a wall. Individual screens weren't the hard part anymore. The hard part was keeping dozens of teams aligned on the same experience.

As my scope grew, I kept seeing the same problems repeat: teams rebuilding the same UI patterns, inconsistent decisions across product areas, research insights that never made it into the next PRD.

I shifted from designing features to building the infrastructure that makes good design repeatable:

• →Design systems that gave teams shared components instead of one-off screens
• →UX processes teams could actually follow, not just document
• →Frameworks for research, prioritization, and knowing when something was ready to build

The goal wasn't efficiency for its own sake. It was giving teams a shared baseline so they could move faster without reinventing the wheel every sprint.

Systems work naturally pulled me into people work.

I started leading designers and UX leads. Mentorship, team structure, figuring out who owns what when the org chart doesn't map cleanly to the product. What I focused on:

• →Clear ownership so designers knew what they were accountable for
• →Coaching people to think about strategy, not just the next deliverable
• →Feedback loops that were direct but not brutal

Scaling design turned out to be as much about people as components. Aligned teams with clear goals beat perfect Figma files every time.

These days my work sits closer to product and business strategy than individual screens.

I partner with product and engineering leadership to:

• →Set experience direction that holds up over multiple release cycles
• →Influence roadmaps based on user evidence, not just loudest voice
• →Introduce decision frameworks teams can reuse without me in the room

Recent work has tied UX to things you can measure: product quality, team velocity, fewer handoff gaps across a platform with dozens of modules.

Success at this level means the teams ship well when I'm not in the meeting. That's the bar.

A few things I keep coming back to:

• Clarity creates momentum

  When goals, roles, and decisions are explicit, teams stop spinning and start shipping.

• Design is a team sport

  The best work happens when product, engineering, and design share ownership of the outcome.

• Systems enable scale

  Repeatable processes beat heroics. One-off fixes don't survive the next reorg.

• Facilitation drives alignment

  Most misalignment is a meeting problem. Get the right people in the room with the right inputs.

• Growth is intentional

  I invest in coaching because the team gets better, not because it's on a checklist.