The best design leaders don’t always give answers

In product design leadership, helping someone does not always mean stepping in with a solution.

Sometimes the team needs a clear decision. Sometimes a designer needs the benefit of your experience. And sometimes the most valuable thing you can offer is a thoughtful question that helps them find their own way forward.

The challenge is knowing which kind of support the situation calls for.

Manage when the team needs clarity

There are moments when a project needs direction rather than another round of exploration. A deadline may be approaching, priorities may be competing, or the team may be spending too much time debating a decision that needs to be made. In that situation, leadership means creating focus.

For example:

“Let’s move forward with the accessible version of the flow and validate the remaining details with users tomorrow.”

This is not about controlling the design or closing down discussion. It is about making the next step clear so the team can move with confidence.

Managing is especially useful when the team is blocked, when a strategic decision has already been set, or when there is a meaningful delivery or customer risk. It also applies when responsibilities are unclear, or when the cost of waiting outweighs the cost of making a reasonable call. A good manager does not provide direction for the sake of being decisive; they provide it when clarity will help the team make progress.

2. Mentor when someone needs perspective

Mentoring is different. It is not about telling someone exactly what to do, but rather sharing an experience, pattern, or way of thinking that they can adapt to their own situation.

For example:

“When I faced a similar navigation problem, mapping the user’s task before exploring layouts helped reveal what really needed to change.”

The example gives the designer a new lens without removing their responsibility to understand the current problem and decide what to do next. This is the kind of leadership I enjoy most.

I love helping designers connect the dots between user needs, product constraints, business goals, and the quality of the final experience. A mentoring conversation can help someone see that a design challenge involves more than the interface in front of them, touching on the underlying product model, the team’s assumptions, the decision-making process, or how the problem was framed.

The best mentoring is practical and generous, but not prescriptive. It sounds less like «Here is what you should do,» and more like «Here is what I noticed in a similar situation; what might apply here?» Mentoring is most valuable when it helps someone develop their own judgment, building their own experience rather than making them dependent on yours.

3. Coach when someone needs to think it through

Coaching is useful when someone already has the knowledge or capability to solve the problem, but needs space to organize their thinking. Instead of offering an immediate solution, you might ask what problem is being solved for the user, what evidence supports the direction, or what they would test first.

These questions encourage the designer to slow down, examine their assumptions, and make the reasoning behind their decision visible. Coaching can be particularly powerful when a designer presents a polished solution too quickly. Rather than reviewing every detail of the interface, you can return to core questions about the target user behavior, the intended product outcome, the riskiest assumptions, the simplest ways to validate direction, and what evidence would change their mind.

The goal is not to lengthen the conversation, but to help the person reach a stronger conclusion with greater ownership.

The answer depends on the moment

The same designer may need all three forms of support during the same project. At the beginning, they may need coaching to frame the problem. During exploration, they may benefit from mentoring and a relevant example from your experience. Before delivery, they may need clear management to align priorities and make a decision.

A new designer may need more structure, whereas a senior designer may need a challenge rather than an answer. Similarly, a team under pressure may need a clear call even when the situation is not perfectly understood.

There is no single leadership style that works in every moment. Great product design leadership is not about always having the best answer in the room, but about recognizing what kind of help will create the most progress.

Sometimes that means setting the direction, sometimes it means sharing what you have learned, and sometimes it means stepping back and asking a question that helps someone else find the answer.

That is why I love mentoring. It combines generosity with restraint: sharing experience, making patterns visible, and offering support without taking ownership away from the other person. The most rewarding outcome is not that someone follows your advice, but that next time, they trust their own judgment a little more.

Hi, I’m Cristina, a Digital Design Lead and Product Designer based in Copenhagen. I write about creative leadership, design culture, and the quiet moments that shape how we grow as professionals. My work connects UX, brand, and strategy to help teams turn complexity into clear, meaningful digital experiences. I lead the design community in Denmark through IxDF, and through design leadership I help ambitious teams build stronger products, sharper practices, and more confident design cultures. I’ve worked across technology, healthcare, fintech, and public-sector products helping teams move from early ideas to focused, production-ready experiences. Forever learning, mentoring, and helping designers find their voice in rooms built for noise.

The best design leaders don’t always give answers was originally published in Bootcamp on Medium, where people are continuing the conversation by highlighting and responding to this story.