Mentoring Designers: Conversations That Actually Help

At some point, becoming a senior designer means becoming responsible for someone else’s growth, not just your own output. And yet mentoring designers is rarely something anyone was actually taught. Years of practice teach you how to make good work; almost nothing teaches you how to hand that skill to someone else.

1. Giving an Answer vs. Giving a Question

When a junior designer brings you a draft, the fastest response is to just tell them how to fix it. The problem is that this improves the one draft in front of you without building the junior’s ability to solve the next similar problem on their own. A junior who gets used to receiving answers eventually starts treating “ask the senior” as the default move, rather than a fallback.

The way around this is handing back a question instead of an answer. “Why did you put this button here?” or “What do you want someone to notice first on this screen?” take longer, but they force the junior to practice building their own reasoning. There are real moments — a tight deadline — where a direct answer is the right call. What matters in mentoring isn’t picking one mode and sticking to it; it’s consciously choosing between the two depending on the situation. As a junior gains experience, it’s usually worth tilting the ratio gradually toward questions. Hand someone full autonomy from day one and they tend to flounder without direction; keep handing them answers indefinitely and you keep postponing the moment they actually grow.

2. Critique Without Leaving a Scar

Sharp feedback and hurtful feedback aren’t the same thing. The difference mostly comes down to whether the feedback targets the work or the person. “This layout’s hierarchy is unclear” is a comment about the work. “Why would you make it like this” reads as a judgment of the person, whether or not that was the intent — and juniors remember the second kind far longer.

Effective critique states an observation and its impact before offering a suggestion. “This button’s contrast is low enough that a visually impaired user might miss it entirely — worth pushing the contrast further” lands as far more constructive than the same content delivered in reverse order, starting from the conclusion. Lead with the conclusion instead, and the junior’s first reaction tends to be defensive — which means the actual point of the feedback gets lost before it even lands.

Keeping 1:1s From Becoming a Formality

A recurring 1:1 that only ever covers project status starts to feel, to the junior, like an extension of reporting up the chain. Opening instead with something like “what’s been hard about work lately” before getting to the project turns that same block of time from oversight into support — a distinction juniors notice immediately.

3. The Common Mistake — Teaching Your Own Method as the Only Answer

The mistake senior designers make most often is teaching their own way of working as if it were the only correct one. Pushing personal habits — a specific tool’s shortcuts, a particular documentation style — onto a junior costs them the chance to develop a working style of their own. The goal of mentoring was never to produce a smaller copy of yourself; it’s to help someone else build their own judgment. A team full of designers who all think exactly alike might feel easier to collaborate with in the short term, but over time it quietly erodes the team’s ability to absorb a genuinely new point of view.

Closing thoughts

Mentoring a designer isn’t about fixing a junior’s work for them — it’s about building the muscle that lets them make good calls on their own. The measure worth using at the next feedback session isn’t how fast the right answer got delivered. It’s what the junior actually noticed for themselves along the way — and that shows up, if it shows up at all, not in the very next draft, but in the one after, made without you in the room.