How to grow a junior designer into a senior one

Promoting a designer doesn't develop them. I've seen this play out more than once: a junior designer does strong work, gets promoted to mid-level, does the same kind of work, gets promoted again. Three years in, they have a senior title and mid-level judgment. The promotions rewarded output. Nobody invested in the reasoning.

The gap between junior and senior is mostly a gap in judgment. The ability to make good decisions when the brief is ambiguous, the constraints are in conflict, and there's no one in the room who can tell you the right answer. That's not a skill you develop by doing more of the same work. It's a skill you develop by being placed in situations where judgment is required and getting feedback when you use it wrong.

What actually builds judgment

The situations that build judgment are the ones that don't have clean answers. The edge case nobody thought about in the brief. The stakeholder whose feedback contradicts the user research. The decision about whether to ship something that works functionally but doesn't feel right.

Junior designers will often wait for guidance in these moments, or default to whatever the most senior person in the room thinks. That's not a character flaw. It's the rational move when you haven't been given authority to make the call yourself. The problem is that waiting for guidance in ambiguous situations is exactly what keeps a junior designer junior.

The manager's job is to create conditions where the junior designer has to make the call, then to debrief it afterwards. Not to take over when things get hard, and not to give so much pre-work guidance that no genuine decision is required. The designer needs to be in the uncertainty, not protected from it.

The feedback problem

Junior designers typically get feedback on craft: execution quality, visual hierarchy, component choices. That's appropriate at the early stages. But if a designer is going to grow toward senior, the feedback has to shift toward reasoning: why did they make the choices they made, what did they consider and dismiss, what are the tradeoffs in the direction they picked?

This requires more from the manager than craft feedback does. You have to understand the designer's reasoning well enough to push on it. "Why this layout over the other option you showed earlier?" is more valuable than "this layout is stronger." The first question builds the muscle. The second one confirms a conclusion.

The shift from craft feedback to reasoning feedback is one of the clearest markers I know of a design manager doing the harder part of their job.

What to delegate

Delegation is the main mechanism for growth at this level, but vague delegation doesn't produce it. "You're leading this project" means nothing if the designer still expects the manager to make every consequential decision.

Useful delegation is specific about what the designer owns. They own the problem definition and will defend it. They own the stakeholder relationships on this surface and will handle the review. They're accountable for the decision to go in one direction over another, and the manager will give feedback on the reasoning after the fact.

The specificity matters because it removes the ambiguity about who is making decisions. When the designer knows the decision is theirs, they make it differently than when they're waiting to see if the manager will step in.

The gap that surprises people

The thing most managers are unprepared for when developing a junior designer is the emotional component. Moving from execution to judgment means moving from a world where someone else validates your work to one where you're responsible for the direction itself. That's uncomfortable for most people, and it produces avoidance behaviors that look like lack of initiative.

A designer who was great at executing under clear direction suddenly seems to be stalling on ambiguous projects. They're asking more questions than usual, seeking approval on small decisions, not bringing work until it's more polished than it needs to be at that stage.

This is almost always about confidence, not capability. The designer has the skills. They don't yet trust themselves to use them in a higher-stakes context. The manager who interprets this as a talent problem will make it worse. The manager who names it directly gives the designer something to work with. "I notice you're waiting for me to confirm things that are yours to decide."

Growth at this stage is mostly about permission: the explicit, repeated communication that this person is trusted to make the call. That trust, extended consistently over time, is usually what actually moves the needle.