The Thing Nobody Wants to Hear
As a creative director, most of my day is providing feedback. I review work, I push teams to think harder, I challenge directions that feel safe. It’s the core of the job, and I’ve been doing it long enough to notice something that genuinely concerns me: most feedback isn’t actually feedback. It’s just people being polite.
We’ve been trained to use the “sandwich method” — say something nice, slip in a small critique, then close with something nice again so nobody’s feelings get hurt. And I get why it exists. Nobody wants to be the person who makes someone feel bad about their work. But here’s the problem: when you prioritize comfort over clarity, nobody actually improves. The person giving feedback feels like they did their job. The person receiving it walks away thinking their work is mostly fine. And the work stays exactly where it was.
Think about going to the gym. You could get a trainer who smiles, counts your reps, and never pushes you past what’s comfortable. You’ll show up, barely break a sweat, and leave feeling fine. Or you could get a trainer who pushes you until your muscles are screaming, the kind of session where you’re sore for two days afterward. That trainer isn’t being mean — they’re tearing your muscles down so they grow back stronger. That’s literally how muscle growth works. It hurts during, and the results come after.
Feedback works the same way. If you want to be great at what you do, you don’t need a cheerleader. You need a sparring partner — someone who respects you enough to push you past comfortable and tell you what’s actually not working.
What We Lost When We Went Remote
I’ve been working remotely since Covid, and I genuinely enjoy most of it. But I realized somewhere along the way that I was missing the one thing that actually made me a better designer early in my career: the war room.
Back in agency days, we’d pin work up on big boards, gather the whole team, and go around the room picking things apart. It was intense and sometimes uncomfortable, but it was also the fastest way to level up. You’d present something you were proud of, and within ten minutes you’d see all the things you missed. Not because anyone was being cruel — because they cared enough to be honest.
That environment created a natural feedback loop. You couldn’t avoid critique even if you wanted to, and over time you stopped wanting to avoid it because you saw how much faster you grew when people challenged your thinking.
Remote work killed that loop for a lot of us. I tried to replace it — Reddit, Slack groups, Discord servers. But most of those spaces are either full of trolls who just want to tear things down, or people who are really just looking for validation. Neither of those helps you grow. The trolls make you defensive, and the validation seekers make you complacent.
The Difference Between Hate, Help, and Hype
This is where it gets important, because there’s a real difference between three types of responses you’ll get to your work, and most people lump them all together.
Destructive criticism sounds like “this sucks” or “I don’t like it.” There’s nothing actionable there. It’s someone’s emotional reaction with zero useful information attached. You can’t do anything with it except feel bad, so it’s essentially worthless as feedback.
Empty praise sounds like “this is great!” or “love it, no notes.” And honestly, this one is more dangerous than the trolls because it feels good. It confirms what you want to believe — that the work is done and you nailed it. But it teaches you nothing. You walk away with your ego intact and your skills exactly where they were.
Real critique is the thing in the middle that most people have never actually experienced. Real critique identifies a specific problem, explains why it’s a problem, and either suggests a direction or forces you to solve it yourself. It’s the difference between “I don’t like this font” (opinion) and “this font is illegible at small sizes, which is going to be a problem on mobile” (actionable observation). One is a feeling. The other is information you can actually use.
The best feedback I’ve ever received didn’t make me feel good in the moment. It made me go back to my desk and rethink something I thought was finished. And the work was always better for it.
The Feedback That Sticks Framework
Over the years I’ve noticed that the feedback that actually changes someone’s work — the kind that sticks with you and makes you better — follows a pretty consistent pattern. I’ve started thinking of it as three principles.
1. Be Specific
Vague feedback is almost as useless as no feedback. “Something feels off” doesn’t give anyone a direction to move in. You need to name the thing.
Instead of “the layout feels weird,” try “the hierarchy isn’t clear — my eye doesn’t know where to go first because the headline and the image are competing for attention.” Instead of “I’m not feeling the colors,” try “the color palette feels too muted for a brand that’s supposed to feel energetic and young.”
When you’re asking for feedback, this works in reverse too. Don’t ask “what do you think?” because you’ll get a general impression that’s hard to act on. Ask “does the visual hierarchy guide your eye in the right order?” or “is the user flow from landing page to signup intuitive?” Specific questions get specific answers, and specific answers are the only kind that actually move your work forward.
2. Be Structural
The feedback that sticks tends to address the structure of the work, not just the surface. Surface-level feedback is about taste — “I’d use a different color” or “I prefer sans-serif.” That’s fine for polish, but it doesn’t make you a better thinker.
Structural feedback gets at the decisions underneath the design. Why did you organize the information this way? Does the layout support the story you’re trying to tell? Is the user flow logical or are you making people work too hard to find what they need?
When I review work with my team, I try to spend most of my time at the structural level. If the foundation is solid, the surface-level stuff is easy to refine. If the foundation is off, no amount of polish is going to save it. I’ve seen designers spend weeks perfecting the visual details of a layout that was fundamentally broken at the information architecture level. All that craft was wasted because nobody flagged the structural issue early enough.
3. Be Solutions-Oriented
This is the one that separates good feedback from great feedback. Identifying a problem is useful. Pointing toward a solution is transformative.
You don’t have to solve it for them — that can actually be counterproductive because it takes away the learning opportunity. But nudging someone in a direction is powerful. “The spacing feels tight in this section — have you tried giving the content more room to breathe, maybe breaking it into two sections instead of one?” That’s a suggestion that opens a door without walking through it for them.
The goal is to help the person see options they weren’t seeing before. Sometimes you’re wrong about the solution, and that’s fine. What matters is that you’ve moved the conversation from “here’s a problem” to “here’s a problem and here are some ways we could think about fixing it.” That shift is what makes feedback generative instead of just critical.
How to Actually Ask for Real Feedback
Knowing what good feedback looks like is one thing. Getting it consistently is another, because most people default to being nice unless you explicitly give them permission not to be. Here’s what I’ve found works:
Kill the sandwich up front. When you share work, tell the person: “Skip the compliments. I want to know what’s broken.” That single sentence changes the entire dynamic. You’re signaling that you’re not looking for validation, and that frees the other person to be honest without worrying about your feelings.
Ask targeted questions. “What do you think?” is the worst question you can ask because it invites a general impression. Instead, direct their attention: “Does this typography feel too crowded?” or “Is the hierarchy clear on the first scan?” or “Would this make sense to someone who’s never seen the product before?” The more specific your question, the more useful the answer.
Find people who are better than you. Or at least as hungry as you. This is the hardest part and it’s the most important. Your feedback circle needs to include people who can see things you can’t — whether that’s because they have more experience, a different perspective, or just a sharper eye for the particular thing you’re working on. Feedback from people at your exact level is still valuable, but the real growth comes from people who can show you a level of thinking you haven’t reached yet.
Build the habit. One round of good feedback doesn’t change your trajectory. A consistent practice of seeking honest critique, sitting with the discomfort, and applying what you learn — that’s what compounds over time. The designers I’ve seen grow the fastest are the ones who made feedback-seeking a regular part of their process, not a one-off event.
Building Feedback Culture
If you lead a team, this applies at a bigger scale too. The culture around feedback on your team is probably the single biggest factor in how fast your designers develop.
Start by modeling it yourself. Share your own work in progress and ask for honest feedback from your team. When a CD or design lead shows vulnerability about their own work, it gives everyone else permission to do the same. If the most senior person in the room is open to critique, it stops feeling risky for everyone else.
Create structured moments for it. Regular crits with clear expectations — not “show and tell” sessions where everyone claps, but actual working sessions where the point is to make the work better. Set ground rules: feedback should be specific, structural, and solutions-oriented. Over time, those ground rules become second nature and the quality of your team’s output goes up across the board.
Why I’m Building This
I couldn’t find a place online that offered this kind of raw, structured feedback environment. Everywhere I looked it was either too casual, too toxic, or too focused on validation. So I’m building it.
Thriveful is going to be a community for serious designers who want to grow — a space where you can share work and get the kind of honest, actionable critique that actually makes you better. Not trolls tearing you down, not friends telling you everything’s great. Real feedback from people who understand the craft and want to help you push your work further.
If that sounds like something you’ve been looking for, keep an eye on what we’re building. We’re getting close.
-K
P.S. If you know a designer who’s been stuck and can’t figure out why, send them this. The answer might just be that nobody’s been honest with them yet.
