Browse all patterns

Giving and receiving effective feedback

It's a paradox: everyone know the feeling that it can be nerve-wracking in some situations to give feedback. And at the same times, everyone likes to hear from others how they can continue to grow. Good news though: giving and receiving feedback is like a muscle you can train. Use this pattern to give feedback that lands well and to receive it with an open mind.

Common misconceptions

There are some common misconceptions that stop people from giving feedback:
  • "If I give feedback on something, it will turn into a big thing." The opposite is true. By not speaking up promptly about what you observed and how it affected you, you increase the chance it does become a big thing.
  • "What I noticed is too small to give feedback on. Feedback has to be about something Big and Very Important." Small, daily feedback is exactly what matters most. Research shows that direct, timely feedback leads to behavior change far more often than feedback that has been saved up. Waiting robs the other person of the chance to learn and grow quickly.
  • "Giving feedback is for more experienced people. You do that after X years of work experience." Wrong. Newcomers often see things most clearly precisely because of their fresh perspective. Speak up.
  • "If I give feedback, it will threaten the good atmosphere." The opposite is true. Saving things up and eventually exploding is what threatens the atmosphere. Good feedback strengthens the relationship. The principle: be soft on the person, firm on the content. Radical candor, not radical avoidance.
  • "If I give feedback in between, I'll have little to add in a reflection session." Repetition is exactly right. Feedback in a reflection session should never come as a surprise. It should be a summary of feedback you have already given along the way.

How to give feedback

Ground rules in practice:
  • Give feedback asap. The closer feedback follows the behavior, the more likely the receiver learns from it. Waiting weeks or months reduces impact.
  • Positive feedback in public, critical feedback in private. Praise someone in front of the team. Address concerns one-on-one. If something bothers you, say it to that person directly, not to other colleagues.
  • The one exception: you may talk through your situation with one trusted colleague to think through how to deliver the message. If a colleague comes to you with complaints about someone else, the right response is: "So you want to think through with me how you're going to bring that up with them?"
  • Prepare before you speak. A good feedback conversation stands or falls with preparation. It helps you:
  • describe concrete examples rather than vague patterns;
  • put your feeling into words precisely;
  • stay out of attack or defense mode;
  • deliver your message with respect.
  • Be concrete: use clear language, avoid vague language. Clear feedback names things precisely. Vague feedback leaves the receiver guessing. Stop using pronouns. Phrases like "this behavior", "that message"," "pay attention to this" or "do these things differently from now on" tell the receiver nothing they can act on. Replace every vague reference with the concrete noun: the specific behavior, the exact situation, the precise action you are asking for.
Example:
  • Instead of: "That is something I'd like you to change."
  • Say: "I'd like you to send the client a response within 24 hours of receiving a message."
Effective feedback follows a clear sequence:

Step 1: Ask permission

Before saying anything, check whether the other person is ready to hear it.
  • Ask for a "micro-yes": a small agreement that signals their brain is open and they are willing to engage.
  • If the moment is wrong, agree on a better time rather than pushing through.
Examples:
  • "Do you have five minutes to talk about how that meeting just went?"
  • "I have a few ideas about how we could improve X. Can I share them now?"

Step 2: Name the behavior

Describe what you observed, not what you think of it.
  • Stick to what you saw or heard, not your interpretation.
  • Be concrete, specific, and actionable. Vague feedback ("you're difficult") cannot be acted on. Precise feedback ("you interrupted me twice before I finished") can.
  • Speak in the first person. Start sentences with "I noticed" or "I saw", not "you always".
Examples:
  • "I saw you arrive at 11:00 when we had agreed on 10:30."
  • "You didn't greet the clients when they came in."
  • "You missed two deadlines last week."

Step 3: Name your feeling

Say how the behavior affected you.
  • Speak for yourself , not on behalf of the team or "everyone".
  • Name the feeling itself, not a judgement dressed up as a feeling ("I feel like you don't care" is a thought, not a feeling). See the examples below⁠.
  • You can also name the underlying need or positive intention that makes this worth raising.
Examples:
  • "I feel frustrated."
  • "I feel upset, because openness and trust matter to me in a working relationship."
  • "I feel worried, because collaboration is important to me."
  • "I'm saying this, because I believe in you and what you're capable of."
  • "I'm giving you this feedback, because I want our working relationship to improve."
Not every sentence that starts with "I feel" expresses a genuine feeling. Know how to distinguish:
Pseudo-feelings (thoughts dressed as feelings):
  • "I feel not taken seriously." (... by you)
  • "I feel unheard." (... by you)
  • "I feel frustrated." (... by you)
  • "I have the feeling I'm being ignored." (... by you)
Each of these says more about how you interpret the situation than about what you actually feel. They also implicitly blame the other person.
Genuine feelings (stay with you):
  • "I feel sad, because I need respect."
  • "I'm angry, because openness and trust matter to me in a working relationship."
  • I feel worried, because collaboration is important to me."
The difference: a genuine feeling names an internal state and, optionally, the underlying need. It does not point a finger.

Step 4: Name the consequence

Explain the effect of the behavior on the work or the organization.
  • Stick to facts , not predictions or worst-case scenarios.
  • Pick the most important consequence. One strong point lands better than a long list.
Examples:
  • "Because you arrived late, your colleague had to stay longer."
  • "Because the presentation was finished late, I had to work in the evening."
  • "Because you don't greet clients when they come in, they feel less welcome."

Step 5: Make the desired behavior explicit

End with a clear request and make space for the other person to respond.
  • Close with a request , either a connection request ("Can we talk about this?") or an action request ("Will you do X going forward?").
  • Check whether the feedback lands. Ask if the other person recognizes what you're describing before moving to solutions.
  • Make concrete agreements where possible.
Examples:
  • "Does this resonate with you?"
  • "How do you see this?"
  • "What solution can you think of?"
  • "What do you think we could both do to improve our collaboration?"
  • "Would you be willing to be in the office by 9:00 on Wednesdays going forward?"
  • If you receive a no to a request: "Can you tell me what would work for you?"

How to receive feedback

Receiving feedback well is a skill too. Three principles:
  • Thank the giver and accept the feedback , even if you disagree with it. Acknowledgment is not the same as agreement.
  • Ask for clarification if you don't understand straight away: "What do you mean exactly?" or "Can you give me an example?".
  • Decide for yourself whether you agree and what, if anything, you want to do with it. You are not obliged to act on every piece of feedback, but you are responsible for deciding consciously.
Examples:
  • "I wasn't aware this was affecting you this much. Thank you for telling me."
  • "What do you mean exactly?"
  • "Can you give me an example of when and how I did that?"
  • Only if you genuinely mean it: "I'll work on it."

Learn more

Recommendations to read/view:

Have you adopted this?

Not adopted
Adopted as written We took it over without material changes. Adopted with changes All of it, with some details changed. Adopted in part We took some sections or ideas. Planned We plan to adopt it.

Choose to receive updates on this pattern.

23 Oct 2026 by Eva