I build the conditions for teams to do their best work.
My role as a design leader is to create clarity where there is ambiguity, develop people into stronger decision makers, connect design to delivery and business outcomes, and stay close enough to the work to raise the quality bar when it matters.
I believe strong design leadership is not about making every decision. It is about giving teams enough context, clarity and trust to make good decisions independently while knowing when senior judgment needs to enter the work.
I have built and led teams at very different scales, from focused product squads to a 25-person design organization. I look at the problem first: roadmap, complexity, timeline, skills and the level of ownership the work requires. Then I shape the team around it.
Mentoring has been a constant throughout my career. I have intentionally hired entry- and mid-level designers when the role and support model made sense, then used coaching, shadowing and critique to help them develop stronger judgment and greater independence.
Some of the hardest product problems are not design problems in isolation. They are conflicts between user needs, business or policy requirements, stakeholder expectations and technical realities.
My approach is to surface those constraints early, give each group a voice in discovery and create shared decision points instead of sequential handoffs. That is how I rebuilt trust between workers, stakeholders, design and engineering at CWS-CARES, and how I involved banking executives directly in shaping the Western Alliance product direction.
As teams grow, quality has to move from individual oversight into the system. I use design principles, reusable components, critique, cross-functional working sessions and clear ownership to create consistency without slowing teams down.
I do not need to own every artifact to stay close to craft. I get hands-on where my involvement creates leverage: defining a difficult interaction model, restructuring information architecture, facilitating a critical workshop, shaping a design system, reviewing a high-risk flow or helping a designer elevate a solution.
When delivery, team performance and client confidence are at risk at the same time, I focus first on what cannot fail, then create the support and communication needed to stabilize the work.
During the Bridge Bank expansion, that meant temporarily covering a delivery gap while coaching a designer and protecting the existing NoteFinance commitment. The full case shows how execution rebuilt client confidence during a commercially sensitive expansion.
Read the Western Alliance pressure test →I connect experience decisions to the larger system around them: operating cost, delivery speed, scalability, adoption, client trust and future opportunity. That mindset helped expand Western Alliance from one initiative into a broader partnership and helped transform CWS-CARES from repeated rework into a more scalable delivery model.
Strong teams. Better decisions. Products that scale.
The measure of my leadership is not how much work carries my fingerprints. It is whether the organization can repeatedly turn complex problems into high-quality product outcomes.
See how this leadership model shows up in the work.
CWS-CARES · Pennsylvania DHS · Western Alliance
Explore case studies →