How to Give Feedback to a Colleague Who Responds to Criticism With Excuses Instead of AccountabilityShare

Why Giving Feedback That Produces Accountability Is Harder Than It Looks

Knowing that you need to address something and actually doing it well are two entirely different things. Most people understand, in theory, that clear feedback helps teams improve. Doing it in a room with a real person who is already defensive is something else entirely.

Here is what makes it so difficult in practice:

• You cannot separate the person from the behavior in the moment. Even when you prepare careful, behavior-focused language, the person across from you experiences criticism as a comment on who they are. Their defenses rise before your second sentence lands.

• Excuses are delivered with confidence. A practiced excuse sounds reasonable. It names real circumstances, real pressures, real constraints. Challenging it feels petty, even unkind, in the moment.

• Most feedback conversations have no structure. People wing it. They have a vague sense of what they want to say, but no clear method for what to do when the conversation goes sideways. When the excuse arrives, they freeze.

• The fear of damaging the relationship is real. Pushing back on an excuse carries a social risk. You worry that you will seem harsh, that the person will disengage, or that the working relationship will cool afterward.

• Silence feels like agreement. When someone offers an excuse and you do not challenge it clearly and promptly, they hear permission. The pattern embeds itself a little deeper.

The goal is not to eliminate these difficulties. It is to build a system that works in spite of them.

The Foundation: What You Need Before You Start

Before you begin, there are three things that need to be clear.

1. Your specific observation, not your interpretation. You must know exactly what you saw or heard, stated in plain language. Not "you seem disengaged" but "in Tuesday's meeting, you interrupted three separate speakers and did not contribute when I asked for input." The more specific your observation, the less room there is for an excuse to take root. Vague feedback invites vague deflection.

2. The impact on the work or the team. You need to be clear about what the behavior actually affected: a deadline, a team dynamic, a client relationship, a decision quality. Impact is what transforms feedback from a personal opinion into a professional concern. Without it, your colleague can dismiss your feedback as a matter of preference.

3. Your own emotional state. If you are still frustrated or hurt by what happened, wait. Not indefinitely, but long enough to deliver the feedback from a place of clarity rather than reaction. Feedback delivered in frustration reads as an attack, and attacks produce excuses. Read How to Use the S.T.R.O.N.G. Method to Prepare Before a High-Stakes Feedback Conversation if you need a proven structure for that preparation.

Get these right first. The steps that follow will not work without them.

Step 1: Open With the Behavior, Not the Verdict

This step sets the entire tone of the conversation, and it is where most feedback conversations go wrong immediately.

The single most common mistake is opening with a conclusion: "You have been unreliable lately" or "Your attitude in meetings is a problem." The person hears judgment, not information. Their defenses go up before you have said anything useful.

Instead, open with a precise, observed behavior. State what happened, when it happened, and who was affected. Keep it factual and keep it brief. You are reporting, not prosecuting.

• Write down the specific incident before the meeting. One concrete example is stronger than three vague ones.
• Use past tense and name the date or context: "On Thursday, during the client briefing..."
• Describe what you observed, not what you concluded about it.
• Keep your opening to two or three sentences maximum. Brevity signals confidence.
• Resist the urge to soften the opening with unrelated praise. It dilutes the message.

Example script: "I want to talk about what happened on Thursday's call. You had committed to presenting the updated numbers, and when the client asked for them, you said they were not ready. That put the team in a difficult position with the client."

That is it. No verdict. No character assessment. Just what happened, clearly stated. Once that is in the room, you pause and let them respond. The opening step positions you for everything that follows.

Step 2: Pause and Listen Before You Push Back

After your opening, silence is your most powerful tool. Most people rush to fill it.

When you deliver feedback and then immediately pile on with more explanation, you are giving your colleague a way out. They can pick a thread, respond to one part, and avoid the core issue entirely. The pause forces them to respond to what you actually said.

This step also gives you information. How someone responds in the first ten seconds tells you a great deal about what kind of conversation you are in. A genuine response sounds different from a practiced excuse, and you need to hear the difference before you decide what to do next.

• After your opening statement, stop talking and make eye contact.
• Allow at least five full seconds of silence. It will feel uncomfortable. Stay with it.
• Listen to the full response before you say anything. Do not interrupt, even if the excuse begins immediately.
• Take a brief mental note of whether the response addresses the behavior or deflects from it.
• If they do take some ownership, acknowledge it before continuing.

This step is not passive. You are actively gathering information about what kind of resistance you are dealing with. That knowledge shapes how you respond in Step 3. For a deeper method to stay grounded when defensiveness arrives, How to Use the C.O.R.E. Framework to Stay Calm When Feedback Triggers a Defensive Reaction gives you a reliable tool.

Step 3: Name the Pattern Without Naming the Person

Here is the truth of it: when someone responds to your specific, behavior-focused feedback with a broad excuse, they have changed the subject. Your job is to notice that shift and name it, without making it personal.

This step is where most people either back down or escalate. Both are mistakes. You need a third path: calm, direct acknowledgment of what just happened in the conversation.

• Say something like: "I hear that the timeline was difficult. I want to come back to the specific moment I described."
• Avoid the phrase "but" after you acknowledge their point. It signals that you dismissed what they said. Use "and" instead.
• Keep your tone level. If your voice tightens or rises, they will respond to your emotion rather than your words.
• Return to your original observation, not to a new one. Stay on the same ground.
• If they offer a second excuse, name the pattern explicitly: "I notice we keep moving away from what happened on Thursday. I want to understand your thinking about that specific moment."

Example script: "I understand the timeline pressure was real. And I want to stay with what happened on Thursday, because that is the piece I am trying to understand. When the client asked for the numbers, what was going through your mind?"

That final question is critical. It shifts the conversation from their defense to their decision-making. It is much harder to excuse a specific choice than a general circumstance. After this step, you are in a genuine dialogue rather than a one-sided confrontation. How to Give Feedback That Strengthens Team Synergy Instead of Breaking It explores how this kind of precision protects relationships while it builds accountability.

Step 4: Ask the Question That Requires Ownership

This step is where the real work happens. You have named the behavior, listened to the response, and returned to the original observation. Now you ask the one question that makes an excuse structurally difficult to sustain.

The question must be specific, past-tense, and focused on their choice, not on external circumstances. "What could you have done differently?" is too abstract. "Given that you knew the numbers were not ready on Wednesday, what options did you have at that point?" is the kind of question that requires genuine reflection.

• Prepare your accountability question before the conversation. Write it down.
• Frame it around their decision at a specific moment, not around their general behavior.
• Ask it once, then be silent. Do not rephrase it. Do not soften it. Let it land.
• If they answer with another excuse, acknowledge it briefly and then restate the question: "I hear that. And what were your options at that point?"
• If they begin to take ownership, even partially, acknowledge it immediately and specifically.

This question works because it separates the circumstance from the choice. Most excuses conflate the two: "it was a hard week" becomes the reason that every decision within it was unavoidable. Your question cuts that connection cleanly. After this step, the conversation has moved from defense to reflection, and that is the ground where accountability grows.

Step 5: Agree on What Changes Next

Accountability without a next step is just a difficult conversation. This step turns the exchange into something useful.

By this point, your colleague has either taken some ownership or is close to it. Now you need to name, together, what will be different going forward. This must be specific. "I will do better" is not a commitment. "I will flag any gaps in my deliverables by Wednesday, before the client meeting" is one.

• Ask directly: "What will you do differently when this situation comes up again?"
• Listen to their answer and test it for specificity. If it is vague, ask them to make it concrete.
• Confirm the agreement by restating it yourself: "So what I am hearing is..."
• Set a follow-up point. Name the date or context when you will check in on progress.
• Close the conversation with something honest and forward-facing, not with hollow reassurance.

Example script: "So, going forward, if you realize a deliverable is at risk, you will flag it to me or the team by the day before the meeting, rather than on the day itself. Is that right?" Pause. Let them confirm. "Good. I will check in with you on that after next week's call."

The follow-up is not optional. Without it, the agreement evaporates within forty-eight hours. This is the step that separates a feedback conversation from a feedback outcome. For a structured method to deliver this kind of feedback using a proven framework, read How to Use the S.B.I. Method to Give Feedback That Actually Changes Behavior.

Step 6: Follow Up Without Hovering

The conversation is over. The agreement is made. Now the temptation is to either forget about it or watch your colleague's every move. Neither serves you.

Follow-up is about one thing: honoring the agreement that was made. When you said you would check in, you meant it. When they said they would do something differently, they said it out loud. The follow-up makes both of those things real.

• Choose a follow-up format that matches the severity of the issue. A brief conversation is usually enough.
• Keep your follow-up neutral in tone. You are not checking up on a suspect; you are closing the loop on an agreement.
• If the new behavior appeared, name it. "I noticed you flagged the numbers on Tuesday. That made a difference."
• If the behavior did not change, return to the process with the new incident as your specific example.
• Document the original conversation and the agreed change, especially if this is part of a larger performance pattern.

After this step, you have either confirmed that the feedback worked or gathered the evidence you need to escalate if it did not. Either outcome is progress. The S.B.I. method applied to team settings can help you structure follow-up conversations that keep the team's dynamic intact even after a difficult exchange.

Adapting This Process for Repeat Offenders in High-Stakes Environments

When the excuse-making is not a one-off response but a persistent pattern, the standard process needs adjustment.

Repeat defensiveness requires a different opening. Instead of starting with a single recent incident, you name the pattern directly and then anchor it with a specific example. "I want to talk about something I have noticed over the past few weeks. Last Thursday was one example." This removes the possibility of treating each incident as isolated and unrelated.

Formality of setting matters more. In a high-stakes environment, a casual corridor conversation is not enough. Book a private room, block enough time that neither of you feels rushed, and let the person know in advance that you want to have a serious conversation. The setting signals that this is not a throwaway comment.

Written records become essential. After each conversation, send a brief follow-up email confirming what was discussed and what was agreed. Keep the tone matter-of-fact, not punitive. "As we discussed today, you will notify the team by Wednesday if any deliverables are at risk." This is not a threat; it is a record. It also removes the possibility of the agreement being misremembered later.

Involve a third party when the pattern continues. If the same conversation has happened more than twice and nothing has changed, you need a witness. This protects both of you and adds weight to the accountability that a one-on-one conversation cannot carry alone. Read How to Respond When a Team Member Reacts Defensively to Synergy-Focused Feedback for guidance on what to do when the defensiveness itself becomes the issue.

The core process does not change in high-stakes environments. Only the formality, documentation, and escalation path change with it.

Common Mistakes to Avoid

Let me tell you about the mistakes I see most often. I have made most of them myself.

• The mistake: Starting with a compliment to soften the blow.

  Why it happens: People fear conflict and try to cushion the opening so it lands more gently.

  What to do instead: Open directly with the specific behavior. Compliments before criticism teach people to wait for the "but," and they stop hearing anything before it.

• The mistake: Using absolute words like "always" and "never."

  Why it happens: Frustration makes us reach for the biggest language available.

  What to do instead: Stay with the specific incident. "Always" gives your colleague something to argue against. One clear example gives them nothing to hide behind.

• The mistake: Accepting the first sign of acknowledgment as full accountability.

  Why it happens: The emotional relief of a partial concession makes people want to close the conversation early.

  What to do instead: Acknowledge the partial ownership warmly, and then ask the next question. Real accountability includes a specific commitment to change, not just agreement that something went wrong.

• The mistake: Delivering feedback in front of others.

  Why it happens: Sometimes the moment arises in a meeting and feels too important to let pass.

  What to do instead: Take note of the issue and address it privately. Public feedback almost always produces public defensiveness, and the audience makes retreat impossible for both sides.

• The mistake: Dropping the follow-up because the conversation felt resolved.

  Why it happens: The conversation was hard, it ended reasonably well, and revisiting it feels like opening a wound.

  What to do instead: Follow up as agreed. A commitment without a check-in is just a conversation. The follow-up is what makes it a change.

These are not character flaws. They are gaps in the system. Fix the system.

Your Practical Checklist

Use this checklist before you begin and after each cycle.

• I have identified the specific behavior I want to address, with a date and context.
• I can state clearly what impact the behavior had on the work or the team.
• I have checked my own emotional state and am ready to deliver this from a place of clarity.
• I have prepared my opening two sentences and written them down.
• I have prepared the accountability question I will ask after the initial response.
• I have booked a private time and place for this conversation.
• I know what a specific, concrete next-step commitment will look like.
• I have set a follow-up date or context in my calendar.
• I am prepared to stay in the conversation calmly if an excuse arrives.
• I know what I will do if the pattern continues after this conversation.

If you cannot check most of these, that is your starting point.

Summary and Next Steps

You now have a method for giving feedback that does not collapse when the excuses begin. You have a structure to carry into the room and a process to hold the conversation steady when it gets difficult.

• Prepare your specific observation, the impact, and your accountability question before you sit down.
• Open with what happened, not with a verdict about the person.
• Pause after your opening and listen to the full response before you do anything else.
• Name the pattern of deflection calmly and return to the original behavior, not a new one.
• Ask the question that requires a specific choice, not a general circumstance.
• Close with a concrete commitment and a named follow-up.
• Follow through on the check-in. That is what separates a conversation from a change.

If you want to understand what happens in the body and mind when someone receives critical feedback, start with How the Amygdala Hijack Sabotages Feedback Conversations and What to Do About It. If you are dealing with a team environment where defensiveness is spreading beyond one person, How to Give Feedback That Strengthens Team Synergy Instead of Breaking It will show you how to protect the wider dynamic while you address individual behavior.

The ability to give feedback accountability is one of the rarest and most respected skills in any workplace. You can practice it, prepare for it, and earn it. Start with one conversation, and build from there.

Frequently Asked Questions (FAQ)

What does it mean to give feedback with accountability?

To give feedback with accountability means delivering your observations clearly, focusing on specific behavior, and holding the conversation open until the other person takes ownership of their response. It requires preparation, courage, and a willingness to stay in the discomfort when excuses emerge.

How do you give feedback to someone who always makes excuses?

Start by naming the pattern directly without attacking the person. Use specific, observed examples rather than general complaints. Ask questions that make excuses harder to sustain, and pause long enough after each one to let the silence do its work. Structure matters more than tone here.

How can I give feedback accountability without sounding confrontational?

Keep your language descriptive, not evaluative. Say what you saw and what it affected, not what it means about the person. Speak in a calm, measured tone and avoid absolute words like always or never. Preparation prevents most of the moments that feel confrontational.

Why do colleagues respond to feedback with excuses instead of owning it?

Excuses are almost always a self-protection response. When people feel judged rather than informed, the brain triggers a defensive reaction before rational thinking can engage. The feedback conversation was likely framed in a way that felt like an attack on character rather than a report on behavior.

What is the best method for giving feedback that leads to real change?

The most reliable method is to separate observation from interpretation, keep feedback specific and timely, and build in a question that invites the other person to respond rather than react. Following up after the conversation is just as important as the conversation itself.

How do I stay calm when someone responds to my feedback with excuses?

Prepare yourself before the conversation so you are not caught off guard by defensiveness. Name what you are observing in real time without escalating: say something like, "I notice we are moving away from the specific issue." Then return to your prepared points and stay grounded in what you observed.