What nobody tells you about your first 90 days as a design leader

The first instinct when you step into a design leadership role is to fix things. There's work that's clearly suboptimal, process that's clearly broken, and you probably got the job in part because you'd been quietly diagnosing these problems for months. Now you have authority.

That's the wrong move. Almost every time.

The things that look broken from outside the role look different once you're in it. What seemed like a team not caring about quality is often a team doing the best they can inside constraints you didn't see. What seemed like poor process is a workaround for something upstream you don't have visibility into yet. Moving fast on your diagnosis burns credibility before you've earned it.

The job changes more than you expect

Before the role, your job was to produce good design. After it, your job is to create conditions where other people produce good design. That shift is larger than it sounds.

Your sense of what good work looks like is still relevant. But it's a supporting skill now, not the primary job. The primary job is making space for other people to do their best work.

Most new design leaders don't make this transition cleanly. They keep doing the work. They take on the most interesting problems themselves. They redesign things that frustrate them rather than helping the designer on the problem see what's wrong. This feels productive. It stunts the team.

The first month is observation, not action

Your goal in the first thirty days is to understand what's actually true, not to confirm what you already believe.

That means sitting in on work you wouldn't normally prioritize. Watching how feedback gets given and received. Seeing where designers get stuck. Understanding what the relationship with product and engineering actually looks like in practice, not in theory.

It means asking questions that reveal constraints rather than problems. "Why does this work this way?" is information-gathering. You'll find out about priorities you didn't know existed, decisions made before you arrived, and constraints that are genuinely real.

One-on-ones with every person on the team in the first two weeks are the most useful thing you can do. Ask what's going well. Ask what they'd change. Ask what they've tried to change that didn't work and why. This gives you a map you can't get any other way.

The things worth doing early

There are moves that pay off early without requiring you to have diagnosed everything correctly.

Showing up consistently to existing work. Being in rooms where decisions get made. Removing specific, obvious blockers. The thing stuck in review, the tool nobody can access, the decision waiting on approval. These build trust without burning it.

What to hold off on

Major process changes until you understand why the current process exists. Visible displays of new direction until you've established credibility. Reorganizing team structure before you know how work actually flows.

And resist the urge to explain your philosophy. New leaders often overexplain their approach before they've done anything. Work earns trust. Explanation doesn't.

Ninety days is about as long as it takes to understand what you inherited. After that, you've earned the context to start changing things.