Feedback and difficult conversations

Feedback is the mechanism by which behaviour changes, and the difficult conversation is feedback at the moment it costs something to give. Most feedback fails not because it is wrong but because of how and when it is delivered: too vague to act on, too late to matter, or so cushioned that the message disappears. The competency covers both directions. A manager who gives feedback well but never asks for it has taught the team that information flows downward only, and has cut off the channel that would tell them when their own judgment is failing. It matters because it is the cheapest corrective a manager has and the one most often deferred: the conversation avoided in week two becomes the performance problem in quarter three, the resignation in quarter four, and the pattern the rest of the team quietly learns is tolerated. The examinations test it because avoidance is the most recognisable mistake in management, and because at every scope the wrong option is usually the comfortable one.

1. Anchor feedback in a situation, a behaviour and an impact. What happened, what the person observably did, and what it caused. Not what they are, and not why you think they did it. Diagnosing character or intent is what produces defensiveness, and it is also usually wrong.
2. Early and small beats late and large. Frequent small corrections make feedback ordinary rather than a verdict. Feedback saved for the review cycle arrives too late to change the quarter it describes and too heavy to be heard.
3. Clarity is the kindness. Softening a hard message until it is unrecognisable is not compassion; it is transferring your discomfort to the person, who will discover the real message later and at higher cost. Say the thing, plainly and privately, with a path forward.
4. Praise follows the same rules. "Great job" is forgettable. Naming the specific behaviour and its effect makes it repeatable, and makes the manager's corrective feedback credible by contrast.
5. Ask for it, and be seen to act on it. Upward feedback arrives only where the reaction to the last piece was visibly good. The first time a manager punishes a messenger, the channel closes for everyone.
6. The truth degrades as it travels upward. Every layer between a leader and reality filters, softens and summarises. The more senior you are, the more deliberately you must build channels that carry unfiltered signal, and the more your reaction to bad news decides whether you ever hear it again.

Feedback has more empirical work behind it than most management topics, but the widely used practitioner structures rest on practice rather than trials, and the unit grades them so.

Situation, behaviour, impact practice

The structure set out in Sloan R. Weitzel, Feedback That Works: How to Build and Deliver Your Message (2000): name the specific situation, describe the observable behaviour, state the impact it had. It works because it removes the two triggers of defensiveness — generalisation ("you always…") and diagnosed intent ("you don't care about…") — and because it gives the person something they can actually change. It is a structure, not a substitute for courage: a difficult message shaped as situation, behaviour and impact but never delivered is still avoidance. For a pattern rather than a single moment, name the pattern and support it with several specific instances.

Radical candour practice

The two-axis model from Kim Scott, Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity (2017): care personally and challenge directly, and the failure modes when one axis is missing. Challenge without care reads as aggression; care without challenge produces what the book calls ruinous empathy, the well-liked manager whose people never learn where they stand. Its value for this unit is the diagnosis of the second failure, which is the common one among managers who think of themselves as kind. The model's limit is that it describes a stance, not a technique; it says why to have the conversation, and the structure above says how.

The three triggers practice

From Douglas Stone and Sheila Heen, Thanks for the Feedback: The Science and Art of Receiving Feedback Well (2014), a model of why feedback is hard to receive rather than to give: truth triggers (the feedback seems wrong), relationship triggers (the problem is who it is coming from), and identity triggers (the feedback threatens the receiver's sense of who they are). It is useful in both directions. A manager giving feedback can anticipate which trigger a message will set off and shape it accordingly; a manager receiving feedback can notice their own trigger firing and separate the reaction from the content. The book is a practitioner synthesis and is graded as such.

Feedback as a system practice

Not a named model but a recurring executive practice: the mechanisms that replace the unfiltered signal a leader no longer receives in person. Skip-level conversations used for signal rather than decisions, engagement data that somebody reads and acts on, calibrated reviews of leaders, and norms that make dissent at the leadership table safe. None has a single provenance; all are widely adopted and all fail the same way, by existing on paper while the leader's reaction to bad news teaches everyone to stop using them.

The weekly small correction

Corrective feedback is given in the week it is earned, in private, in under five minutes, shaped as situation, behaviour and impact, and followed by a question rather than a lecture. The habit matters more than any single instance: a team that receives small feedback often does not experience feedback as a verdict, and the difficult conversation, when it comes, is a continuation rather than an ambush.

The difficult conversation, prepared

Before a hard conversation the manager writes down three things: the specific instances, the impact on the team or the work, and what they are asking for. If the instances cannot be written, the conversation is not ready and the feedback is an impression, not an observation. The conversation itself opens with the behaviour, states the impact, asks for the person's account, and closes with a named expectation and a date to look again. It does not open with reassurance, which delays the message, and it does not close without the expectation, which leaves the message deniable.

Triangulating second-hand signal

When feedback about someone arrives through others, especially about a manager from their reports, the practice is to verify before acting: skip-level conversations, direct observation, peer input, and team-health indicators such as attrition and engagement. Raw hearsay taken to the person burns the sources and invites denial; dismissing it because it has not reached a formal channel abandons the people who provided it. The feedback that is eventually given is the manager's own, evidence-based, and does not identify who spoke.

Asking for it

At a fixed interval the manager asks each report one concrete question about their own management — what should I do more of, less of, what is one thing I do that gets in your way — and reports back what they changed. The report-back is the whole mechanism. Asking without visibly acting teaches people that the question is ceremonial.

Protecting the messenger

When bad news arrives, the visible reaction is the practice: thank the person, ask what they need, and act. This is the same behaviour whether the messenger is an engineer or a vice-president, and it is the single most consequential thing a senior leader does for the quality of their information.

At team scope the object is an engineer's behaviour and the manager gives feedback directly and often. At organisational scope the object becomes a manager's leadership, which cannot be observed by reading their status reports; the manager of managers must gather evidence at one remove and give feedback about how someone leads, not only what their team ships. At executive scope unprompted truth has largely stopped arriving, and the work is to institutionalise what lower scopes do personally, and to deliver hard messages to powerful people without either flinching or humiliating them. The pattern is in How Judgment Scales; leading the managers who receive the feedback is PL-6 Leading through leaders.

• Gives frequent, small, specific corrections so that feedback stops feeling like a verdict. team
• Delivers a hard message plainly and respectfully, in private, with a path forward.
• Names the behaviour and its impact, never the person's character or presumed motive.
• Solicits upward feedback and visibly closes the loop on it.
• Praises specifically, so the praise is repeatable and the corrections are credible.
• Failure mode — saving feedback for the performance review. team
• Failure mode — softening a hard message until it is unrecognisable, then being surprised the behaviour continued.
• Failure mode — giving feedback while visibly frustrated, so the emotion drowns the content. team
• Failure mode — "you're careless": targeting the person instead of the behaviour.
• Gives managers feedback about how they lead, shaped as situation, behaviour and impact, not only about what their team delivered. org
• Triangulates second-hand signal before acting on it and protects the people who provided it. org
• Names the actual gaps of a well-liked manager whose delivery has slipped; likeability is not the bar. org
• Failure mode — letting a manager's own account stand in for the reality of their team. org
• Failure mode — relaying skip-level input so identifiably that people stop talking. org
• Failure mode — treating second-hand signal as either a verdict or noise. org
• Builds mechanisms that surface bad news early and rewards the people who bring it. exec
• Delivers hard feedback to senior, powerful people with the same directness owed to a junior engineer. exec
• Failure mode — softening messages in proportion to the recipient's seniority. exec
• Failure mode — punishing messengers and then wondering why surprises keep arriving. exec
• Failure mode — mistaking the absence of complaints for organisational health. exec

Directness versus relationship. The fear is that a plain message will damage the working relationship. Usually the reverse is true: a relationship in which hard things cannot be said is the fragile one, and people trust the manager whose praise means something because their criticism does. The judgment is in the delivery, not in whether to deliver.

Timeliness versus preparation. Feedback given in the moment is most useful and most likely to be badly shaped; feedback prepared carefully arrives late. The resolution is scale: small corrections in the moment, difficult conversations prepared, and a rule that a difficult conversation never waits past the week the instances were gathered.

Evidence versus urgency. Second-hand signal about a manager demands action and cannot be acted on as it stands. Verifying takes time during which the harm continues; acting without verifying destroys sources and may be wrong. The discipline is to verify fast and deliberately, not to choose between the two.

Candour versus safety. A team that hears hard truths often can become one where people brace for them. The counterweight is the care axis: hard messages land in a relationship where the manager has visibly invested in the person, praised specifically, and asked for feedback in return.

Filtering versus fidelity. As information travels upward, some summarising is necessary and all of it costs fidelity. A leader who demands raw detail drowns; one who accepts summaries is managed by them. The judgment is which signals must arrive unfiltered, and building the channel for those.

A manager of managers hears, in three separate skip-level conversations over two weeks, that one of their managers takes credit for the team's work in leadership meetings and is dismissive of people in private. The manager in question runs a high-output team, is well regarded by peers, and their own account of the team in weekly one-on-ones is uniformly positive. Nothing has reached a formal channel. Two of the three engineers who spoke asked not to be named.

The two reflexes are both wrong. Taking the accounts to the manager directly, as received, exposes the engineers who trusted the skip-level and invites a denial that cannot be answered without naming them. Dismissing the accounts because they are informal, or because the numbers are good, abandons the people who provided them and tells them the channel is decorative.

The judgment is to verify before acting, and to act as soon as verification allows. The manager of managers extends the evidence without exposing the sources: they attend the next two leadership meetings the manager presents in and listen to how the work is attributed; they look at the team's attrition and internal-transfer requests over the past year; they ask the manager's peers an open question about working with the team; and they run their remaining skip-levels with that team a week earlier than scheduled. Within a fortnight the picture is confirmed by things they observed themselves: the manager presented a design as their own that the skip-levels attributed to two engineers, and two transfer requests from the team are pending.

The feedback given is then the manager of managers' own. In a private conversation they name two specific instances they witnessed, state the impact — the team's work is invisible to leadership and its people are trying to leave — and ask for the manager's account. They do not cite the skip-levels. They set an explicit expectation about attribution and about how the manager speaks to their people, and a date to revisit it with fresh evidence. They also tell the manager that this is feedback about leadership, not about delivery, and that delivery does not offset it.

Two things are deliberately not done. The engineers who spoke are not told what was done with their words beyond "I heard you, and I am acting on it"; the loop is closed without the detail that would expose them. And the manager's output is not used as a reason to wait. What was avoided is the version of this story in which the manager of managers waits for a formal complaint that never comes, because the people who would make it have already left.

• PL-4 Performance management — where the conversation goes when feedback has not changed the behaviour: expectations, support and honest consequences.
• PL-6 Leading through leaders — the managers who receive feedback about their leadership, and how their judgment is developed.
• CC-1 Psychological safety and productive conflict — the safety that determines whether feedback, especially upward, is given at all.
• CC-2 Coaching versus directing — coaching as the form feedback takes when the goal is judgment rather than a specific behaviour.
• CC-5 Values, integrity, and ethical judgment under pressure — the costly right call when the person who needs the hard message is senior, valuable or feared.

1. Rewrite "you need to communicate better" as a situation, a behaviour and an impact.
   Answer

   "In Tuesday's design review, when the platform team raised the migration risk, you moved on without responding; they left believing the risk was accepted, and it was not." A specific moment, an observable act, a named consequence, and nothing about the person's character.
2. Why does softening a hard message until it is unrecognisable count as a failure of kindness rather than an excess of it?
   Answer

   Because the person will discover the real message later, from consequences, without having been given the chance to change. The manager has spared themselves the discomfort and transferred the cost.
3. Three engineers tell you in skip-levels something damning about their manager. What do you do first, and why not confront the manager immediately? org
   Answer

   Verify through your own observation, peer input and team-health data, without exposing the sources. Confronting the manager with hearsay burns the people who trusted you and invites a denial you cannot answer; the feedback you eventually give must be your own and evidence-based.
4. What is the single most consequential thing a senior leader does for the quality of the information that reaches them? exec
   Answer

   Their visible reaction to bad news. Thanking and acting keeps the channel open for everyone watching; punishing the messenger once closes it for a long time.
5. Name the three triggers that make feedback hard to receive, and say how knowing them helps the giver.
   Answer

   Truth, relationship and identity triggers. The giver can anticipate which one a message will set off and shape it accordingly: more evidence for a truth trigger, a different messenger or an explicit relationship repair for a relationship trigger, and a framing that separates the behaviour from the person for an identity trigger.
6. A well-liked manager's delivery has slipped for two quarters and their team is happy. What is the feedback, and what is not the bar? org
   Answer

   The feedback names the specific delivery gaps with evidence and sets a clear expectation and a review date. Likeability is not the bar; a happy team that does not ship is a leadership gap, and avoiding the conversation because the manager is liked is the failure the unit describes.
7. What replaces the unfiltered signal an executive no longer receives in person, and what makes each replacement fail? exec
   Answer

   Skip-level programmes, engagement data that somebody reads, calibrated leadership reviews and norms for dissent at the leadership table. Each fails the same way: it exists on paper while the leader's reaction to the bad news it carries teaches people to stop using it.

• Sloan R. Weitzel, Feedback That Works: How to Build and Deliver Your Message (2000) — the situation, behaviour, impact structure.
• Kim Scott, Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity (2017) — care personally, challenge directly; ruinous empathy.
• Douglas Stone and Sheila Heen, Thanks for the Feedback: The Science and Art of Receiving Feedback Well (2014) — the three triggers; receiving feedback well.