The slide says 18. On Lin Mei’s laptop, the latest tracker says 12. Her manager, Chen, has just told a meeting room in Hangzhou that 18 stores are ready for a promotion. Across the table, a logistics colleague has started planning the next day’s deliveries. Mei has a few seconds to decide what to say and how much of the disagreement the room needs to hear.
Imagine that meeting in an ordinary Chinese office, where a conversation can start around a table, continue in a WeChat group, and finish in a one-to-one message. The scenes here are fictional, but the choices will feel familiar to anyone who has hovered over Send. In Chinese, people sometimes talk about mianzi, often translated as ‘face’. In a meeting like this, it can mean something quite practical. Can the person who gave the number check it and correct it without having to defend their competence in front of a room?
Three ways feedback can embarrass a colleague
Correcting your manager in front of the team
Mei could say, ‘Chen, you pulled the wrong number again.’ The word ‘again’ invites the room to consider Chen’s track record while everyone is still waiting for the store count. The logistics colleague needs a number to plan around. The conversation about how Chen’s slides are updated can happen after the meeting.
If the slide is a rough agenda for next week and nobody will act on it today, Mei can wait until the room clears. ‘I saw 18 on the slide and 12 in the tracker. Can we check what each one counts before the deck goes out?’ That wording gives Chen room to say where the figure came from. Sometimes a discrepancy comes down to two people using the same word, such as ‘ready’, for different stages of the work.
Naming a junior colleague in the work group chat
Later, Chen notices that the delivery sheet posted by Yu, a junior coordinator, is missing two store contacts. He starts typing in the project’s WeChat group. ‘@Yu, you forgot the contacts again. Everyone is waiting.’ The warehouse team does need to know when it can use the sheet. The tagged message gives a wider audience something else to remember as well. It links Yu’s name to a mistake in a thread that people may scroll back through, quote, or screenshot.
Chen can post a usable update in the group. ‘Two store contacts are still missing from the delivery sheet. Please hold the dispatch calls until I post the updated link by 3 p.m.’ Then he can message Yu directly. ‘Can we look at the two blank contact fields? I’d like to know what was available when you uploaded the sheet.’ Yu gets a chance to explain. The warehouse team gets a time and a clear instruction.

Pointing out a peer’s mistake as a joke
At lunch, Mei’s teammate Gao sits down with a bowl of noodles. Someone says, ‘Keep Gao away from the shared drive. We’ll get a fourth “final” file.’ A few people laugh. Gao laughs too and goes back to his lunch. His laugh tells you very little about how the line landed. The problem that sent two teams to different versions of the file is still there.
Mei could catch Gao at his desk and say, ‘I used the file you sent at ten, and support used the one from eleven. Can we pin one link in the project chat?’ If you made the joke yourself, a plain acknowledgment in private gives your colleague space to respond. ‘That crack about the files put you on the spot. I should have asked you about the links directly.’ If the joke also left the group with a false impression, correct that impression where people heard it.
Choose the audience before you choose the words
A work chat is useful because everyone can see the revised link or figure without sitting through another meeting. That same reach changes how criticism lands. A manager’s quick tap on an @mention can make a missed field feel like a team-wide judgment, especially for a new employee who has to keep working with everyone on the thread. A direct message works well for a narrow question. A short call or a quiet room works better when the answer depends on tone, context, or several rounds of questions.
Teams in China vary in how openly they disagree. At one office, junior staff may routinely flag discrepancies in a meeting. At another, a new hire may need a manager to invite questions before speaking. Pay attention to who can challenge whom and what happens afterward. Before you post, ask who needs the update to do their job and who can help you understand what happened. The two audiences often have different sizes.
How to give difficult feedback in private
Chen asks Yu to step into a small meeting room. He starts with something Yu actually did. ‘You got the delivery windows back from all the stores yesterday. That gave the warehouse enough time to plan the route.’ Then he points to the sheet. ‘The version you uploaded at 11 had two blank contact fields. The warehouse paused the dispatch calls because they didn’t know whom to call at those stores. What did you have when you sent it?’
Yu says, ‘Those two stores had confirmed their delivery windows. I was still waiting for the phone numbers. I thought sending what I had would give the warehouse a head start.’ Chen hears a decision he can work with. ‘Next time, can you mark the missing numbers as pending and give us a time for the next update?’ Yu checks his notes. ‘Yes. For today, I’ll call both stores now and send you the revised link by 2:45.’

The sequence is simple. Recognize a specific contribution, describe what happened and what it affected, then agree on the next action together. Specific recognition helps Yu keep a part of the process that worked. The timestamp and the blank fields give him something concrete to explain. As the person receiving feedback, he can check his understanding before leaving the room. ‘So the warehouse can start planning with a partial sheet as long as I mark what’s pending and say when I’ll update it?’ Now both people can tell whether they’ve agreed to the same thing.
When a key number needs correcting on the spot
Back in the morning meeting, the logistics colleague is about to plan deliveries around the figure on Chen’s slide. Mei speaks before the discussion moves on. ‘Could we pause on the store count? The tracker I have shows 12 confirmed. Does the 18 on the slide include stores that are still pending? Can we check before we book the deliveries?’
Chen opens the tracker. Six stores are still awaiting confirmation, so he asks logistics to plan for 12. If the two sources can’t be reconciled in the room, someone can name the uncertainty and set a checkpoint. ‘We have two counts in circulation. Let’s hold the bookings while Mei and I check the source. We’ll post the confirmed figure before noon.’ When it’s verified, the correction belongs wherever people are relying on the old number, whether that’s the meeting notes, the group chat, or both.
By the time the warehouse opens the updated sheet that afternoon, it needs two reliable things from the team: the confirmed store count and contact details for the calls. Yu needs to know how to flag missing information next time. A clear update in the group and a few minutes in a small meeting room can give each person what they need to get on with the work.
















Leave a Review