← BACK TO HOME

Design as a strategic function — not a production resource.

Design
Leadership

Where the design function sits determines what it can change. Here's how I think about that — and the work that proves it.

Where Design
Sits, Matters

→

I've sat in enough rooms to know that the gap between design and decision-making rarely announces itself. It shows up quietly. In a product direction that felt right until it didn't. In an AI feature the team believed in but users walked away from. In a launch that hit its date and missed its mark.

Nobody puts "design wasn't upstream" in the postmortem. But it's there.

Design leadership that's part of those conversations early doesn't just improve the work. It changes which problems make it to the table in the first place.

What
Changes

→

I've spent months inside organizations, sleeves rolled up, untangling product decisions that would have taken a week to get right if design had been in the conversation earlier. The call gets made without the full picture. That's usually what happened.

Design moves upstream. Product decisions get looked at for their human and behavioral implications before they're built, not after. The team produces work that accumulates toward something rather than shipping in isolation. Problems that used to surface at launch start surfacing in the room where the decision is made. That's a much cheaper place to find them.

When design has the right seat, the work changes. So does the pace. So does the confidence in the room when a hard call has to be made. Customers feel it too. Not in any way they can name, but in whether the product earns their trust or quietly loses it.

That last part shows up in retention numbers. It doesn't usually get attributed to design. It should.

How
I Work

→

I dissect before I build. I've seen too many teams sprint toward the wrong solution with great execution, so my approach is about defining clear solutions, not just caution. I look for the decision underneath the decision because that's where the assumption usually got baked in, or where most teams stopped asking the hard questions because the goals got traded away for speed. That work is hard and fast, but it's also not visible until it saves you six months.

The same applies whether a team is working with AI or not. The question I bring to any integration, any product decision, any operating model change is the same: does the decision itself hold? The data model, the interaction pattern, the trust, the copy. Whether what the system claims to do is actually what it does to the person on the other side of it.

Teams are where this either compounds or collapses. Yes, craft matters enormously. But honestly, craft without judgment is just polish. The work I care about is building teams that can reason their way to the right problem before they start solving it. That's the ceiling worth raising.

SELECTED WORK Three organizations. Three different problem dimensions.

IF THIS IS THE LEVEL YOU'RE WORKING AT

I work with organizations that are ready to treat design as a strategic function, not a production resource. If that's where you are, or where you're headed, the conversation is worth having.