Leadership
How I lead
I build the conditions for good work: shared principles, a steady rhythm, and the training that makes new habits stick. Then I step back, ask before I answer, and let designers tell the story of their own work.
Where we work
Teams on three continents
North America
- Redmond, WA
- Mountain View, CA
- New York, NY
- Vancouver, Canada
Europe
- Barcelona, Spain
Asia
- Beijing, China
Principles
What I believe about teams
- 01
Candor with care
Precise feedback, paired with explicit expectations for growth and recognition.
- 02
Revenue and respect aren’t a trade-off
The best monetization is something people would choose. If it only works by tricking users, it doesn’t work.
- 03
Ship the MVP, protect the North Star
Every feature gets an MVP, a North Star and an incremental path between them, with off-ramps in case we learn something.
- 04
Ask before you answer
Most of the time, I ask for someone’s approach before offering mine. Teams grow when leaders hold back.
- 05
Everyone presents
Designers should tell their own story to executives. Visibility is a growth tool, not a reward.
- 06
Design in the medium
In the AI era, the prototype is code. Our designers build what they mean.
Operating rhythm
The rituals that keep a team moving
Each row shows how often it happens across one quarter.
Weekly
- 1:1sWith every direct report: growth, blockers, boundaries.
- Design critiquesThree to five a week, structured to balance candor and safety.
- PM/design scrumsShared backlogs per workstream, so load is visible and balanced.
Every two weeks
- AI workshopsTwo hours of building together: everyone builds products, and builds themselves.
- Team meetingsBringing the team together to align, answer questions and grow together.
Monthly
- All-team forumOrg updates, community, learning and celebration.
- Skip-levelsDirect time with everyone in the org, contractors included.
- AI shareEveryone shows one AI experiment or process change.
Quarterly
- Designers present to execsEvery designer tells the story of their own work.
- Growth conversationsExplicit expectations for growth and recognition.
- Team offsiteStorytelling, a future-state playbook, hands-on building, partners.
See it in practice
Read the case studies