Challenging without wounding: the hard situations

Models work in calm situations. The real test comes when the feedback is heavy: a repeated mistake, a behavior going off the rails, an underperformance. This chapter covers the cases people dread — and the condition that makes everything else possible.

The baseline condition: psychological safety

Amy Edmondson's work (Harvard) on psychological safety shows that the highest-performing teams are not the ones that avoid touchy subjects, but the ones where everyone can say and hear hard things without fearing humiliation or retaliation. Demanding feedback is only possible on this foundation. So before challenging someone, make sure the relationship can carry it — otherwise, build trust first.

"Psychological safety is not about being nice. It's the belief that you won't be punished for saying what you really think." — Amy Edmondson

Preparing difficult feedback

A challenge that goes wrong is almost always an unprepared one. Four points before the conversation:

Describe the behavior, never the intent

The classic mistake when challenging someone: attributing an intent. "You deliberately left me out" is an unprovable accusation that triggers defense. Stick to the observable fact: "I wasn't copied on that email." Then question the intent instead of decreeing it: "Was that on purpose or an oversight?" You leave the other person room to explain — and that's what defuses things.

Challenging a repeated behavior

When a behavior recurs despite feedback, you step it up without attacking the person. The effective structure: fact + history + impact + request + consequence. "This is the third time this month the report is late (fact + history). As a result, the team waits and reschedules (impact). I need it ready by Thursday noon (request). Otherwise we'll have to rethink the setup together (consequence)." Firm on the behavior, respectful of the person.

flowchart TD
    A[Problematic behavior] --> B[Describe the FACT<br/>observable and dated]
    B --> C[Name the concrete IMPACT]
    C --> D[Question, don't<br/>assume the intent]
    D --> E[State a clear<br/>REQUEST]
    E --> F[Set a CONSEQUENCE<br/>if it recurs]

Positive feedback: the underrated one

We often think only corrective feedback requires technique. False. A vague compliment ("great job!") motivates little and teaches nothing. Precise positive feedback — same SBI structure — tells what to do again: "In your presentation (S), you summed up the stakes for the client in one sentence before each section (B); he said it was the first time he understood our offer (I)." This reinforces an identified behavior, instead of flattering. Precise recognition is one of the most powerful drivers of engagement.

Managing your own emotion

If anger rises, postpone. Feedback given in the heat of emotion targets the person, not the behavior. The rule: "Praise in public, criticize in private" — praise can happen in front of others, but challenging is always done in private, never in front of the team, on pain of threatening status (SCARF) and causing lasting defensiveness.

What to say / what not to say

A team member delivered sloppy work.

• Don't say: "You don't care at all about this project." (assumed intent + attack)
• Do say: "In this deliverable, three of the five sections are still in draft (fact). We can't send it to the client as is (impact). What happened, and what do you need to finalize it by tomorrow?" (fact + impact + opening + request)

Practical exercise

Identify a difficult conversation you've been putting off. Write your opening sentence, forbidding yourself two things: any adjective about the person, and any assumed intent. Keep only a dated fact and its impact. That's where to start.

Summary

Demanding feedback first requires psychological safety (Edmondson). You prepare it: precise fact, impact, request, your own intent. You describe the observable behavior without assuming intent, which you question rather than decree. For a repeated behavior: fact + history + impact + request + consequence. Precise positive feedback (SBI) reinforces what should be repeated. And you always challenge in private, never in the heat of emotion.