Reviewing design can feel oddly exposing when design is not the job. Plenty of smart marketers, founders, account leads and senior stakeholders can talk confidently about budgets, positioning, operations and growth, then go slightly vague the moment a creative review starts. Suddenly the language gets mushy. “Can it pop a bit more?” “I’m not sure it feels premium.” “Could we make the logo bigger?” “Something’s off.” That wobble is understandable.
Most non-creatives are expected to review design and give stakeholder feedback on work that will affect the brand, the customer experience and the commercial outcome, often without being taught what good design feedback actually sounds like. The problem is not that non-designers are incapable of judging creative work. It’s that many reviews are set up around taste rather than objectives, and taste is a terrible moderator.
Nielsen Norman Group defines design critique as analyzing a design and giving feedback on whether it meets its objectives, not simply judging it. Figma makes a similar distinction, noting that different kinds of review need different types of feedback depending on whether the work is still exploratory or being assessed against product and business goals.
That matters because the difference between useful review and idea-diluting interference is rarely intelligence. It is usually method. Non-creatives can be extremely good at evaluating creative work when they know what to look for: whether the work solves the brief, reflects the brand, serves the audience, communicates clearly, and earns its place in the market. They become dangerous when they mistake personal preference for strategic judgement, or when a room full of stakeholders starts trying to design by committee.
Adobe’s guidance on feedback warns against gut reactions and comments based on personal preference, while GOV.UK’s design principles insist that good design starts with user needs rather than internal assumptions. That is the real shift non-creatives need to make. The question is not “Do I like this?” but “Is this doing the job it needs to do?”
Why Non-Creatives Struggle with Evaluating Creative Work
Andreas Krasser
The first reason is simple: most people have been taught to consume design, not critique it.
Everyone has opinions about what they notice, what they remember and what they find attractive or irritating. That is not the same as knowing how to assess whether a piece of creative work is effective. A stakeholder may know that a layout feels cluttered, that a campaign line sounds awkward or that a landing page seems confusing, but without a framework those instincts often emerge as vague reactions.
NN/g’s research on derailed design critiques notes that feedback sessions easily slip into hypothetical scenarios, personal preferences and unactionable suggestions unless they are actively structured. That is not because stakeholders are foolish. It is because critique is a skill, and unstructured skill tends to turn into noise.
The second reason is that design reviews often ask people to comment on the wrong thing at the wrong time.
Early-stage concepts need openness. Product reviews closer to delivery need alignment to business and user goals. When those stages get blurred, stakeholders end up applying finish-line judgement to unfinished ideas or, just as badly, airy blue-sky commentary to work that is already trying to solve specific constraints. The result is frustration on both sides. The designer thinks the room is nitpicking. The stakeholder thinks the work is somehow avoiding the real issue. Often both are reacting to a badly framed review.
The third reason is status. Not everybody wants to admit they feel underqualified in a design review, especially if they are senior elsewhere.
That discomfort often produces one of two bad behaviours. Either the stakeholder withdraws into vague approval and says nothing useful, or they overcompensate with confident but arbitrary opinions. Both are common. Stakeholders are people with interest, power or influence over the project, which means their comments carry real weight whether or not those comments are well formed. That can make design reviews feel politically loaded. A designer may hear one casual remark from a senior stakeholder as an instruction. A stakeholder may offer a preference thinking it is just part of the conversation. This is how “a few thoughts” becomes three weeks of avoidable revision.
The fourth reason is that creative work is unusually good at triggering personal language.
People rarely say “I don’t like this spreadsheet” unless something has gone truly wrong. They say it about design all the time. Visual work invites instinctive response, which is part of its power. But instinct is not yet critique. Practical critique guidance consistently pushes people to anchor comments in objectives, audience and context instead. Once reviews become a referendum on taste, the work usually gets blander very quickly because blandness is the closest thing a committee can find to consensus.
What Good Feedback on Creative Work Actually Looks Like
Lemonade Illustration Agency
Good feedback is specific, relevant and attached to a goal.
That sounds almost insultingly obvious, but it rules out most of the remarks that make designers quietly stare into the middle distance. “Make it more modern” is not specific. “I’m not sure it feels right” is not relevant unless the speaker can explain what “right” means in relation to the brief. “Could we make the headline bigger?” may be relevant, but only if the problem is actually hierarchy or missed messaging rather than personal alarm at whitespace.
Good feedback also observes before it prescribes.
That is one of the most useful habits a non-creative can learn. Start by saying what the work seems to be doing and where it may be succeeding or failing. “The page feels visually calm, but I’m not immediately seeing the primary action.” “The concept is distinctive, but I’m not sure the message lands quickly for somebody who doesn’t know the category.” “This does feel more premium than the previous version, though I’m wondering if the product benefit has become less obvious.” Those remarks are miles better than jumping straight to “Make the button red” or “Use a different photo.” The point is to name the issue before pretending to know the fix.
Good feedback is also proportionate to the reviewer’s expertise.
A non-designer does not need to apologise for being a non-designer. In many cases, that perspective is helpful. A marketer may understand audience nuance. A founder may understand business stakes. A product lead may understand user flow and commercial friction. A customer-support manager may spot tone problems immediately because they hear real complaints all day. What non-creatives should usually avoid is speaking with unearned certainty about executional craft when the underlying issue can be expressed more honestly at the level of effect. It is perfectly reasonable to say, “I’m struggling to follow the visual hierarchy here,” even if you could not lecture anyone on hierarchy theory. It is less useful to say, “Move this up 12 pixels and change the tracking,” unless that really is your expertise.
The Biggest Mistakes in Stakeholder Feedback
A-dapt
The first mistake is reviewing against taste instead of criteria.
This is the classic one. It sounds like “I just prefer…” or “I don’t love…” or “Could we make it feel a bit more like…” followed by a brand the company has absolutely no business resembling. Taste is not useless, but it is a very weak decision tool when used alone. A design should be assessed against the brief, the audience, the brand, the medium and the job to be done. GOV.UK’s design principles start with user needs for a reason. Work that serves the internal preferences of senior stakeholders but ignores real user needs is still bad work, even if the meeting goes well.
The second mistake is offering solution-shaped feedback too early.
This is how promising ideas get strangled before they have had a chance to develop. Early concepts require an open mind and that feedback which tightens the net too early can limit possibilities. That is exactly what happens when a stakeholder sees a rough concept and immediately starts prescribing typography, photography style or executional mechanics before the team has even agreed whether the underlying direction is the right one. Good review protects the emerging idea long enough for it to prove itself. Bad review panics at ambiguity and tries to make everything neat too soon.
The third mistake is piling on from multiple angles at once.
A lot of stakeholder feedback fails because it is not prioritised. Marketing wants more brand distinction. Sales wants clearer messaging. Legal wants safer language. Product wants less friction. Leadership wants more confidence. None of these concerns is inherently illegitimate. The problem comes when they are all thrown at the work simultaneously with no ranking, no decision framework and no acknowledgement of trade-offs.
The fourth mistake is giving feedback with no reference to the audience.
Non-creatives often ask what they should focus on when reviewing design without technical knowledge. The answer is surprisingly reassuring: the user, the user, and then the user again. If the reviewer cannot explain the design principles involved, they can still ask powerful questions. Is the main message clear? Is the desired action obvious? Does this feel trustworthy? Is anything likely to confuse, slow down or distract the intended audience?
The fifth mistake is using vague, theatrical language.
“Make it pop” deserves its terrible reputation. So does “Can we make it more dynamic?” unless somebody can explain what dynamic means in context. These phrases are not evil. They are just lazy placeholders for thoughts that have not yet been made usable. A review should not force designers to become amateur mind readers. If something feels flat, say what seems flat about it. If it seems overly safe, explain what risk the work is currently failing to take. If the message is being lost, point to where comprehension appears to drop. Specificity is not a courtesy. It is the substance of good critique.
How to Evaluate Creative Work Without Design Expertise
Nucco
The most liberating thing a non-creative can learn is that they do not need to become a designer to become a useful reviewer.
They do, however, need a better lens. Start with the brief. What was this work supposed to do? Was it meant to build recognition, explain a product, sharpen positioning, improve conversion, feel more distinctive, simplify a journey, support a launch, attract a different audience? Before commenting on the design itself, the reviewer should be able to restate the job in plain language.
Then move to audience. Who is this for, and what do they need from it?
This is where non-creatives often have more to contribute than they realise. A client, account lead, strategist, marketer or founder may understand the audience anxieties, objections and motivations better than anyone else in the room. That insight is useful if it is used honestly. The right question is not “Do I personally enjoy this?” but “Will the intended audience understand, trust or respond to this in the way we need?”
After that, look at clarity.
Can the reviewer tell what the piece is asking the audience to think, feel or do? Is the main message apparent quickly? Is the hierarchy helping or hindering? Is the brand recognisable without overwhelming the communication? This is not advanced design theory. It is a practical reading of what the work appears to be doing. Non-creatives are often very good at spotting unclear communication precisely because they are closer to the “fresh eyes” position than the design team. The key is to phrase comments in terms of the observed effect rather than commanding an executional fix.
Then look at fit.
Does the work feel appropriate to the brand, the context and the medium? A careers campaign can be playful in ways that a regulated financial product page cannot. A premium packaging system may need a different visual pace from a retail endcap. A pitch deck, an app onboarding flow and an OOH campaign are not the same type of communication problem.
Finally, ask whether the work is adding up to the intended outcome.
That might mean commercial outcome, behavioural outcome or perceptual outcome. Does it feel more distinctive? More usable? More credible? More emotionally resonant? More likely to earn attention? More likely to reduce confusion? A non-designer can evaluate all of these things with real value, especially if they resist the temptation to collapse those observations into personal preference. That is how a non-designer evaluates creative work confidently: not by pretending to have craft expertise they do not have, but by becoming unusually disciplined about purpose, audience and effect.
A Simple Framework for Evaluating Creative Work
Rhapsody
Most review meetings improve dramatically when people are given a few good questions.
A simple framework could be this: objective, audience, clarity, distinctiveness, and action.
Objective comes first. What is this supposed to achieve? If the room cannot answer that consistently, the work may not be the problem. The brief may be.
Audience comes next. Who is this for, and what do they need or care about? What might confuse them, reassure them, interest them or put them off? This prevents the all-too-common mistake of turning the most senior person in the room into the default audience.
Then clarity. Can the reviewer quickly understand the main idea, message or action? Is anything obscured by the way the work has been expressed? This is where comments about hierarchy, readability, emphasis and comprehension can be useful even from non-designers, so long as they are phrased as observed communication issues rather than arbitrary fixes.
Then distinctiveness. Is this recognisable, ownable or memorable enough for the category and the brand? Or does it feel generic, derivative or too safe? This is a particularly useful question because non-creatives often sense blandness before they know how to describe it. The task is to link that feeling to strategy. Does it feel generic because the visual language resembles the whole category? Because the message is interchangeable? Because the brand’s particular point of view has been diluted? Once that’s stated properly, the feedback becomes useful.
Then action. What should happen next? What is the most important issue to address, and what should stay? Good reviews do not produce a shopping list of edits with equal weight. They identify the big thing.
That framework will not turn anyone into an art director overnight. It will, however, stop a lot of avoidable damage.
Examples of Bad vs Good Feedback on Creative Work
JSR Agency
Bad feedback says, “I don’t like the blue.”
Good feedback says, “The colour palette feels calmer and more premium, but I’m wondering whether the key action is standing out enough for somebody scanning quickly on mobile.” The difference is not politeness. It is usefulness. One offers preference. The other identifies a possible communication issue.
Bad feedback says, “Can we make the logo bigger?”
Good feedback says, “I’m not sure the brand is landing strongly enough in the first few seconds. Is that a branding issue, or is the answer elsewhere in the layout?” That keeps the brand concern alive without assuming the most obvious fix is the right one. It also gives the designer room to solve the real issue rather than obeying a reflex.
Bad feedback says, “It needs more energy.”
Good feedback says, “The current version is clear, but it feels more restrained than the campaign territory we discussed. I’m missing the sense of momentum we said would matter for this audience.” This is still subjective, of course, but it is subjective in a way that points to the brief and the intended outcome rather than floating free as mood commentary.
Bad feedback says, “This doesn’t feel right.”
Good feedback says, “I’m struggling to connect this execution to the audience tension we identified earlier. Can you talk me through how this direction addresses that?” That is a strong non-creative move because it asks for rationale before issuing a verdict. It also gives the team a chance to reveal whether the work is smarter than it first appears. Critique, after all, is a conversation, not just a series of notes.
Bad feedback says, “Can we see five more options?”
Good feedback says, “I think the room is still unsure about one particular issue. Before we ask for more routes, can we clarify whether the uncertainty is about message, audience fit, or distinctiveness?” More options are not always more thinking. Sometimes they are just a more expensive way of avoiding a decision.
How to Give Feedback Without Watering Down Creative Ideas
IllustrationZone
This is the part that matters most, because “watered down” rarely happens in one dramatic act. It happens through accumulation.
A brave idea gets a little safer because one stakeholder worries it may be misunderstood. Then a little more generic because another stakeholder wants to make sure the product benefit is impossible to miss. Then a little more crowded because somebody asks to include three extra messages. Then a little more familiar because someone references a competitor they consider successful. Then the tone softens, the layout tightens, the distinctiveness recedes, and by the end the work is technically acceptable and strategically forgettable.
The way to avoid that is not to stop giving feedback. It is to give feedback at the right altitude.
Focus first on whether the core idea is strategically right. Does it answer the brief? Does it express something meaningful? Does it create the right kind of tension or clarity? If the idea is right but the execution needs work, say that. Protect the core. Early ideas need an open mind and that feedback which narrows the field too early can limit possibilities. That is highly relevant here. If the room reacts to every emerging rough edge as though it were final, strong ideas often get flattened before they can mature.
Second, separate discomfort from dysfunction.
A lot of interesting work feels slightly uncomfortable before it feels inevitable. That is not a flaw. Sometimes the design is genuinely unclear or off-brief. Sometimes it is simply unfamiliar, and unfamiliarity makes stakeholders nervous. Non-creatives need enough self-awareness to ask which of those two things is happening. That does not mean treating every bold idea as sacred. It means not confusing personal unease with professional judgement.
Third, comment on the problem you see, not the edit you want.
This is probably the single best habit for preserving quality. “I think the proof point is getting lost” is good. “Put the proof point in a yellow box in the top right” is usually not. “I’m not yet convinced the audience will understand why this matters to them” is good. “Rewrite the headline to say exactly this” is often not. Let the creative team do the creative solving, unless your expertise genuinely lies in the solution being discussed.
Fourth, prioritise.
If everything is an issue, nothing is. Tell the team what matters most. What is the one thing they most need to address before the work moves on? What is strong and should be protected? What is secondary and can wait? Review sessions become destructive when they create a long, unranked list of edits that nudges the work toward compromise by exhaustion. Clear priorities make stronger work more likely.
Fifth, remember that the goal of review is not to prove you are useful in the meeting.
This may be the quietest cause of bad stakeholder feedback. Some people feel they need to say something substantial to justify their presence, especially if they are senior. So they say something. Anything. A colour preference. A line-level tweak. A request for variants. A reference to some campaign they vaguely remember liking. None of that is harmless just because it is casually said.
Sometimes the most useful contribution is to recognise that the work is doing its job and resist the urge to decorate the conversation with unnecessary intervention. This is an inference, but it follows directly from the critique principles above: feedback should be objective-led, relevant and actionable, not performative.
How to Review Design Without Pretending to be a Designer
Paul Pateman
A non-designer does not need to speak the language of kerning, grids or typographic contrast to offer great design feedback. They need to speak the language of purpose, audience, clarity, brand and effect. They need to know what they are actually trying to protect. And they need the discipline to leave the designer enough room to solve the problem well.
That is how a non-designer evaluates creative work confidently. It is how to review design without pretending to be a designer. It is how to contribute stakeholder feedback without interfering blindly in the process. And it is why better evaluating creative work is not about becoming more opinionated. It is about becoming more precise.
In the end, the best way to review design as a non-creative without watering it down is to stop asking whether the work flatters the room and start asking whether it serves the job. The moment design feedback shifts from personal taste to objective-led critique, stakeholder feedback becomes far more useful and far less destructive. That is when non-creatives stop being accidental editors of the work and start becoming serious partners in evaluating creative work properly.
Shawnee Dee April 4th, in the evening
Thank you for sharing.