Approach / Leadership

Design playbook

How I think about design leadership, team collaboration, and cross-functional partnerships — a personal operating model.

My philosophy is built on Simplexity — making complexity feel effortless and natural. Design isn't decoration; it's logic, empathy, and the pursuit of a more usable world.

I am a structuralist by nature. I keep information organized, intentional, and tightly structured to minimize cognitive load. I treat async collaboration as a superpower: it gives people time to think, space to focus, and the freedom to do their best work without noise.

Leadership philosophy

Design how we communicate, not just what we make.

My role as a design leader isn't just to set visual direction — it's to design how we communicate, collaborate, and make decisions. The design capabilities I support sit at the intersection of business strategy, cross-product experience, and narrative clarity. That means our work often spans multiple products, teams, and time horizons.

In that environment, clarity and transparency aren't nice to have — they're how we scale. When context is shared and intent is clear, teams move faster, make better trade-offs, and design experiences that actually work end to end. Transparency is itself a form of design.

Working with the team

What you can expect from me.

I create opportunities for you to own meaningful, high-leverage problems. I provide clear, timely, and actionable feedback — not vague opinions. I actively support your growth as a designer, whether that's craft, systems thinking, or leadership readiness. I won't micromanage execution — but I will care deeply about intent, quality, and impact.

Day-to-day we work async-first by default. 1:1s are your space to bring priorities, challenges, or early ideas. Decisions are made with early input from diverse perspectives — and the why is always explained, so decisions scale beyond a single moment.

When information flows freely within a team, most problems naturally find their way to resolution.

Cross-functional partnerships

Design as the glue and the catalyst.

Exceptional customer experiences aren't owned by a single team — they're built when Product, Engineering, GTM, and Design operate as one system around a shared business goal. My role is to ensure design acts as both the glue — aligning intent, decisions, and user experience across functions — and the catalyst — accelerating outcomes by turning strategy into coherent, high-leverage experiences.

For Product: system-level experience frameworks, cross-product flows, and critical entry points — validating assumptions early and strengthening decision quality. For Growth: lifecycle goals translated into measurable experience improvements — reducing time-to-value and enabling faster experiment loops. For Engineering: clear intent, scalable interaction patterns, and shared design systems that reduce downstream rework through upfront alignment.

Focus areas

Three priorities that compound.

Strengthen system-level thinking: help the team move beyond isolated features toward cross-channel flows, lifecycle experiences, and coherent narratives. Align design work with business impact: connect our efforts clearly to activation, adoption, expansion, and long-term platform value — not just shipped screens. Build durable collaboration models: establish predictable ways of working with Product, Engineering, GTM, and PMM — so design acts as both the glue and the catalyst across teams.

Help each person do the best work of their career, while building experience systems that truly move the business forward.