A manager sits down for the conversation they have been putting off all week. They open with praise to soften the ground. They slip the real issue into the middle, wrapped in qualifiers: "maybe," "a little," "when you get a chance." They close with more praise. The report leaves the room feeling fine. Nothing changes. Two weeks later the same problem is back, the manager is quietly furious, and the feedback, technically delivered, never actually arrived.
This is the most common way feedback fails, and it does not feel like failure in the moment. It feels like kindness. But feedback the other person cannot act on is not kind. It is just comfortable for the person giving it. The fix is not more courage or a better mood. It is a structure: a way to say the hard thing so it lands clearly and the relationship survives. That structure has a name, and it is older than most of the management advice built on top of it.
Why most feedback fails
Feedback fails in two directions, and they are mirror images of each other. The first is dilution: the message is softened so far that the recipient never hears the actual point. Hedging language, the feedback sandwich, vague words where specific ones were available, a disclaimer in front of every sentence. The person leaves the room genuinely unsure anything was wrong. The second is damage: the message is delivered so bluntly it attacks the person rather than the work. "You're unreliable" instead of "the report was two days late." The recipient stops listening to protect themselves, and while the message may have landed, the relationship took the hit, so the next conversation starts from a deficit.
Most well-meaning managers fail by dilution, not damage. The instinct to protect someone's feelings is decent. But it produces feedback so hedged it carries no information, and the behavior it was meant to change continues. Worse, when the manager finally snaps, the surprise feels like a betrayal to someone who was never clearly told. Gallup has measured the result at scale: only about a quarter of employees strongly agree that the feedback they receive helps them do better work.
BID: behavior, impact, desired outcome
BID is a three-part structure for delivering a hard message: name the Behavior, state its Impact, and ask for the Desired outcome. It descends directly from the Center for Creative Leadership's SBI model (Situation–Behavior–Impact), the most-taught feedback frame in corporate leadership development. Where SBI stops at impact and leaves space for the person to respond, BID adds the forward-looking step, the explicit ask, that turns an observation into a request for change. Reach for BID when you are coaching down to a report or across to a peer, where a specific change is the point of the conversation.
Behavior. A specific, observable action, something a camera could have recorded. "The handoff doc went out three days after the deadline," not "you're disorganized." This is the step managers skip most, because naming the exact behavior requires having actually noticed it. Character labels ("careless," "unreliable") feel like feedback but are unfalsifiable, and the recipient can only argue or deflate. A behavior can be discussed; a character verdict can only be defended.
Impact. The concrete consequence: what the behavior cost you, the team, the client, or the outcome. "The client emailed me to double-check the numbers, and we spent an hour rebuilding trust we'd already earned." Impact is what makes the behavior matter. Without it, the recipient hears nitpicking; with it, they understand the stakes and can own the fix rather than dispute the premise.
Desired outcome. The specific change you want, stated plainly. "Going forward I need the figures reconciled before anything goes to the client." Not "be more careful," which is a wish, not a request. The desired outcome is the difference between feedback that vents and feedback that redirects.
"Clear is kind. Unclear is unkind. Feeding people half-truths to make them feel better — which is almost always about making ourselves feel more comfortable — is unkind."
Brené Brown · Dare to Lead (2018)
The same feedback, twice
Here is the dilution version, the one most managers default to: "Hey, you're doing a great job overall, really. I just wanted to flag, and it's honestly not a big deal, that maybe sometimes the client updates could be a little tighter? But seriously, great work." There is no behavior in it, no impact, and no ask. The recipient hears "great job" twice and a fog in the middle. Nothing will change, because nothing was actually requested.
Now the BID version: "In the last two client updates, the figures didn't reconcile with the deck" (behavior), "so the client emailed me afterward to re-check the numbers, which cost us an hour and a little credibility" (impact), "going forward I need the figures reconciled before the update goes out" (desired outcome). Same conversation, same goodwill toward the person, a fraction of the words. The difference is that the second one arrived.
Read those numbers together and the gap is almost comic: people want the corrective feedback their managers are most afraid to give, and when managers do give it, it usually fails to help. The shortfall is not appetite, and it is not even courage. It is craft: the difference between a manager who has a reliable structure for the hard conversation and one who improvises under stress and reaches for the sandwich. Which raises the obvious question. If dilution is the failure mode, why is it so magnetic?
Nice and kind are not the same thing
In my workshops this is the distinction I keep coming back to, because it sits underneath everything else. We should always be nice to one another. We are all just humans showing up to do our best, and basic decency is not optional. But nice is not the same as kind. Nice protects the moment. Kind holds up a mirror so a person can see the one thing they cannot see on their own. Feedback, done well, is that mirror, and the manager who softens it into vague reassurance has chosen to be nice at the cost of being kind.
This is where Brené Brown's "clear is kind" earns its weight, and where Kim Scott, in Radical Candor, names the failure mode "Ruinous Empathy": caring so much about someone's feelings in the moment that you withhold the very thing they need to grow. It feels generous. It is, in the end, the least generous option on the table, because it trades the person's long-term progress for your short-term comfort. Holding up the mirror is the kind act, even when it is not the nice one.
There is a second mirror most managers miss. When you name the behavior and the impact and then stop talking, how the person responds tells you something you could not have known walking in: where they push back, where they go quiet, what they were already worried about. That reaction is data. It is how a coach learns what is actually getting in the coachee's way, and how to help them move forward and correct. Feedback is not a one-way verdict you hand down. Done well, it is the moment the conversation becomes diagnostic for both of you.
The space where both mirrors work is what we call the Middle Path: Parlare's own principle, with no guru attached. On one side is dilution, the message softened until it disappears. On the other is damage, the message sharpened until it wounds. A coach on the Middle Path names the specific behavior, states the impact plainly, and delivers it in a way the person can actually hear, so the clarity and the relationship both survive the same conversation.
Dilution. Hedging, the feedback sandwich, vague language, a disclaimer before every point. The message is softened so far it never lands, and the recipient leaves without understanding the real issue.
Damage. Attacking character instead of behavior, with no acknowledgment of the person or their effort. The message may land, but trust breaks and the recipient shuts down.
The Middle Path is the space between. Parlare scores each practice conversation on whether it held that line, alongside its BID structure and its clarity (Brené Brown's "Clear is Kind"). A message can be perfectly clear and still slide into the damage ditch, so the two scores are not the same, which is exactly the point.
A template you can use this week
The whole structure collapses into one sentence you can say out loud, then a pause: "When you [specific behavior], the impact was [concrete consequence]. Going forward, I'd like [desired outcome]." Then stop talking. The silence after the ask is where the other person takes ownership; fill it and you take the ownership back. Three examples, in the three situations managers dread most.
The missed deadline. "When the handoff doc came in three days after the deadline, the downstream team lost a full sprint waiting on it. Going forward I need the doc by the date we commit to, and if it is going to slip, a heads-up the day before." Note what is absent: no "you're disorganized," no sigh, no sandwich. A behavior, a cost, a clear ask.
The peer who talks over people. Feedback across, not down: "In the last two planning meetings, you cut in before Dana finished a couple of times, and she stopped offering ideas after. I'd like us to make sure everyone gets to land their point. Can we both watch for that next time?" Same spine, softer register, because a peer has not asked you to coach them. The behavior and the impact still arrive.
The sloppy client-facing work. "The last proposal went out with the old pricing table, and the client caught it before we did, which dented their confidence in the numbers. Going forward I'd like a second set of eyes on anything client-facing before it ships." Specific behavior, named impact, concrete change. The recipient knows exactly what to do differently on Monday.
Knowing BID is easy. Holding it is hard.
None of this is complicated to understand. You could memorize the three steps in a minute and the template in two. That is exactly why feedback training so rarely changes behavior: the failure is not a knowledge gap. It is what happens in the half-second after you name the behavior and the other person's face falls, when the dread you walked in with spikes and every instinct says soften it, take it back, reach for the sandwich. The structure you rehearsed evaporates under the social pressure of the real moment. (Giving clear feedback is one side of the manager-as-coach job; resisting the urge to jump in with advice is the other, and both crack under the same pressure to fill an uncomfortable silence.)
That is a practice problem, not a reading problem. You do not learn to hold the Middle Path by understanding it. You learn it by saying the hard sentence, feeling the flinch, and staying in it, enough times that the flinch stops running the conversation. The reps have to happen somewhere. Better the first dozen happen in a simulation than on the report who deserved a clear, kind version on the first try.
Feedback is a gift only if it arrives. Behavior, impact, desired outcome, said plainly and held steady when it counts, is how you make sure it does.