I lead design at the intersection of strategy, craft, and people.
I'm Angira Chokshi. I build design practices and the teams that make them excellent — leading work that shapes products millions of people use, while creating the conditions where designers grow into leaders in their own right. Across fintech, luxury commerce, enterprise platforms, and AI-driven products, I've learned that the best outcomes happen when design operates at every level: in the strategy, in the system, and in the detail.
Clients supported
How I Lead.
My Design Philosophy.
People grow the work.
The measure of good design leadership isn't the quality of what ships while you're watching — it's what the team ships when you're not in the room. The best design decisions come from teams that feel safe to challenge, experiment and disagree. When designers feel genuinely trusted, they make calls you wouldn't have made yourself — and they're often better ones.
I invest in progression frameworks, 1:1 coaching, and cultures of psychological safety because I've lived that truth repeatedly. Several of the designers I've worked with are now senior leads and managers in their own right. That's the measure I care about most.
Strategy first, craft always.
Good strategy and strong craft aren't in tension — but it takes discipline to hold both. I stay involved in product strategy: shaping OKRs, sitting in roadmap conversations, understanding the commercial context behind design decisions. And I stay close to the craft: in crits, in wireframes, in the moments that determine whether something feels right or just functions.
​
I've seen leaders drift toward one at the expense of the other. When strategy loses touch with craft, teams ship things that work but don't resonate. When craft loses touch with strategy, teams do beautiful work that doesn't move anything. The goal is always both.
Know the user. Know the business.
Designers who understand commercial pressures, technical constraints, and business strategy make fundamentally better decisions than those who don't. Not because it compromises user advocacy — but because it sharpens it. The most impactful work I've led has come from teams that could hold the user's reality and the business's reality in the same thought. That's what I hire for, coach for, and model every day.