Giving Feedback to a More Junior Designer Without Just Replacing Their Decisions With Yours¶

Reviewing a junior designer's work and simply telling them exactly what to change is genuinely the fastest path to a better result on that specific piece - and it's also one of the most reliable ways to make sure they don't develop the judgment to make that same call independently next time. The tension is real: a senior reviewer's time is limited, the work often needs to ship, and building someone's judgment takes longer than just fixing the thing yourself. But feedback that only ever hands over the answer produces a junior designer who gets better at following direction, not one who gets better at designing.

Notice Whether You're Answering "What's Wrong" or "What Should It Be"¶

There's a real difference between pointing out that something isn't working and prescribing the exact fix - "this hierarchy isn't guiding the eye where it needs to go" identifies a problem; "make the headline larger and move it here" hands over the solution without the junior designer ever engaging with why that particular solution addresses the problem. Defaulting to identifying the problem and asking them to propose a fix, rather than jumping straight to the fix yourself, is slower in the moment and is what actually builds the underlying skill over repeated instances.

Ask the Question You'd Ask Yourself, Out Loud¶

Senior designers usually aren't consciously aware of the internal checklist they run through when evaluating their own work - does this guide attention correctly, does this feel balanced, does this actually solve the stated problem. Making that internal process explicit, by asking it as a direct question during feedback rather than silently applying it and delivering only the conclusion, gives a junior designer a transferable framework instead of a one-off correction that only applies to this specific piece of work.

Let Some Decisions Ship Imperfect on Purpose¶

Not every piece of work is high-enough-stakes to warrant insisting on the ideal outcome - some genuinely are the right place to let a junior designer's own judgment call ship, even knowing a more experienced designer might have made a slightly different choice, specifically because the learning that comes from seeing the real-world result of their own decision (rather than a decision handed to them) is valuable in itself. This requires a real, deliberate judgment call about which projects can absorb that kind of learning cost and which genuinely can't - but treating every single piece of work as too high-stakes to allow this removes the opportunity entirely.

Separate Skill-Building Feedback From Deadline-Critical Corrections¶

When a deadline genuinely doesn't allow for the slower, more Socratic version of feedback, it's worth saying so explicitly rather than pretending the fast, prescriptive correction is a teaching moment when it isn't one - "I'm going to just tell you the fix this time because we're out of runway, but let's talk through the reasoning after this ships" preserves the learning opportunity even when the immediate feedback had to be direct, and it's honest about why the shortcut was taken.

FAQ¶

Doesn't asking a junior designer to propose their own fix risk shipping a worse result?
Sometimes, on lower-stakes work, and that's an acceptable and even useful trade-off - the point is being deliberate about which work can absorb that risk, not eliminating the practice of building judgment entirely because it occasionally costs a slightly weaker outcome.

How much time should senior designers realistically spend on this kind of feedback versus just fixing things directly?
More than feels immediately efficient, especially early in a working relationship - the time investment pays off as the junior designer's judgment improves and needs progressively less direct correction over time, which a purely prescriptive feedback style never achieves.

Is this approach different for feedback on strategic decisions versus purely visual execution?
The underlying principle holds for both, though the specific questions differ - strategic feedback might ask what the audience actually needs from this, while execution feedback might ask what's drawing the eye first, but in both cases, prompting their reasoning rather than supplying the answer is what builds transferable judgment.