Workplace Criticism Is Not Swinging a Hammer, but Offering a Ladder

At a weekly meeting, my manager suddenly looked at me and said: "Your report wasn't prepared thoroughly enough, so we had to schedule an extra meeting. If this continues, it will easily slow down progress."

I froze on the spot, my face burning. It wasn't that he was entirely wrong, but the way he said it embarrassed me: in front of the whole team, with a harsh tone. In that instant, all I could think about was defending myself, and I couldn't calmly consider how to improve.

After the meeting, I felt more and more frustrated. If he had told me "which part wasn't thorough enough and what to pay attention to next time," I could have adjusted immediately. But all I got was a vague label, and the only thing I gained was the frustration of being criticized. It was only after that experience that I slowly realized: criticism is supposed to be a tool to help people improve, but in the workplace, if the method is wrong, it easily becomes a way to tear someone down.

When many people hear the word "criticism," what comes to mind is cold, harsh blame: "Why are you always like this?" "How could you make such a basic mistake?" These words sound like they are "pointing out problems," but their real effect is usually just one thing—putting the other person into defensive mode. As a result, criticism that should be used to drive improvement turns into emotional venting, or even the starting point of a rift in the relationship.

Even worse, some people treat shifting blame as criticism. When a project is delayed, their first reaction is not to review the process, but to say, "They didn't follow up properly." The moment those words are spoken, they might feel relieved, but there is no value for improvement—it just kicks responsibility away. The difference between blame-shifting and criticism is simple: the former aims at self-protection, the latter at improvement. Don't confuse the two.

Truly effective criticism is about helping the other person correct their direction. Its purpose is not to embarrass others, but to make things better. In the end, criticism is not about tearing down the stage, but about building it up.

I once mentored a new hire, Xiao Li, who caused an incident when writing his first deployment script, leading to a brief production outage. After the incident, a manager from a neighboring team publicly questioned him: "How could you make such a low-level mistake?" Xiao Li's face turned bright red, and he didn't dare to speak up for a whole week. Later, when I did a one-on-one review with him, I learned that he actually knew he needed to do validation, but because there was no existing script, he didn't dare to add one himself. So I told him that next time he encounters this situation, he could pause, complete the validation script, and then request the deployment. As a result, he became the most proactive person in the team when it came to writing automation tools. That experience further confirmed my belief: if criticism is about building the stage, the other person will grow faster.

Of course, criticism is not just from superiors to subordinates. In a cross-cultural workplace, I have also experienced the subtlety of "upward criticism." Once, a leader insisted on adding a feature during a review meeting, but our team judged that it would be too difficult to implement. I didn't directly say "no." Instead, I first acknowledged the value of the feature, then added: "However, with the current architecture, the testing cycle would be extended by two weeks. If the launch date remains unchanged, we might sacrifice stability. Should we start with a simplified version and gradually improve it later?" On the surface, this was supplementing information, but in essence, it was also a form of criticism. In the end, the proposal was accepted, and the leader didn't feel that I was "talking back." Often, the trick to upward criticism is to first acknowledge the other person's starting point, then offer constructive corrections.

The way criticism is delivered often determines its effect. Some people are used to calling people out in public, thinking it's the quickest approach, but public criticism can easily make people feel humiliated, leading not to improvement but to strained relationships. In contrast, if the issue is a common process or team-wide problem, pointing it out publicly can help everyone reflect together; but if it's a personal habit or attitude issue, private communication often works better.

The same words, said in a different order, can have completely different effects. Direct criticism makes people instinctively defensive, but if you first acknowledge something positive and then point out the shortcomings, it becomes easier for the other person to accept. For example, "This time your proposal covers most scenarios, but the exception handling could be further supplemented" sounds much smoother than "You didn't consider things thoroughly."

Criticism also needs to be specific. Vague criticism only leaves people confused. "The document isn't well written" has no reference value, but if you say, "If you outline the chapter structure first, readers will understand it more easily," the other person will know exactly how to improve.

In cross-department collaboration, criticism is even more of an art. With information asymmetry, it's easy to immediately say, "Their assessment is inaccurate." But I've seen a development lead whose approach is worth learning from: he would say, "This API change may have affected the schedule. Next time, let's sync up earlier." This way of speaking points out the problem without making the other person lose face, and the relationship remains smooth.

There's another point that is often overlooked: criticism doesn't end when you finish speaking. A good piece of criticism needs a "follow-up action." For example, if you remind a colleague to improve the logic of their PPT, and they actually do better next time, you should give timely feedback: "This time the logic is much clearer." This closed loop helps the other person truly understand that your criticism is not about making things difficult, but about making things better.

Finally, there is one key factor that is often underestimated: tone. A cold tone triggers a reflexive defensive response, while a neutral or even slightly caring tone makes it easier for people to listen. For example, "Why is this report wrong again?" sounds like an interrogation, whereas "I noticed a few inconsistencies between the report and the template. Would you like me to take a quick look next time before you submit?" conveys a collaborative attitude.

Looking back, I increasingly feel that criticism is essentially a form of collaboration. If your only goal is to "point out the problem clearly," it easily turns into friction; but if you treat criticism as "helping the other person build a higher platform," it becomes a lubricant that moves things in a better direction.

So, next time before you criticize someone, ask yourself: Am I tearing down their stage, or helping them build it?

If the answer is the latter, you'll find that many things can be said in a different way.