Give constructive feedback by describing a specific action, explaining its effect and agreeing on what to do next. Receive it by asking for examples and separating what you can use from how the message was delivered.

On an international team, the same words can sound helpful to one person and harsh or vague to another. Rather than guessing from someone's background, ask how they prefer to exchange feedback. Check that you both understand the outcome.

The examples below are illustrative.

Use situation, behavior and impact to make feedback useful

One starting point is situation, behavior and impact: name when something happened, describe what you observed and explain why it mattered. Then invite the other person's view and discuss a next step.

Compare:

You're unreliable. You need to communicate better.

With:

On the client report, I received your section after the agreed handoff. I had less time to review the full draft before sending it. What got in the way, and how could we flag a delay earlier next time?

The second version gives the person something to respond to. It also leaves room for information you might not have: perhaps the handoff changed, the instructions were unclear or another priority took precedence.

Use the framework as a guide, not a speech to memorize:

Situation: Choose a particular meeting, task or exchange.
Behavior: Describe what you saw or heard, not what you think the person intended.
Impact: Explain the effect you observed. If it is your interpretation, say so.
Conversation: Ask for their perspective before settling on a solution.
Next step: Agree on a change within someone's control.

The CIPD evidence review describes useful feedback as specific, relevant, constructive, credible and unbiased. Check your facts before speaking, and make the main point clear enough that the other person knows what needs to change.

Choose what to reinforce and what to correct

When something works, name the action and its value so the person knows what to repeat:

In the project meeting, you summarized the open decisions before we finished. That helped me understand what the team still needed from me. Please keep doing that in future meetings.

Use corrective feedback when the person needs to identify and close a gap. The CIPD review found that negative feedback was more effective than positive feedback for tasks involving precision, risk or prevention. For creative tasks, positive feedback worked better. In practice, point out a missed safety check clearly; when reviewing an early creative idea, identify what works and discuss how to develop it toward the goal.

That does not mean ignoring a creative brief or withholding praise from careful work. Match the message to the task.

Corrective feedback also depends on the relationship and the standard. UIC Business reports that negative feedback improves performance when the recipient trusts the giver and expectations have been explicit. If either is missing, start by clarifying the goal, acknowledging any unclear instructions and listening to the other person's account.

Do not manufacture praise to surround a serious concern. Genuine appreciation can stand on its own, and a correction deserves enough space to be understood.

Discuss a missed deadline without assigning blame

Before the conversation, check what was agreed. If the deadline or priority was unclear, own your part rather than presenting the issue as solely the other person's failure.

A vague opening such as "You always miss deadlines" invites an argument about always. A more useful conversation might begin:

We had agreed I would receive the draft before the team review, but it arrived after the review started. I couldn't include the latest changes in the discussion. How did the timing look from your side?

Suppose the colleague explains that they were waiting for information from another team. You might agree:

Next time, if you're blocked, could you send me a short update before the handoff? Then we can decide whether to move the review or work with what we have.

If you manage the person, check whether they had the authority, time and resources to meet the expectation. A request to communicate earlier helps only if someone is available to respond and make a decision.

Address a communication clash without judging personality

Labels such as "aggressive," "too quiet" or "unprofessional" can obscure the behavior you want to discuss. They can also turn a difference in communication style into a judgment about character.

Instead of "You're too aggressive in meetings," try:

In the planning meeting, I noticed you responded before I had finished explaining the proposal. I lost my place and didn't get to share the concern about timing. Could we let each other finish before responding?

Then listen. The colleague may have understood the exchange differently or may not have realized you were still speaking. If the issue is a team pattern, propose a shared practice, such as inviting comments after each person has finished.

If you were the one who interrupted, acknowledge the effect without debating your intention:

I thought I was keeping the discussion moving, but I can see I cut you off. I'll pause and check whether you've finished.

Adapt directness while preserving dignity

In a low-context style, the speaker tends to put the main point into words. In a high-context style, the relationship, setting and surrounding cues may carry more of the meaning. These are ways to notice differences, not labels to assign to individuals. Preferences can change with the topic, relationship and risk involved.

For a colleague who prefers direct wording, you might say:

The proposal needs a clearer recommendation. Please add the option you recommend and the reason for it before the review.

For someone who prefers a softer opening:

Could we make the recommendation more explicit before the review? It may help the team decide which option to take.

Both versions identify the change. The second should not conceal a requirement. If the change is essential, say so respectfully:

We need that recommendation in the version we submit. Would you be comfortable adding it, or should we discuss the options together?

Consider face-saving: protecting someone's dignity and standing while discussing a problem. A private conversation, an invitation to explain and a focus on the work rather than the person can make it easier to address a concern without public embarrassment. The guide to saving face in Asian cultures explains the idea; do not assume every colleague values or interprets it in the same way.

Silence is not proof of agreement, and a polite "yes" may not mean a request was understood as mandatory. Check the plan without testing or embarrassing the person:

Just so we leave with the same plan, what will each of us do before the review?

For more context, see high-context and low-context communication and direct and indirect feedback styles.

Make it safer to disagree across seniority

Psychological safety means people can raise questions, admit uncertainty or disagree without expecting humiliation. You cannot create it just by saying "be honest." People judge whether it is safe by what happens after they speak.

Give corrective feedback privately, share the topic in advance when practical and ask what you may have missed. Acknowledge your contribution if unclear instructions or decisions created part of the problem. Do not promise confidentiality you cannot guarantee.

When someone challenges your view, resist arguing immediately:

Thank you for telling me. I see the situation differently in one respect, but I want to understand your example first.

When giving feedback upward, focus on the work and make a specific request:

In the last planning meeting, the priority changed after we had started the draft. I was unsure which work to stop. Could we confirm what should be deprioritized when a new request comes in?

If speaking up feels risky, seek guidance from a trusted person or an appropriate internal channel. If the concern involves harassment, discrimination or another serious issue, use the relevant reporting route rather than treating it only as a difference in feedback style. Follow organizational policies and local labor-law requirements; consult a qualified professional about your individual situation.

Receive feedback without having to agree immediately

Listening is not the same as accepting every judgment. First, understand what the person is asking you to consider.

If you feel defensive, pause before explaining. Ask for an example and the standard they had in mind:

Could you point me to a moment when that happened?

What would a better approach have looked like in that situation?

Is this a suggestion, or a change you need me to make?

Separate the observation from the label. If someone says, "You aren't collaborative," an example may reveal a specific issue: perhaps you made a decision without checking with a colleague. You can examine that action even if you disagree with the label.

If the feedback is broad, unfair or contradictory, say what you need:

I want to understand the concern, but I can't act on "be more proactive" yet. Could we identify a recent situation and what you wanted me to do differently?

You can also take time before responding:

I'd like to think about this and come back with a proposal. Can we revisit it at our next check-in?

Afterward, note the observation, your emotional reaction and one concrete experiment. For example: "My update did not identify the decision needed; I felt embarrassed; I'll put the decision at the top of the next update." This separates useful information from your immediate reaction without requiring you to accept an unfair judgment.

Choose the right channel for remote and hybrid feedback

A written message gives the recipient time to read and respond when schedules do not overlap. It also removes tone of voice. Use writing for a specific, limited point; offer a conversation when the topic is sensitive or the context is uncertain.

In a shared document, instead of "This section doesn't work," write:

In the recommendation section, I can see the options, but I'm not sure which one we want the reader to choose. Could you add the recommendation and a brief reason? Happy to talk it through if I've missed the intended structure.

For a higher-stakes example, suppose you notice that a report due for release may contain unverified figures. First, follow the appropriate process to prevent an inaccurate release; do not wait for a feedback conversation if the issue needs immediate action. Send the colleague a private factual message:

I found figures in the report that I can't trace to the source. I've flagged the report for a check before release. Can we speak privately about what happened and how to verify it?

In the conversation, explain what you found, ask for their account and agree who will check the figures. The source may exist, or the verification process may have been unclear. Afterward, confirm the practical agreement privately:

I'll check the source for these figures. You'll add the source reference to the report, and we'll confirm the check before release.

In a call, leave space for pauses. Avoid assuming that silence means disagreement or that a camera must be on for someone to participate. For hybrid teams, record shared decisions where remote colleagues can access them, but do not publish a private feedback conversation without agreeing what belongs there.

Build a feedback loop that leaves time to act

Choose a rhythm that fits the work rather than filling a calendar with feedback sessions. Gallup recommends frequent feedback, including a few times a week for most jobs and close to the action. The CIPD review, however, reports one study in which professionals improved more with monthly than weekly feedback. Neither finding sets a universal schedule: the role, the kind of feedback and the time available to act all matter.

Use a brief comment when it helps someone repeat or correct a specific action. For a broader development issue, agree on a longer interval to try a change before reviewing it.

Ask focused questions:

What is one thing I could change to make my project updates easier to use?

What should I keep doing when we work together?

Look for patterns across people who see different parts of your work. Repeated examples may point to a useful change; conflicting views may reveal expectations worth discussing.

Close the loop:

You mentioned that my updates made it hard to see decisions. I've started putting the decision needed at the top. Is that more useful?

The Pro section adds reusable rituals and scripts for hybrid teams.

Set up a hybrid feedback ritual without creating more meetings

Agree on the purpose and channel before choosing a frequency. A useful arrangement separates quick feedback about an action from a deeper discussion about a recurring pattern.

At the start of a project, ask each person privately:

When I have a small suggestion, would you rather receive it in the document or in a private message? For a sensitive issue, would you prefer a note before we talk?

Make clear that preferences guide the conversation but do not replace required processes. Also agree where work decisions will be recorded so that colleagues who are not in the office can see them.

During the project, use a short private message for a limited observation:

In today's handoff, the open question was easy to find at the top of your update. That helped me respond quickly. Please keep that format.

For a recurring issue, reserve a check-in for the pattern rather than sending a stream of corrections:

I've noticed that we have had to clarify the owner of several decisions after meetings. I'd like to compare what each of us thought was agreed and settle on a way to record ownership.

At the check-in, choose one change, an owner and a point at which to review it. Record the agreed work process in the shared project space; keep personal feedback private. At the review, ask whether the change helped and adjust it rather than assuming the first solution worked.

Use advanced scripts when directness and authority collide

When a request sounds optional but is required

A softer opening can preserve dignity, but it must not leave the requirement ambiguous:

Could we revisit the figures in this section together? They need to be verified before release. I may be missing the source, so please show me how you checked them.

The invitation leaves room for the colleague's knowledge; the second sentence makes the requirement clear.

When a senior colleague gives a vague instruction

Ask for a standard without challenging their authority in public:

I want to make sure I act on your feedback about being more concise. Could we look at one update together and identify what you would remove or move to an attachment?

If the answer remains unclear, propose an experiment:

For the next update, I'll put the decision and recommendation first, then keep the background below. Would that meet your expectation?

When a colleague agrees in the meeting but the work does not change

Do not assume bad faith or blame their communication style. Reopen the agreement privately:

We agreed the recommendation would be added before review, but I don't see it in the draft yet. Was my request clear, and did something prevent you from making the change?

Listen for a different understanding, a competing priority or a missing resource. Then confirm the revised plan and who owns the next action.

Giving and Receiving Feedback at Work: International Guide