top of page

Cringe Isn't a Feedback Strategy

How to give clear, honest feedback without making the person on the receiving end feel smaller.


Recently, I received feedback that included the word “cringe.”


Not “this section needs clarification.”

Not “I think the concept is slightly off.”

Not even “this doesn’t sound like me.”


Cringe.


It was memorable, I’ll give it that.


It also reminded me of something I’ve believed for a long time: feedback should improve the work without making the person who created it feel smaller. That doesn’t mean feedback has to be soft, vague, or wrapped in layers of praise.


I’m not suggesting that every correction needs to arrive with a compliment sandwich and a handwritten note.

  • Clear feedback is useful.

  • Direct feedback is useful.

  • Specific feedback is extremely useful.


But humiliation is not a feedback strategy.


We all have unfiltered thoughts. We read something and think, “What happened here?” We sit through a meeting and wonder whether everyone else has quietly lost the plot. We open an email, take a deep breath, and briefly consider moving to a remote cabin with no Wi-Fi. I know this isn't just me.


Those reactions are human. Professionalism is deciding which ones belong in the email.

Good feedback focuses on the work. It tells someone what isn’t working, why it matters, and what a better direction might look like.


For example:

  • “This opening needs a stronger connection to the audience.”

  • “The tone feels more formal than our usual voice.”

  • “This idea needs more support.”

  • “I think we’re solving the wrong problem here.”


All of those statements are direct. None of them are cruel.


They also make it possible for the recipient to do something useful with the information.

That matters because people usually do their best work when they feel safe enough to think clearly. Fear, embarrassment, and resentment don’t sharpen creativity. They narrow it. This is true whether you’re giving feedback to a contractor, employee, colleague, or friend.


Kindness doesn't lower standards. Respect doesn't prevent honesty.


In fact, the clients I’ve done my best work for are usually the ones who communicate clearly, assume good intent, and treat revision as part of the process rather than proof of incompetence.


They tell me when something misses the mark. They also understand that good work is often collaborative. That kind of relationship makes me more willing to take risks, suggest ideas, and care deeply about the outcome. It makes me better at what I do.


The opposite is also true. When feedback consistently feels dismissive, personal, or performative, people start protecting themselves. They stop experimenting. They give the safest answer instead of the best one. Eventually, they may decide the relationship is no longer worth the emotional cost.


That isn’t oversensitivity. It’s information. Feedback reveals more than what someone thinks about the work. It reveals how they view the person receiving it.


So before sending the message, it’s worth asking:

  • Is this specific?

  • Is this useful?

  • Is this about the work?

  • Would I say it this way if the person were sitting across from me?


If the answer to that last one is no, the email probably needs another draft. We can correct the work without flattening the person. We can be direct without being demeaning.


And we can remember that “cringe” may be an honest reaction, but it's rarely a complete communication strategy.

 
 
 

Comments


bottom of page