Bad Feedback Is Often a Framing Problem

Designers like to commiserate over terrible stakeholder feedback: “Make the logo bigger,” “It doesn’t feel right,” or the ever-vague “Can you make it pop?” It’s easy to blame the client, but if this happens regularly, the common denominator might be the designer. The issue often isn’t the audience’s taste — it’s how the work was presented and what questions were asked.

Too many design presentations walk viewers through a linear history of every iteration. “First I tried this, then I tried that” is meaningful to the designer but tedious for everyone else. When no business problem is being framed and no decision is on the table, executives tune out. Then, when the designer finally asks, “So what do you think?”, they snap to attention and deliver exactly what was requested: unfiltered personal opinions. That is the opposite of useful feedback.

## Frame the Problem First

Before showing a single screen, explain what is wrong with the current design and what problem the new version is meant to solve. Design is problem-solving, not a gallery exhibition. If you do show dead ends, tie them to the problem rather than saying “this typeface didn’t work” — vague aesthetic statements invite subjective opinions.

When you reach the final design, engage stakeholders at a strategic level. Explain how the solution addresses the problem, and ideally how you plan to prove it works:

“We’re going to push this release out next week, and we will come back to you with some figures by the end of the month.”

That statement is far more productive than an open-ended “What do you think?”

Ask for the Feedback You Actually Need

Be explicit about the kind of feedback you want. Is it visual style, or is that already locked down by brand guidelines? Often what you really need is agreement that the solution solves the stated problem — so ask that directly.

Flag contentious issues before they surface. If a form has changed from opt-out to opt-in for GDPR compliance, tell the Chief Marketing Officer before they spot it themselves. If you receive feedback, don’t assume it’s a change request. Treat it as free advice, acknowledge it, and say you’ll consider it. When you’re unsure, clarify: if the person isn’t the directly responsible individual (DRI), state that you’ll run it past whoever owns final approval. Executives are usually trying to be helpful; it’s your job to channel that.

Don’t be afraid to state the boundary:

“We’re not looking for feedback on the visual language at the moment, but we would love feedback on X!”

Don’t Fish for Praise

The habit of ending a presentation with “What do you think?” is often a plea for validation. Junior designers ask hoping to be told they’re right. Senior designers genuinely hope they’ve missed something, because good feedback is how they improve.

If you don’t need feedback, say so: “We’re not looking for feedback at this stage.” And when real feedback arrives, especially if it challenges your work, resist the urge to defend. The better response is:

“That’s super interesting — tell me more!”

That invites dialogue. Blurting out reasons why you’re right and they’re wrong just entrenches positions.

Let People Learn From Tangible Failure

Experts can warn until they’re blue in the face — most people still need to experience the failure themselves before the lesson sticks. As a startup advisor, you see this constantly with founders who make avoidable mistakes. The role isn’t to stop them; it’s to be visible when the lightbulb goes on, so they connect the dots between your earlier warning and their eventual success.

Usability testing is a powerful way to accelerate that learning loop. Designers often feel frustrated when stakeholders ignore good advice, but they rarely follow up to make the consequences visible. The responsible person never sees the problem because it’s hidden in data or obscured by process — and so they never learn to listen next time.

Show Work Long Before It’s Polished

Too many designers wait until they think the work is 95% done before showing anyone. When feedback arrives at that point, it feels like being asked to run another ten miles at the end of a marathon. That defensiveness is often tied to self-worth — criticism of the work feels like criticism of the person.

The remedy is simple but uncomfortable: get comfortable showing messy first drafts. Work in progress signals that feedback is expected, so it lands without the sting of rejection. You’ll still have energy to iterate, and you’ll bring stakeholders along rather than ambushing them with a “big reveal.” Kill the reveal moment — it rarely works in your favor.

Rather than waiting until you’ve reached perfection, get comfortable showing work in progress — messy first drafts you know are going to solicit feedback.

Feedback Is a Gift, Not a Threat

Good feedback produces better products with a higher chance of client and peer acceptance. To get it, designers need to show work early, present the business case for their decisions, and ask precise questions that steer the conversation where it needs to go. The best designers know the difference: good designers hope to be proved right, but great designers want to be proved wrong — because that is the fastest way to learn.