Leadership & ways of working

I've led design teams in conditions that don't appear in job descriptions. First engagements where the margin for error is zero. Deadlines set before the brief exists. Organizational silos that block the research you need. Stakeholder matrices where everyone has veto power and nobody has full visibility.

One of the things that genuinely frustrates me about how design projects are sold is the gap between estimated effort and reality. I've worked on too many projects where delivery timelines were set by commercial pressure rather than honest scoping, and the people who pay for that gap are always the team. That's why I push hard to be involved in the strategic phases of a project, before contracts are signed and roadmaps are locked. Not because I want more meetings, but because that's where you can actually influence what's feasible. Once the deadline is fixed and the scope is written, you're just managing damage.

When pressure does arrive, and it always does, my job is to absorb as much of it as possible before it reaches the people doing the work. I've been in rooms where a client's anxiety was turning into daily escalations that had nothing to do with the actual design quality. The team doesn't need to feel that. They need clarity, air, and enough psychological safety to make good decisions. Creating that buffer is part of the role, and it doesn't show up in any deliverable.

The most expensive design mistakes I've seen don't happen in Figma. They happen in alignment gaps, between what the business thinks it asked for, what engineering thinks it's building, and what the user actually needs. My role is to hold those three things in tension without letting any one of them collapse the other two. That means knowing when to push back, when to absorb, and when to call something out in a room where nobody else wants to say it.

I'm an early adopter by instinct. I've been integrating AI into my professional and personal workflow since the first generation of usable tools, not as a novelty but as a genuine productivity layer. I use it to accelerate discovery, compress iteration cycles, and stress-test design decisions before they go into a room. The Orange and DORA projects sit at opposite ends of a decade of thinking about how humans and machines share decision-making, and that question still feels unresolved enough to be interesting.

What I've learned about leading teams is simpler than it sounds: clear ownership, honest feedback, and the discipline to protect the work from the noise. The number of people on the team matters less than whether they know what they're responsible for and feel safe enough to say when something isn't working.