Give clear feedback without making it personal

To give feedback without damaging a working relationship, describe a specific action and its effect. Then invite the other person's perspective and agree on a useful next step. To receive feedback, listen for the concern, ask for an example and give yourself time to decide what to do with it.

This approach can reduce defensiveness, but it cannot guarantee agreement or repair a difficult history. The wording matters, as does being fair, open to correction and willing to follow through.

Decide whether to ask, offer or raise a concern

Feedback can feel threatening when it seems to put someone's competence or standing in question. The NeuroLeadership Institute describes stress responses associated with both giving and receiving feedback. Asking for input gives the recipient more choice in the exchange, though an invitation alone does not make a conversation safe.

Use your relationship and the stakes to choose an opening:

  • Ask for feedback first when you are building a relationship and want a more mutual exchange: "What could I do differently to make our handovers easier?"
  • Offer an observation when you have a concern about a peer's work: "Would it be helpful to share something I noticed about the handover?"
  • Raise the concern directly when your role requires you to address performance, or when delay could harm the work. You can still offer a choice about timing, but do not imply that the conversation is optional if it is not.

When the other person has more power than you, assess the setting before offering unsolicited feedback. If candid input is not welcomed or you have reason to fear retaliation, consider a safer channel, such as an established review process or a confidential conversation with an appropriate internal contact.

In a new or strained relationship, start with a narrow, recent issue rather than a list of past frustrations. A specific concern is easier to understand and respond to.

Prepare the conversation before choosing your words

Write a private purpose statement. For example:

"I want us to agree on a clearer handover so the next shift has the information it needs."

Then check whether your purpose is developmental or evaluative. Developmental feedback helps someone improve; evaluative feedback tells them how their work measures against an expectation. A conversation can include both, but the distinction matters. If performance is being formally assessed, say so rather than presenting the meeting as informal coaching.

Choose an example you can describe accurately. Separate what you observed from what you inferred. "The handover did not include the revised deadline" is an observation. "You did not care about the deadline" is a conclusion about intent you cannot know.

Choose a private setting for sensitive feedback, and give enough notice that the person knows what the discussion is about:

"Could we talk about how the last handover went? I'd like us to find a way to make the next one clearer."

Do not wait so long that the details become difficult to recall. If you are angry or the other person is under immediate pressure, though, take enough time to prepare. For sensitive issues, a live conversation usually leaves more room than a message to clarify tone and respond to questions. A short written note can be useful for a small, straightforward issue or to record an agreement afterwards.

Choose a framework that fits the conversation

A framework can help you organize your thoughts, but it is not a script to recite without listening. The examples below are illustrative. Each addresses the same situation: a handover omitted a revised deadline, and the receiving team had to ask for clarification.

SBI: A specific incident

Use situation, behavior, impact when you need to discuss one observable event. It is a good default for feedback to a peer or manager because it keeps the concern narrow.

"In the handover yesterday, the revised deadline was not included in the notes. The receiving team had to ask for clarification before they could plan the work. What was happening from your side?"

The situation makes the event identifiable. The behavior names what happened without labeling the person, and the impact explains why it matters. End with a question: the missing information may have a cause you do not know about.

STAR: Performance in the context of a task

Use situation, task, action, result when the person's responsibility and the outcome need more context, such as in a performance discussion.

"For the last handover, your task was to give the receiving team the current plan and deadline. The notes did not include the revised deadline, so the team had to ask for it before planning their work. What made that detail difficult to include, and what would help next time?"

STAR is useful when an isolated action only makes sense against a broader responsibility. Be precise about the result: if you do not know whether the omission delayed the work, do not say that it did.

COIN: A conversation about what to change

Use connect, observe, impact, next steps when you want to work through a recurring issue together.

"I'd like our handovers to be easier for both teams. In the last one, the revised deadline was missing from the notes, and the receiving team had to ask for clarification. How can we make sure the current deadline is visible next time?"

COIN brings the working relationship and a possible change to the foreground. Do not rush from impact to your preferred solution: the other person may know about a constraint you have missed.

None of these models replaces the need to explain a formal expectation or consequence where one applies. They can help you communicate the issue, but they do not determine the outcome.

Make room for a different account

After describing the issue, stop talking. Ask "What's your perspective?" or "What am I missing?" Listen for information that could change your understanding, not just for a response you can rebut.

Paraphrase before moving to a solution:

"You're saying the deadline changed after you sent the notes, and you weren't sure who should update them. Have I understood that correctly?"

If the other person corrects a fact, acknowledge it. You can revise your account without abandoning the underlying concern:

"I had the timing wrong. The deadline changed after your handover. We still need a reliable way for the receiving team to see changes. What could work?"

Avoid "always," "never" and character labels such as "careless." They invite an argument about the person rather than a discussion of the work. Avoid hiding the concern between compliments, too. Recognize good work when you mean it, but make the issue clear enough that the person knows what you are asking them to address.

Respond to emotion without guessing its cause

If you notice your own frustration, pause before continuing. Put both feet on the floor, take a slow breath and look at your notes. You do not need to suppress the emotion; the aim is to keep it from deciding what you say next.

If the other person seems upset, describe what you can observe and check rather than naming their emotion as a fact:

"I can see this is difficult to discuss. Would a short pause help, or would you prefer to continue?"

Do not use a pause to avoid the issue indefinitely. Agree on when to return, especially if a decision is needed. If the discussion becomes hostile or you do not feel safe, end it and use an appropriate workplace channel.

Emotional intelligence includes recognizing and regulating your own emotions as well as paying attention to others'. For more on applying those skills in a management role, see emotional intelligence for cross-cultural managers.

Receive feedback without agreeing too quickly

Your first job is to understand the feedback, not to accept every part of it. If you feel defensive, pause, breathe and take a note. A brief silence is better than agreeing to a change you have not understood.

Ask questions that turn a broad judgment into something you can examine:

"Can you give me an example of when that happened?"

"What was the effect on your work?"

"What would you like to see me do differently?"

Then summarize what you heard:

"The main concern is that my updates arrived too late for you to plan. You'd like an earlier indication when the timing may change. Is that right?"

Thanking someone for explaining their concern is not the same as agreeing with it. If you need time, say so and propose a return point:

"I want to consider this properly. Can we reconvene tomorrow after I've reviewed the details?"

If the feedback feels inaccurate, separate the parts. You might disagree with the description of your intent while accepting that the outcome caused difficulty:

"I don't agree that I withheld the update deliberately. I can see that you received it late. Let's look at what happened and how to prevent that."

Bring relevant notes or examples to the follow-up. If the feedback is vague, discriminatory or connected to a formal decision, you do not have to resolve it through conversation alone; consult the relevant workplace policies and appropriate support channels.

Adapt to the relationship and communication style

When giving feedback to your manager

Focus on a change that would help the work, not a verdict on their leadership. Choose a private setting and consider whether there is an established opportunity to offer input.

"When priorities changed during the project, I wasn't sure which task to pause. Could we agree on what I should stop when a new urgent request comes in?"

If the response is dismissive or the power imbalance makes speaking up risky, do not assume better wording will solve the problem. Decide whether another channel is appropriate.

When giving feedback to a peer

You may not have authority to set expectations for a colleague. Describe the effect on your shared work and ask for an agreement rather than issuing an instruction.

"When the handover arrives without a named owner, I spend time working out who can answer questions. Could we add an owner to future notes?"

For an ongoing partnership, agree on how you will raise small problems: directly after the work, in a regular conversation or in writing. Ask what each of you is comfortable having shared with others.

When communication preferences differ

Do not assume that someone wants direct or indirect feedback because of their background or personality. Ask what helps them receive it, and adjust your delivery without making the message so indirect that the concern disappears.

For a closer look at those trade-offs, see direct and indirect feedback in global teams.

Turn the conversation into a workable agreement

End with a specific change, who will make it and when you will check whether it helped. Include any support or dependency: a person cannot fix a handover process alone if they do not have access to the information they need.

"For the next handover, you'll include the current deadline and I'll flag any later changes in the shared notes. Let's check after the next handover whether that gives the receiving team what it needs."

At the check-in, look at what happened rather than relying on either person's memory of the original conversation. If the change worked, say what improved. If it did not, ask whether the expectation, resources or process need adjusting. Keep notes proportionate and share them only with people who need them.

Over time, trust also depends on what happens when someone raises a concern. Psychological safety means people can take interpersonal risks, such as asking a question or admitting a mistake, without expecting to be humiliated for doing so. Leaders can support it by acknowledging their own errors, responding fairly to disagreement and acting on concerns rather than merely inviting them. A recurring team discussion can help, but a ritual is not a substitute for those responses.

These are communication strategies, not legal or HR compliance advice; consult your workplace policies and an appropriate HR professional for individual performance-management procedures.

The members' bonus provides reusable scripts and a follow-up record for your next feedback conversation.