From Great Designer to Great Leader:
What to Unlearn

You got promoted because you could spot a broken interaction from across the room, untangle a messy workflow, and turn “we want it to feel more intuitive” into something people could actually use.

Naturally, your reward is a calendar full of meetings and significantly less time to do any of that.

Welcome to design leadership.

The tricky part is that the habits that made you a great designer can become the habits that hold your team back. Your eye for detail becomes constant correction. Your reliability becomes everyone’s dependency. Your ability to solve anything becomes an invitation to solve everything.

Getting better at leadership means noticing when your strengths have started doing someone else’s job.

Unlearn being the person with the answer.

As a designer, having a strong answer was often your contribution. As a leader, answering first can shut down the thinking you’re trying to develop.  When someone brings you a difficult problem, resist the urge to start designing out loud. Ask:

• What do you think is happening?
• What have you considered?
• Where are you stuck?
• What would help you make the call?

You’re looking for the point where their reasoning needs support. Maybe they’re missing context. Maybe the tradeoff is genuinely difficult. Maybe they already know what to do and need to hear that they have the authority to do it.

That doesn’t mean turning every conversation into a coaching obstacle course. If someone needs a straightforward answer, give them one.

But if every meaningful decision travels through you, you’ve created an approval queue with a LinkedIn title.

Unlearn treating your taste as the quality bar.

You might have excellent taste. Your team still needs something more usable than “I’ll know it when I see it.”

A quality bar should describe what the work needs to accomplish: clear hierarchy, understandable interactions, accessible behavior, appropriate system patterns, and enough evidence to support the decision.

Before giving feedback, identify what you’re reacting to.

Is there a usability problem? A missed requirement? An inconsistency that will create confusion? Or would you simply have designed it differently?  “I would have done this differently” deserves much less authority than “This prevents someone from completing the task.”

Explain your concern and its consequence. Give the designer room to solve it. There are usually several good answers. Leadership gets easier when you stop requiring all of them to look like yours.

Unlearn rescuing every project.

You can probably fix the flow faster yourself.

Today.

But when you repeatedly take work back, your team loses practice, ownership, and confidence. They also learn that if something gets sufficiently complicated, you’ll eventually appear with a fresh Figma page.

Before stepping in, diagnose the problem. Does the designer need clearer expectations, missing information, a narrower scope, or help building a specific skill?

Match your support to that need. Work through one difficult interaction together. Explain your reasoning. Agree on a checkpoint. Then hand ownership back. There are moments when you should intervene directly, especially when the consequences of a mistake are serious. Make those interventions explicit rather than quietly commandeering the file.

Rescue the project when necessary. Don’t accidentally make rescue the process.

Unlearn measuring your value in visible output.

A productive design day leaves evidence: a prototype, a resolved flow, a satisfyingly organized page. A productive leadership day might leave a canceled project, a clearer decision, or a designer who finally understands what’s expected of them.

Less photogenic. Potentially much more valuable.

Pay attention to whether your team makes decisions with less confusion, catches risks earlier, and delivers work that holds up in implementation. Look at whether designers are growing in judgment and whether stakeholders understand the reasons behind the work.

Those are meaningful signals of your contribution, even when your cursor never enters the canvas. Keep your craft sharp. Review real work. Stay close to users and the product. Just be careful about grabbing execution work because it gives you a more familiar way to feel useful.

Your team shouldn’t have to compete with you for the interesting projects.

Unlearn equating support with agreement

Being supportive includes telling someone when their work isn’t meeting expectations.

Waiting until a performance review is neither kind nor particularly efficient. By then, you’ve spent months being frustrated while they’ve spent months assuming things were fine. An impressive waste of everyone’s time. Give feedback while there’s still room to act on it. Describe what you observed, why it matters, and what needs to change. Ask what’s getting in the way.

“The last two handoffs didn’t include error states, which left engineering making interaction decisions during implementation. Let’s agree on what needs to be covered before the next review.”

That’s a conversation someone can work with.

“Be more strategic” is a mysterious assignment with no due date. Clear expectations give people a fair chance to succeed. Follow-through makes those expectations credible.

Unlearn speaking design as your only language.

Your partners have pressures you may not see: delivery commitments, technical constraints, revenue targets, support volume.  Learn enough about those pressures to connect your concerns to the decisions they need to make.

Explain how a confusing workflow creates avoidable support requests. Show how inconsistent patterns add implementation work. Be honest about where you have evidence and where you’re making a hypothesis.

That makes your judgment easier to assess and your recommendations easier to act on.

You can advocate firmly for users while understanding why someone else is pushing back. Curiosity is useful even when you’re fairly certain the proposed modal is a crime against navigation.

Let your team be good without you in the middle.

The transition can feel strange. You’re loosening your grip on the work that established your credibility and learning to find satisfaction in someone else making the call.

Start small. In your next critique, ask before suggesting. In your next handoff, clarify ownership. In your next one-on-one, give the feedback you’ve been politely avoiding.

Over time, your contribution becomes visible in the team’s judgment, confidence, and ability to deliver.

And when someone solves a hard problem beautifully without asking you first, enjoy it. You helped build that.