Give direction. Make space.

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: that is 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. The team doesn't need to feel that pressure. 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.

What reaches the team is a decision: what goes into this cycle, what waits, and what we stop asking for. If pressure lands as vague urgency, each person resolves it differently and the work fragments. If it lands as scope, the team can finish something.

That buffer does not hide the problem. The team knows the date and what is at stake. What they should not have to manage is the noise of every priority shift, or the conversation I already had. And when I cannot hold the line, I say so before it shows up on the calendar as a surprise.

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.

Alignment is not imposition. You have to negotiate: translate the risk of a decision into language business and engineering understand, and bring back what each side cannot drop. You have to know when to yield, when the cost of insisting is higher than adapting the design. And you have to set limits when yielding breaks the experience, the date, or the team. Without that ongoing negotiation, alignment is only a kickoff agreement that falls apart at the first friction.

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.

That starts with reading the environment: who decides, where work gets stuck, and what pressure arrives from outside. With that map, responsibilities can be named without ambiguity. Then you have to make space: not reviewing every pixel or every sentence, but agreeing the criterion and trusting people to apply it. Without trust, ownership is on paper; without space, feedback turns into control.

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, 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.