I've built design organisations from zero three times. What I've learned is that the hardest part isn't hiring — it's creating the conditions where people do their best work and design earns its seat at the table.
I lead from the craft — shaping product strategy, staying close to design, and developing designers into leaders.
I work with Product and Engineering leadership on roadmaps, product bets and tradeoffs, while building teams, leaders and systems that scale beyond me.
I stay close enough to the work to shape problem framing, design direction, critique and quality — not just review the final screens.
I partner with Product and Engineering leaders early, influencing roadmaps, product bets and tradeoffs before execution begins. At ServiceNow, I worked with VP Product, VP Engineering and Design SVP/VP on platform-level roadmaps. At ColorTokens and Quick Heal, I partnered directly with CPOs, CTOs and CEOs to connect design decisions to product and business outcomes.
My goal isn't to create dependency on me. I develop designers who can challenge briefs, lead initiatives, raise quality and make decisions independently.
I turn what works into repeatable practices — from critique and decision-making to career development and AI-native workflows.
One of my designers was sharp and fast — but design reviews consistently started with the solution rather than the problem.
So I changed the conversation. Instead of giving feedback on screens, I asked: "What problem are we solving?"
We focused on framing the problem, challenging assumptions and defining what good looked like before opening Figma. Six months later, the designer was reframing the PM's brief before a pixel was drawn.
That's what leadership means to me: Not making better designers dependent on you — making them capable of leading without you.
These aren't processes for the sake of process. They're infrastructure for making good design repeatable.
Frameworks aren't theory — they're reusable infrastructure I built to solve real operational problems across ServiceNow, ColorTokens, and Quick Heal. Each time I joined a new org, I built the design operating system from scratch.
A structured async framework for aligning distributed design teams across time zones — keeping design intent, decisions, and culture coherent without calendar overload or late-night calls.
A framework for building AI-native practices and culture within the design team — measuring AI maturity, driving adoption of AI tools, and making AI a true design partner at every stage.
A tiered, structured approach to critique and approval — from IC-level concept reviews to bi-weekly leadership alignment — reducing rework and making design decisions traceable.
The hardest AI products aren't the ones that struggle to generate an answer. They're the ones that ask people to trust, approve, or act on something they didn't fully create or understand.
I design the boundary between AI autonomy and human judgment — deciding what AI should do, what it should explain, when humans should intervene, and how people recover when it gets something wrong.
From intelligence to action — without losing control.
The goal isn't to make AI feel human.
It's to make human judgment stronger.
As AI becomes more capable, design's role isn't to remove people from the loop — it's to determine when AI should lead, when humans should decide, and how the two recover together when things go wrong.