Build
I stay close to the work. I design, prototype, critique, and code when it helps move the product forward.
Grow
I connect design decisions to customer behavior, product metrics, and the health of the business.
Enable
I hire, coach, and create ownership so designers can make strong decisions without depending on me.
Evolve
I adopt new technology early and fold it into how teams understand, design, prototype, and build.
Ambiguity is usually the real design problem.
Most important product problems don’t arrive as clean briefs. They arrive with competing customer needs, business priorities, technical constraints, incomplete data, and different opinions about what matters.
- What problem are we actually solving?
- Why does it matter to the customer and the business?
- How will we know if we made it better?
From there, I use customer insight, prototypes, data, and storytelling to create a direction that product, engineering, data, and leadership can rally around.
Shipping the design is not the outcome.
I want to understand how the business works, which customer behavior matters, and which metric tells us whether the experience is actually doing its job. That lets design participate in prioritization and strategy, not just execution.
Leadership doesn’t distance me from the product.
I still get into the details when that is the highest-leverage thing to do. Sometimes the fastest way to create alignment is not another meeting or presentation. It is something people can see, touch, and react to.
- Prototype to create conviction.
- Use craft judgment to raise the quality bar.
- Work directly with engineering around real constraints.
- Code when building is faster than explaining.
- Step back once the team has clarity and ownership.
Build designers who don’t need me in every decision.
My role isn’t to become the person who approves every pixel. It is to give designers context, ownership, feedback, and confidence to make strong decisions themselves.
Hire
Look for complementary strengths, craft, curiosity, product judgment, and ownership.
Context
Give designers the why, business model, customer problem, constraints, and success metric.
Ownership
Give designers meaningful problems to solve rather than prescribing solutions.
Critique
Raise quality through clear feedback without taking the work away from the person doing it.
Growth
Create progressively harder opportunities that help designers build their next capability.
Trust
Step back when the designer has enough context and confidence to run.
Design is a team sport.
The strongest outcomes rarely come from design working alone. I spend a lot of time creating shared context, making decisions visible, and helping teams disagree productively.
Product
Align on the problem, priority, tradeoffs, and success metric.
Engineering
Bring technical partners into the conversation early instead of handing off finished designs.
Data
Define what success means before launch, not after the experiment comes back.
Leadership
Communicate through customer value, business outcomes, and tradeoffs.
Design
Create a high bar without turning critique into approval theater.
Technology has always been part of my design material.
I’ve coded prototypes throughout my career and adopt new tools early when they help me understand a problem, communicate an idea, or move from concept to reality faster. AI is now embedded throughout how I work.
Understand
Research synthesis, pattern discovery, competitive analysis, and finding signal faster.
Think
Explore product hypotheses, edge cases, flows, and alternative approaches.
Make
Rapid prototypes, conversational experiences, functional concepts, and code.
Scale
Documentation, design systems, repeatable workflows, and faster iteration.
Lead
Sharper narratives, faster alignment, and clearer decision-making.
The work should prove the philosophy.
A few examples where business outcomes, hands-on product judgment, team leadership, and cross-functional influence came together.