What do managers say when giving negative feedback?

Start with the specific observation, not the conclusion: 'I noticed the forecast landed two days late without warning' rather than 'your work has been late.' Then name the impact: 'When that happens without notice, the downstream team can't adjust.' Then ask: 'What was happening on your end that week?' If the issue is real, finish with what you need: 'What I need going forward is early warning — by Wednesday if something's at risk.' That sequence — observation, impact, ask, specific change — is the structure that makes negative feedback land without triggering defensiveness.

How do you tell an employee they're underperforming?

Name the specific gap between what was agreed and what's happening — not a character assessment of the person. 'We agreed Q3 reports land by the 5th. Three of the last four were late. That's the gap I need us to close.' Then ask: 'What's making the 5th hard to hit?' If there's no valid blocker, name what changes: 'Here's what I need: by the 5th, or I hear about a delay the week before — not after. Can you commit to that?' Underperformance conversations fail when they lead with the verdict rather than the behavioral gap.

How do you talk to an employee about attitude problems?

Name the specific behavior, not the attitude. 'Attitude' is a character judgment with no actionable edges. 'I noticed you had your camera off and your responses were one-word in the Q4 review' is a behavior. That's what you say. Then ask: 'I want to hear what's going on from your side — is there something happening that I'm not seeing?' Attitude problems are almost always behavioral patterns that haven't been named specifically. Name the behavior, ask what's underneath it, and make space for the real conversation before drawing the character conclusion.

How do you address a pattern of behavior without making it personal?

Keep the language at the level of behavior, not character, and connect it to impact rather than interpretation. 'When X happens, Y is the consequence for the team' is not personal — it's describing cause and effect. 'You clearly don't care about the team' is personal — it's a conclusion about intent and character. The test is whether the other person can do something specific with what you've said. Behavioral observations are actionable. Character judgments aren't.

How do you tell someone they have a blind spot at work?

Lead with what you've observed — not the conclusion that they have a blind spot. 'I want to share something I've noticed, and I'm curious whether you're aware of it.' Then name the specific behavior and its impact on how others are experiencing them. 'When you interrupt in the product sync, I notice other people stop contributing — I'm not sure you can see that from where you're sitting.' The framing 'I'm not sure you can see this' is honest and non-blaming. It names the gap without making it a character verdict.

How do you tell an employee their work isn't good enough?

Name the standard explicitly and the gap to it specifically. 'The expectation for this deliverable was X. What landed was Y. Here's where the gap is: [specific elements].' Then ask: 'What happened in the process that created this version?' Most 'not good enough' conversations fail because the standard was assumed rather than named. Naming the standard before the gap — not after it — is what makes the feedback fair rather than arbitrary.

For Managers

What managers avoid saying — and what to say instead

Managers avoid specific sentences, not conversations. The six most-avoided things are: naming a slipping standard, connecting a pattern to impact, naming someone's blind spot to their face, asking for change directly, naming disappointment without blame, and telling the truth about where things stand. Here's how to say each one.

June 27, 20266 min readDifficult ConversationsFeedbackAccountability Dial

Most management avoidance isn't about avoiding the whole conversation. It's about avoiding the specific sentence. The one that actually says the thing.

Managers know something needs to be addressed. They sit down for the 1:1. They circle around it. They talk about the project, the team, the strategy — anything but the thing. And then they leave, having technically had the meeting, having said nothing that required courage, and the thing is still unsaid.

This is why most 1:1s default to status updates. The specific sentences that require courage are the ones that name something, and naming something has a cost. But the cost of not naming it is higher — it's just delayed, and it accumulates.

Here are the six most-avoided sentences. And what to say instead.

1. "I've noticed this pattern, and it's been going on for a while."

What managers actually say instead: Nothing. They wait for the review. They put it in a project comment. They mention it to a peer but not to the person.

Why it's avoided: Saying "I've noticed a pattern" requires you to have been watching. It implies the manager has been holding it without saying anything. That admission is uncomfortable — it feels like it will trigger "why didn't you say something sooner?"

What to say: "I've been watching this for the last few weeks, and I should have mentioned it sooner. The pattern I'm seeing is [specific behavior]. I want to talk about it now."

Acknowledging the delay — briefly — and then naming the pattern is far more effective than pretending it's the first time you noticed. People can tell when a manager has been holding something. Naming the holding creates more trust, not less.

2. "When this happens, here's what it costs the team."

What managers actually say instead: "I've just been a little concerned about X." Or: "I think there might be something worth talking about here." Or: vague, soft language that doesn't actually land.

Why it's avoided: Naming the impact feels like it will upset the person or make the conversation feel punitive. The manager wants to "be gentle."

The thing about gentle: vague concern is not gentler than specific impact. It's just less honest. "I've been a little concerned" puts the manager's feelings at the center, gives the person no behavioral target, and provides no reason to change anything. Impact is specific and actionable. "When the forecast slips with no warning, the downstream team can't adjust and I'm left fielding calls I don't have the information to handle" — that's what happened, and that's why it matters.

What to say: Name the behavior, name the consequence, be specific. "When [behavior], [cost to team/work/person]. That's what I'm trying to address."

3. "I'm not sure you're aware of how this is landing."

What managers actually say instead: The opposite — they assume the person knows. They think awareness is obvious and say nothing, waiting for the person to self-correct.

Why it's avoided: Saying "you may not be aware" sounds like you're implying they're oblivious. It feels condescending.

The reality: Most behavioral patterns that managers notice are genuinely invisible to the person exhibiting them. The manager can see the impact from a vantage point the person doesn't have. Naming that vantage-point gap — "I can see something from here that I'm not sure you can see from where you're sitting" — is honest, not condescending. It gives the other person something they actually couldn't see.

What to say: "I want to share something, and I'm not sure you're aware of it. When [specific behavior], I've noticed [specific response from others/the work]. I'm not sure that's visible from your side."

4. "I need [specific thing] to change. Not 'improve' — specifically, [this]."

What managers actually say instead: "I'd like to see more consistency" or "I think we need better communication" or "I want us to get ahead of this kind of thing."

Why it's avoided: Being specific about a change makes the manager accountable to having said it. If the manager says "communicate earlier — by Wednesday when you know something is at risk, not Friday when it's already happened," then the manager can't pretend they didn't say it. Vague asks give the manager a backdoor.

The reality: Vague asks give the person a backdoor too. They can't know exactly what changed, and they can't be held accountable to something they didn't agree to specifically. The vague ask protects no one.

What to say: Name the specific behavioral change. "What I need is: [specific thing], by [specific time or trigger]. Not 'better communication' — specifically, a flag to me by Wednesday if a deliverable is at risk that week. Can you commit to that?"

5. "I want to be direct — I'm disappointed."

What managers actually say instead: "I just want to make sure we're aligned going forward." Or: silence, and an invisible drop in how much opportunity the person receives.

Why it's avoided: Saying "I'm disappointed" sounds personal. It sounds like the manager is making it about their feelings. It might also sound like a verdict.

The thing managers miss: Invisible disappointment is worse than named disappointment. People can tell when a manager has shifted. They see the fewer opportunities, the shorter responses, the changed dynamic — but without the language for it, they fill the gap with their own interpretation, usually worse than the truth.

What to say: "I'm going to be direct: I'm disappointed by how this landed. Not as a verdict — I still believe in your capacity here. But I want to name it rather than pretend it didn't happen. Here's what I saw, and here's what I needed."

6. "Here's where we actually stand."

What managers actually say instead: Ambiguous reassurance. "Things are going well overall." "I think we're in good shape." Optimism that protects the manager from the conversation, not the person from the situation.

Why it's avoided: "Here's where we actually stand" requires the manager to have a clear and honest assessment that might not be welcome. If the assessment is "you're close to a Boundary conversation on this pattern," saying so is uncomfortable.

The reality: Naming where things actually stand is the most useful thing a manager can do. It's not a threat — it's honest information the person needs to make a decision about their own behavior. "I want to be honest: if this pattern continues, we're going to be in a different kind of conversation. I'd much rather have this one."

What to say: "I want to be honest with you about where I think we are. [Specific assessment]. I'm telling you this because I'd rather name it while it's still recoverable than wait until it isn't."

The sentence that starts all of them

Every one of these avoided sentences becomes possible with a single setup line: "I want to say something directly."

That sentence does two things: it signals to the other person that something real is coming (which activates attention, not defensiveness) and it gives the speaker permission to actually say it.

"I want to say something directly" is not a threat. It's an act of respect. It says: I'm going to be honest with you, because I think you deserve the honest version.

The alternative — circling the thing forever, hoping it self-corrects — is not kind. It's avoidance dressed as consideration.

For the full methodology behind accountability conversations, read The Accountability Dial. For templates and scripts for specific situations, see Accountability Dial feedback templates.

If this is the standard you want on your team

Send it to them. In your own voice.

One click opens a draft in your email or copies the share text — edit it, send it from your own address. We never email anyone on your behalf.