Quick answer

There is no single best feedback model, the right one depends on the conversation. Match the model to the moment: something quick for everyday feedback, something more collaborative when you need shared understanding, something that checks in on emotion when a strong reaction is likely, and a different skill altogether when you’re on the receiving end.

Four ways to match the model to the moment:

  • Everyday feedback: AID or COIN, quick enough to use in the flow of normal work.
  • A difficult conversation: CEDAR, when you need shared understanding rather than a delivered verdict.
  • A likely emotional reaction: BIFF, which builds in an explicit check on how the person is feeling.
  • Receiving feedback: RADAR, to take it in without becoming defensive.

The aim isn’t to memorise every model on this page. It’s to build enough range that you can match the model to the conversation in front of you.

This page brings together a curated set of proven feedback models and practical guides that show how feedback actually works in everyday leadership practice.

It includes widely used frameworks such as AID, BOOST, CEDAR, COIN, SBI, BIFF and RADAR, alongside applied tools for team feedback, receiving feedback, and handling emotional reactions. Together, they cover the full feedback cycle, from preparing and giving feedback, to receiving it, to embedding learning and improvement.

Wherever possible, original sources are referenced so you can explore the foundations behind each model and adapt them with confidence in your own leadership context. Where a model has no single traceable origin, I have said so rather than inventing one.

Who this page is for

This hub is designed for:

  • Leaders and managers who want to give feedback with clarity and confidence
  • HR, L&D and OD professionals designing feedback frameworks
  • Coaches and facilitators looking for open, usable feedback models
  • Teams building a stronger feedback culture

Jump to a model

AID · E2C2 · AIR · BOOST · CORBS · FAST · CLEAR · CEDAR · BIFF · COIN · DESC · SBI · RADAR · Feedforward · Team feedback tools · WWW/EBI · Feedback sandwich · Feedback excuses · Receiving feedback · Negative reactions

Which model should I use?

If you already know roughly what kind of conversation you’re walking into, this is the fastest way to pick a starting point.

Situation Model Why
A quick, everyday check-in AID, E2C2 or AIR Three or four steps, quick enough to use in the flow of normal work
You want to catch mistakes before you even open your mouth BOOST, CORBS, FAST or CLEAR All four are preparation checklists rather than delivery scripts
The conversation needs shared understanding, not just a verdict CEDAR Builds in a genuine joint diagnosis stage rather than a delivered conclusion
You’re anticipating a strong emotional reaction BIFF Includes an explicit pause to check how the person is feeling
You want a coaching-style, exploratory conversation COIN Choose a “push” or “pull” delivery depending on how directive you want to be
You need to be assertive about the effect on you specifically DESC Built for stating the impact on you directly, without escalating
You want the original situation-behaviour-impact model SBI CCL’s own licensed model, see the note below for the open alternatives

AID feedback model

AID is my personal favourite and structures feedback around three moves: the Action you actually observed, its Impact, and the Development or Desired behaviour that follows. It keeps the conversation anchored in what happened rather than in your interpretation of someone’s intentions or character, which is what makes it hard to argue with and quick to use in the flow of everyday work.

  • Action: Name it first, limiting yourself to one or two things the person can realistically act on rather than a list that dilutes the message.
  • Impact: Explain the effect, on the result, the team, the customer or the process, since praise or correction without impact rarely lands.
  • Development or desired behaviour: Ask what needs to change or improve, ideally letting the other person suggest it first, which tends to produce more ownership than simply telling them.

How it sounds in practice

Action: I noticed you were fifteen minutes late to the client meeting. Impact: This made the team feel rushed, and we had to skip the introductions. Development: Going forward, I need you to log on five minutes early so we start on time.

Do Don’t
Limit yourself to one action the person can genuinely digest List ten things at once and expect all of them to land
State the impact even when the feedback is positive Say “well done” without saying what made the difference
Ask what they think needs to change before telling them Jump straight to prescribing the fix

Read the full AID feedback model guide →

E2C2 feedback model

E2C2 is one I put together myself a decade or so ago, as part of a short practice project I ran on Twitter called 100 Days of Biz Acronyms. The two doubled letters, Evidence and Effect, then Change and Continue, are shorthand for a simple structure: point to what actually happened, say what it did, then agree what happens next.

  • Evidence: Point to the specific evidence you observed, the actual moment, rather than a general impression built up over time.
  • Effect: Name the effect it had, on the result, the team, the customer or the work.
  • Change: State the change you are asking for or, for positive feedback, the behaviour that produced the effect.
  • Continue: Agree what continues from here, whether that’s the new behaviour bedding in or the good practice carrying on.

It sits close in spirit to AID, and I’d treat it as an alternative phrasing of the same underlying discipline rather than a fundamentally different model, use whichever language lands better with the person in front of you.

How it sounds in practice

Evidence: The client update you sent on Tuesday had all the numbers and the context in one place. Effect: I didn’t have to chase anyone for detail before the board call. Change: Keep including that context section, it’s what made it usable straight away. Continue: Let’s keep this as the format for future updates.

Do Don’t
Point to one specific piece of evidence Rely on a vague, built up impression
Say what continues, not just what changes Stop at the change and leave the follow through unspoken
Use it interchangeably with AID if the language fits better Treat E2C2 and AID as though they need separate explaining to a team

AIR feedback model

AIR is close in spirit to AID, describe the action, name the impact, then ask for a change, it just phrases the final step as a question rather than a statement. It’s popular in tech, product and UX circles, most visibly through Hyper Island’s facilitation toolbox, though I couldn’t trace it back to one original author, so I’m treating it as a widely shared adaptation rather than a single person’s model.

  • Action: Describe the specific, observable behaviour you saw directly, rather than something reported to you secondhand.
  • Impact: Say what effect it had on you personally, including how it made you feel, not just the practical consequence.
  • Request: Ask for the change as a genuine question, “would you be willing to…”, framed so it is specific, realistic and timely enough to actually happen.

How it sounds in practice

Action: When the sprint review overran by half an hour and we didn’t get to the demo. Impact: I felt frustrated, because the client had specifically asked to see it. Request: Would you be willing to timebox the review more strictly next sprint, even if that means cutting a few updates short?

Do Don’t
Frame the request as a genuine question Turn “would you be willing to” into an instruction in disguise
Name how the impact made you feel Skip straight to the practical consequence
Use it interchangeably with AID if the framing fits better Treat AIR as a separate discipline to learn on top of AID

BOOST feedback model

BOOST is a preparation checklist as much as a delivery model. It asks whether feedback is Balanced, Observed, Objective, Specific and Timely before you open your mouth, which catches a lot of the ways feedback goes wrong before the conversation has even started.

  • Balanced: Check that you are mixing performance improvement feedback with genuine praise rather than delivering a dump of negative points.
  • Observed: Base it on something you have actually seen, not hearsay or a borrowed opinion.
  • Objective: Focus on the event, not the person, contrasting something like “you have been more than thirty minutes late every day this week” with the far less useful “you are lazy”.
  • Specific: Use an accurate example of what happened and when, rather than a general impression.
  • Timely: Give it as soon as possible after the event rather than saving it up.

How it sounds in practice

Balanced: I want to start with what’s working, then get into what needs to change. Observed: I saw the deck three times before the client call, and twice it still had last quarter’s numbers. Objective: That’s not about effort, it’s about the numbers being current. Specific: This happened on the Tuesday and Thursday drafts. Timely: I wanted to raise it today, while it’s fresh, rather than wait for the review.

Do Don’t
Check your own balance before raising the issue Raise something you noticed weeks ago as if it just happened
Describe the specific moment, not a general pattern Say “you always” or “you never”
Deliver it close to the event, while it is still useful Save it all up for the annual review

Read the full BOOST feedback model guide →

CORBS feedback model

CORBS is a five point checklist that overlaps with BOOST in places, both share a concern with balance and specificity, but it comes out of a different tradition. It is used more in coaching supervision, clinical and educational settings than in general management training, and it puts particular weight on owning your feedback as your own perception rather than presenting it as settled fact.

  • Clear: Say what you mean plainly, without wrapping it in so much caveat or softening language that the message gets lost.
  • Owned: Frame it as your own observation and reaction, “I noticed” or “I felt”, rather than stating it as an unchallengeable truth.
  • Regular: Give feedback close to the event and often enough that it doesn’t become a rare, high stakes occasion.
  • Balanced: Include what is working as well as what needs to change, without forcing artificial positives just to soften a criticism.
  • Specific: Ground it in a particular, observable moment rather than a general impression.

How it sounds in practice

Clear: I want to talk about how the deadline conversations have been going. Owned: I’ve noticed I’m the one raising concerns most weeks, and it’s starting to feel one sided to me. Regular: I wanted to say this now rather than let it build up. Balanced: The work itself has been solid, this is specifically about how we handle timelines. Specific: On the last two projects, we agreed a date, then I only found out it had slipped once I asked.

Do Don’t
Own it as your perception, “I noticed” rather than “you always” Present your interpretation as settled fact
Give it often enough that it stays a routine conversation Save everything for one high stakes moment
Ground each point in a specific, observable moment Offer a vague general impression

FAST feedback model

FAST is another preparation checklist, and it sits close to BOOST and CORBS in spirit, all three are concerned with much the same underlying qualities: being specific, timely and fair, even though the letters land differently. FAST comes from the management author Bruce Tulgan, who set it out in his book Fast Feedback, drawn from his research into what separates managers who give feedback well from those who don’t.

  • Frequent: Give feedback often enough that it becomes a normal part of how you work together, rather than saving it up for a rare, high stakes moment.
  • Accurate: Get the facts right and balance genuine praise with genuine criticism, rather than letting either crowd out the other.
  • Specific: Set out concrete goals with clear parameters, so the person knows exactly what “better” looks like.
  • Timely: Treat it as an ongoing practice tied to the work, rather than an isolated event tied to a review cycle.

How it sounds in practice

Frequent: I want to make this a regular five minutes at the end of our one to ones, not just something that comes up at review time. Accurate: The client call went well, you handled the pushback on pricing calmly, and the follow up email was clear. Specific: For the next proposal, I’d like the draft to include a rough timeline, that’s the piece that’s been missing each time. Timely: I wanted to say this today, while the call’s still fresh for both of us.

Do Don’t
Make feedback a regular five minutes, not an annual event Save it all up for the scheduled review
Balance accurate praise with accurate correction Let one crowd out the other
Give concrete goals with clear parameters Leave “better” undefined

CLEAR feedback model

CLEAR is a fourth checklist model, from the speaker and author Rory Vaden, and it covers much of the same ground as BOOST, CORBS and FAST: keeping feedback specific, timely and free of unnecessary heat. Its distinctive addition is a reminder to keep feedback separate from any feedback you’ve just received yourself, so it doesn’t turn into deflection.

  • Concise: Keep it brief and focused on one issue at a time, rather than a list that overwhelms.
  • Logical: Stay emotionally neutral, and keep praise public while keeping correction private.
  • Explicit: Use a specific, recent example rather than a generalisation like “always” or “never”.
  • Actionable: Focus on the behaviour, not the person’s character, and name the preferred behaviour clearly.
  • Real time: Deliver it as close to the event as possible.

How it sounds in practice

Concise: I want to raise one thing from the workshop. Logical: I’ll say this the same way I would if we were alone, not in front of the group later. Explicit: Yesterday’s client demo ran twenty minutes over, and we lost the closing slot. Actionable: I need the next demo to stay inside the agreed time, even if that means cutting content. Real time: I wanted to mention it today rather than wait until the debrief.

Do Don’t
Raise one issue at a time Dump several unrelated concerns in one conversation
Keep correction private and praise public Critique someone in front of the group
Reference a specific, recent example Say “you always” or “you never”

CEDAR feedback model

CEDAR is built for a genuinely two-way feedback conversation rather than a one-way delivery of a verdict. It moves through Context, Examples, Diagnosis, Agreed action and Review, and its distinctive move is the diagnosis stage, where both people explore what happened together rather than the giver assuming they already have the full explanation.

  • Context: Set up the conversation by framing why it matters and what impact the issue or opportunity is having, so it doesn’t start cold.
  • Examples: Give specific illustrations of what happened, with a clear sense of when and where.
  • Diagnosis: This is where CEDAR earns its keep. Instead of declaring what the problem means, ask for the other person’s view and jointly explore what happened and why, and why it went well or not so well.
  • Actions: Work best when the ideas start with the person receiving the feedback rather than you supplying the answer.
  • Review: Jointly set a date, typically within two to three weeks, to check how it went.

How it sounds in practice

Context: I wanted to talk about how the last two client presentations went, because I think it matters for how the team is seen. Examples: In both, the deck had numbers that didn’t match the report we’d sent beforehand. Diagnosis: What’s your read on why that happened? Actions: What would help avoid that next time? Review: Let’s check in after the next presentation to see if it’s worked.

Do Don’t
Treat the diagnosis stage as genuine exploration Use it as a formality before announcing your conclusion
Set a real review date, two to three weeks out Let agreed actions disappear once the conversation ends
Use it for conversations that need shared understanding Reach for it when a quick AID conversation would do

Read the full CEDAR feedback model guide →

BIFF feedback model

BIFF, as used here, stands for Behaviour, Impact, Future expectation and a check on Feelings: it clarifies what happened, why it matters, what should happen next, and deliberately pauses to notice how the other person is receiving it. It is worth flagging that the same letters are best known for a different tool, Bill Eddy’s BIFF response for defusing hostile written communication. This is a distinct, less formally documented model for giving feedback, closest in spirit to John Tomlinson’s BIF (Behaviour, Impact, Future) framework with an explicit emotional check added.

  • Behaviour: A specific description of what the person has done.
  • Impact: The outcome that behaviour has had on you, colleagues, customers or performance.
  • Future: A plain statement of what you expect in terms of behaviour or performance going forward.
  • Feelings: The genuine pause, an honest check on where the person is emotionally after hearing the feedback, before you decide whether to continue, slow down or stop.

The model works for both positive and corrective feedback, and can be delivered directively or as a more open, exploratory conversation.

How it sounds in practice

Behaviour: In yesterday’s meeting, you cut across two people before they’d finished their point. Impact: A couple of people went quiet after that, and I don’t think we got their full thinking. Future: I need you to let people finish before you respond, even if you disagree early. Feelings: How does that land, is this something you were already aware of?

Do Don’t
Name the future expectation plainly, not just the problem Leave the person guessing what “better” would look like
Pause if you notice a strong emotional reaction Keep talking over visible defensiveness or distress
Use it when the emotional stakes feel higher than usual Reach for it for routine, low-stakes feedback

COIN feedback model

COIN moves through Context, Observation, Impact and Next steps, and is popular in coaching and HR practice for its clean, repeatable flow, most widely documented by MindTools. Some versions distinguish between a “push” delivery, where you state your view directly, and a “pull” delivery, where you invite the other person to reach the observation with you.

  • Context: Create connection with the person and frame the situation before you get into it.
  • Observation: Give a clear, objective description of the behaviour you saw, not your reading of it.
  • Impact: Outline the effect that behaviour has had on the people actually affected by it, which is not always the person in front of you.
  • Next: This is where COIN is most explicit. Say what needs to happen going forward, whether that is continuing something that is working well or changing something that isn’t.

How it sounds in practice

Context: Thanks for making time, I wanted to talk through last week’s handover. Observation: The notes you left for the next shift didn’t include the two open issues from the client call. Impact: The morning team spent almost an hour re-establishing what was outstanding. Next: What would help you capture those before you sign off?

Do Don’t
Keep the context brief, a sentence or two at most Spend so long on context that the point gets lost
Choose “pull” when you want the person to self-diagnose Default to “push” out of habit when pull would land better
Name one concrete next step before you close End on the impact and leave next steps implied

DESC feedback model

DESC comes out of assertiveness training rather than management theory. It was developed by Sharon and Gordon Bower and set out in their book Asserting Yourself, and it is built for situations where you need to be direct about the effect someone’s behaviour is having on you, without tipping into aggression or retreating into vagueness. It pairs well with something like AID or COIN, use one of those to work out what actually happened, then reach for DESC when you need the language to say it assertively.

  • Describe: State the specific behaviour factually, sticking to what you observed rather than your interpretation of it.
  • Express: Say how it affects you or the work, using “I” language rather than accusation.
  • Specify: Be concrete about the change you are asking for.
  • Consequences: Explain what follows if the behaviour changes, or doesn’t, framed as a genuine outcome rather than a threat.

How it sounds in practice

Describe: In the last three planning meetings, my proposals have been discussed after everyone else’s, even when I raise my hand first. Express: I feel overlooked when that happens, and it’s affecting how comfortable I am contributing. Specify: I’d like us to go in the order hands are raised. Consequences: If that happens, I think we’ll get more of the team’s full range of ideas on the table.

Do Don’t
Prepare what you want to say before the conversation Improvise an assertive conversation on the spot
Use “I” language to express the effect on you Open with “you always” or “you never”
Name a genuine consequence Use consequences as a veiled threat

SBI feedback model

SBI anchors feedback in a specific moment, an observable action and a real impact, and it was one of the earliest widely adopted models for keeping feedback objective. I have not written it up in the same depth as the others on this page for a specific reason: SBI is the proprietary intellectual property of the Center for Creative Leadership, so the responsible thing is to point you to their own resource rather than reproduce their model here.

If you want the underlying discipline without the licensing question, AID, E2C2, AIR, COIN, CEDAR, BIFF and DESC above apply the same evidence-based principle, grounding feedback in a specific, observed moment and its impact, and each adds a forward-looking step that takes the conversation somewhere.

Do Don’t
Go to CCL’s own materials if you want the official version Treat this brief description as a substitute for their licensed content
Use AID, E2C2, AIR, COIN, CEDAR, BIFF or DESC for the open equivalent Assume every situation-behaviour-impact model is interchangeable

RADAR model for receiving feedback

RADAR is built for the receiving end of a feedback conversation.

  • Repeat: Repeat what you heard, to confirm you understood it and signal openness.
  • Ask: Ask clarifying questions rather than let vague feedback stay vague.
  • Discuss: Discuss your own perspective, without needing to agree with everything.
  • Align: Align or commit to what will change.
  • Reflect: Reflect afterwards, since this is the step most people skip even though it’s where the real learning happens.

The value of RADAR is that it slows down the instinctive defensive reaction long enough to extract something useful. Repeating and asking buy you time and clarity before you have to respond substantively. Discussing lets you add context without shutting the feedback down. Aligning and reflecting turn the conversation into something you actually act on, rather than something you simply survive.

How it sounds in practice

Repeat: So what you’re saying is the report took longer than expected and that pushed the whole handover back, have I got that right? Ask: Can you give me an example of where the delay caused a problem downstream? Discuss: From my side, I was waiting on figures from another team, but I can see I should have flagged that earlier rather than staying quiet. Align: I’ll let you know as soon as I’m blocked on something, rather than waiting until the deadline. Reflect: I want to build in an earlier check-in for the next project so this doesn’t happen again.

Do Don’t
Repeat back what you heard before responding to it Start defending yourself before you’ve confirmed you understood
Ask for a specific example if the feedback feels vague Accept a vague generalisation without asking for detail
Reflect afterwards, not only in the moment Treat the conversation as over the second it ends

Read the full RADAR process guide →

Feedforward

Feedforward, a term popularised by Marshall Goldsmith, shifts the conversation from analysing what already happened to generating ideas for what could happen next. It works well for a few practical reasons: it is future oriented, so it gives a positive guide to change rather than a rehash of the past; it isn’t taken personally, since you are asking for ideas rather than being judged; anyone can play, so you aren’t limited to feedback from your manager or at a moment someone else chooses; and it is quick, often taking only a few minutes per conversation.

The practical version is simple. Pick one behaviour or capability you would like to improve, choose a handful of people to ask, and request five minutes of their time one to one. Ask for ideas on how to improve it, and only listen, resisting any urge to explain, defend or debate what they suggest. Thank them, note what they said, and once you have collected a few conversations’ worth, reflect on everything you’ve heard and choose which ideas to actually try.

Do Don’t
Ask a wide range of people, not just your manager Limit it to formal feedback moments
Listen only, and note what you hear Argue with a suggestion you don’t think will work
Reflect across everything you collected before acting React to each suggestion the moment you hear it

Team feedback tools

Individual models like AID and COIN are built for one-to-one conversations. When a whole team needs to surface patterns in how it works together, two simple tools tend to do more good than any individual framework: Stop-Start-Continue and the Sailboat exercise.

Stop-Start-Continue asks the team three plain questions: what should we start doing that we don’t do now, what should we continue doing because it adds value, and what should we stop doing because it is getting in the way. Its strength is its simplicity, it needs almost no facilitation skill to run well. Sailboat is an Innovation Games tool with roots in Kurt Lewin’s Force Field thinking, driving forces against restraining ones, popularised in its boat form by Luke Hohmann’s Speedboat exercise. It asks the team two fundamental questions: what is driving or accelerating performance, and what is slowing it down or stopping it. The visual metaphor of wind, anchors and rocks tends to surface things a straight discussion misses.

Do Don’t
Agree what happens with the output before you start Collect a list of frustrations and then do nothing with it
Use Sailboat when the team needs a fresh way to talk Run the same exercise every retrospective until it goes stale
Keep it collective, about patterns, not individuals Let it turn into feedback about one person in the room

WWW/EBI (What went well, even better if)

What went well, even better if started life in schools, as a lightweight way for teachers and observers to give feedback on a lesson without resorting to a formal grading system. It has since found its way into some workplace coaching and team settings, largely because two open prompts are easy to remember and easy to run without training.

  • What went well: Name what worked, specifically enough that it could be repeated on purpose next time.
  • Even better if: Suggest one change, framed as a forward looking possibility rather than a verdict on what happened.

I’d treat it as a light touch tool rather than a substitute for something like AID or CEDAR. It’s quick and low pressure, which makes it useful for frequent, informal check ins, but that same simplicity means it can stay fairly surface level for anything that needs real diagnosis or a harder conversation.

Do Don’t
Use it for quick, informal check ins Reach for it when the conversation needs real diagnosis
Make the “even better if” a genuine, actionable suggestion Let it become a disguised criticism
Keep both halves specific Settle for generic praise and a generic improvement

Feedback sandwich

The feedback sandwich, praise, then criticism, then more praise, is probably the most widely taught and most widely used piece of feedback advice there is. It is included here not as a model to use, but as one worth understanding, since so many leaders were taught it as a default. As I put it to clients, it’s a bit like a sandwich with good bread and bad meat in the middle: not very enjoyable, however it’s dressed up.

There are a handful of reasons it tends not to work. People know what is coming, so the opening praise stops registering as genuine recognition. The point you actually want to make gets smothered in sweetness and can go missing entirely. Telling someone what to think is rarely as effective as asking them, which the sandwich doesn’t leave room for. People often leave the conversation confused about what mattered most. And, put simply, there are better ways to do this, several of them on this page.

Do Don’t
Give appreciation on its own, when it is genuine Use praise as a wrapper to soften unrelated criticism
Say clearly what needs to change Let the correction get lost between two layers of praise
Reach for AID, COIN or CEDAR instead Default to the sandwich out of habit

Feedback excuses

Most leaders already know feedback matters. What stops them is rarely a lack of a model, it is one of a small set of recurring excuses that feel reasonable in the moment but quietly protect the leader more than they protect the relationship.

The excuse A more useful move
“I don’t have the time” Spend at least one hour a week in one-to-ones with your team
“I don’t know where to start” Keep a simple feedback diary of what you notice week to week
“I don’t know how to structure it” Use an established model, BOOST or AID work well to start with
“I’m unsure how they’ll take it” Prepare properly and build it as a two-way conversation, not a verdict
“It’s not clear when the best time is” As soon as possible after the event, rather than waiting for a formal moment

None of these excuses are irrational. They usually trade a real short-term cost, an awkward conversation, for a larger cost later, a pattern that continues because nobody named it.

Receiving feedback tips

Receiving feedback well is a skill in its own right, and it matters as much as giving it does. A simple set of habits helps: take it as a gift rather than an attack, remain calm, get a clear understanding of what’s actually being said, compartmentalise it away from your sense of your own worth, and review it to create real next steps.

Taking it as a gift means recognising the effort it took the other person to raise it, even when it’s unwelcome. Staying calm doesn’t mean suppressing your reaction, it means giving yourself a beat before responding. Getting a clear understanding means paraphrasing and asking clarifying questions rather than assuming you already know what they mean. Compartmentalising means treating the feedback as information about a specific activity, task or behaviour, not a verdict on who you are. Reviewing means leaving the conversation with something concrete, even if it’s only “I’ll think about this and come back to you.”

Do Don’t
Paraphrase back what you heard before you respond Jump straight to explaining or justifying
Treat it as information about behaviour, not identity Let one piece of feedback become a verdict on your worth
Leave with at least one concrete next step Let the conversation end with nothing to act on

Negative reactions

Sometimes, despite your best intentions, feedback still lands badly and the person becomes defensive, upset or angry. Most of the work in reducing that happens before the conversation starts: preparing your feedback and thinking through your examples in advance, and using simple, clear language rather than jargon or softened phrasing that leaves room for misinterpretation.

During the conversation itself, remaining calm, both mentally and emotionally, does more than any clever phrasing. Spotting emotional reactions early, in facial expression and body language, not just words, lets you adjust before things escalate. Allowing the other person to input their perspective, rather than delivering a monologue, tends to reduce defensiveness on its own. And structuring the feedback with an established model, AID, CEDAR or BIFF all work well here, keeps the conversation from drifting into territory that makes things worse.

Do Don’t
Prepare your examples and language in advance Improvise a difficult conversation on the spot
Watch for emotional reactions in expression and body language Keep talking as if you haven’t noticed
Let the other person input their perspective Turn it into a one-way monologue

Frequently asked questions about feedback models

1. What is the best feedback model for managers?

There is no single “best” feedback model. The most effective approach depends on the intent of the conversation, the relationship, and the level of emotion involved.

For everyday one-to-one conversations, models like AID and COIN work well because they keep feedback grounded in observable behaviour and move quickly towards practical next steps. If the conversation requires deeper learning, problem-solving, or rebuilding shared understanding, CEDAR is often a better choice because it creates space for diagnosis and joint ownership before committing to action. When defensiveness or strong emotion is likely, BIFF can be helpful because it makes the receiver’s emotional state part of the conversation rather than something to work around.

Over time, the goal is not to memorise more models, but to build range. A model is simply scaffolding that helps you be clear, fair, and consistent.

2. What is the simplest feedback model to use?

If you want a model that is simple enough to use in the flow of everyday work, AID is hard to beat. It gives you a quick structure without turning the moment into a formal performance review.

Start with the action, focusing only on what you observed rather than your interpretation. Then name the impact, describing what it changed for the team, the customer, the outcome, or the process. Finally, move to development or desired behaviour, which makes the conversation practical rather than judgemental. This last step is where feedback becomes learning, not critique.

The simplest model is the one you can use consistently and calmly, even when you are busy.

3. What feedback model should I use for difficult conversations?

Difficult feedback conversations usually fail for one of two reasons: they move too fast into judgement, or they skip the part where both people make sense of what actually happened. When the stakes are high, it helps to choose a model that slows the conversation down and keeps it respectful.

CEDAR is effective because it explicitly creates a diagnosis phase. You set context, use concrete examples, explore what drove the behaviour or outcome, then agree actions and a review point. That structure reduces defensiveness because the person being coached is involved in making sense of the situation.

BIFF can also be useful in difficult conversations because it includes an explicit emotional check. That does not mean turning the conversation into therapy. It means noticing whether the person is still able to hear and process what is being said, and adjusting the pace accordingly.

4. What is the difference between feedback and feedforward?

Feedback looks backward. It is information about what has already happened, intended to reinforce what worked or change what did not. Done well, it is factual, specific, and focused on learning.

Feedforward looks forward. Instead of analysing past mistakes, it invites ideas for future improvement. This can be especially helpful when the person already knows what went wrong, or when you want to keep energy high and focus on growth rather than blame.

In practice, both are useful. Feedback builds clarity and accountability. Feedforward builds momentum and experimentation. Strong leaders know when the situation calls for reflection on the past and when it calls for design of the future.

5. Why does the feedback sandwich not work?

The feedback sandwich often fails because it creates a predictable pattern that undermines trust. People learn to listen past the praise and wait for the criticism. Over time, the “positive” parts start to feel like manipulation rather than recognition.

It also muddies the message. When praise and correction are mixed too tightly, the person leaves unsure what to take seriously and what to change. If the goal is clarity, the structure works against you.

A more effective approach is to separate intent. Give appreciation when it is genuine and specific. Give corrective feedback when it is needed and clear. If both need to happen, signal the transition explicitly rather than trying to disguise one inside the other.

6. How can I receive feedback without becoming defensive?

Defensiveness is usually a sign that the brain is treating the feedback as a threat rather than information. You cannot always stop that initial reaction, but you can work with it in a structured way.

A receiving framework such as RADAR helps. You repeat what you heard to confirm understanding, ask questions to make it specific, discuss your perspective without dismissing the feedback, align on what will change, and then reflect afterwards on what you want to take forward.

The goal is not to agree with every point. The goal is to stay curious long enough to extract the useful signal and convert it into action.

7. What feedback model should teams use?

Teams usually need feedback at the pattern level, not just the individual level. The most useful team feedback tools help people talk about habits, ways of working, and shared constraints rather than turning everything into personal critique.

Tools such as Stop-Start-Continue and the Sailboat exercise work well because they make feedback visible, collective, and action-oriented. They surface what accelerates the team, what slows it down, and what to change together. They also create a shared language for improvement, which is essential if you want change to stick.

If the team is ready for deeper feedback, structured approaches such as team 360 processes can help, provided they are handled carefully and followed through with real actions.

8. How do I build a feedback culture in my organisation?

A feedback culture is built through routines and modelling, not slogans. People watch what leaders do, what gets rewarded, and what gets ignored. Culture changes when consistent practices make feedback normal, safe, and useful.

Start with a shared model so managers are not improvising wildly different approaches. Create simple rhythms, such as regular one-to-ones, project retrospectives, and lightweight check-ins that include feedback as a normal agenda item. Invest in psychological safety by rewarding honesty, curiosity, and learning, especially when mistakes are discussed without blame.

Finally, make feedback actionable. If feedback conversations do not lead to real agreements, experiments, or follow-up, people stop taking them seriously. The strongest cultures treat feedback as a form of collective learning and accountability, not as a performance ritual.

Further reading and related leadership capabilities

If you would like to deepen your practical use of workplace feedback models, these guides explore related ground in more depth.

How to help a team member receive feedback without getting defensive at work
Practical strategies for supporting others through difficult feedback conversations, strengthening psychological safety, and keeping performance discussions constructive.

How do I give feedback without making someone defensive?
A closer look at the distinction between observation and interpretation, and why the aim is reducing unnecessary defensiveness rather than eliminating discomfort altogether.

Feedback: giving
The leadership capability page behind this hub, covering why feedback matters, what good and bad feedback looks like, and the barriers and enablers that shape whether leaders give it well.

Feedback: responding
The companion capability page on receiving feedback well, covering why it matters, what good and bad responses look like, and the habits that build or erode a leader’s access to honest input.

Want some help putting this into practice?

For You: Leadership Clinic

Bring one difficult feedback conversation. I prepare beforehand, then we spend 90 focused minutes clarifying the message, anticipating what may create unnecessary threat, and working out how you want to approach it.

For You: Executive Coaching

For feedback challenges that need more than one conversation. Work with me over time to become clearer, more specific and more skilful in the difficult conversations your leadership role requires.

For Your Organisation: Leadership, Teams & Facilitation

Bring me in to train your management cohorts to deliver high-stakes, performance-improving feedback, with a safe environment for hands-on practice using these exact frameworks.

Choose the level of support that fits what you are working through.

Sources

Full references for AID, BOOST, CEDAR and RADAR are held on their own dedicated guides, linked above.