Why First-Time Managers Struggle to Give Feedback and How to Fix It

Most first-time managers don't avoid feedback because they are nice.

They avoid it because they are afraid of losing the relationship.

You were peers last month. Now you have to tell someone their work was late, or sloppy, or dismissive in a meeting. So you wait. You soften it. You hope they figure it out on their own.

They won't. And the delay makes it worse.

What usually happens

It happens by week two. Someone misses a deadline. You say nothing in the moment. You tell yourself you'll bring it up in their 1:1.

In the 1:1, you spend 20 minutes on project updates. With three minutes left, you say, “Oh, one small thing, try to be a bit more on top of timelines, okay?”

That is not feedback. That is a hint.

Or you do the sandwich: compliment, vague criticism, compliment. The person leaves remembering only the bread. The meat is gone.

The longer you wait, the bigger the conversation feels. By week three, a small miss has become a pattern, and now giving feedback feels like a confrontation.

Why this becomes a problem

Performance drifts. If no one corrects early, small misses become standard. Then you have to correct a habit, not a moment. That is ten times harder.

Resentment builds. The rest of the team sees the miss. If you say nothing, they assume you don't see it, or you don't care. Morale drops faster from ignored problems than from direct feedback.

You lose authority. A manager who won't address issues is not kind. They are avoidant. The team can feel the difference.

You explode later. Avoid, avoid, avoid, then snap in a meeting. That is what happens when feedback has no regular outlet.

The mistake managers make

The mistake is making feedback a big event.

New managers think feedback needs a perfect moment, the right tone, a private room, and 30 minutes. So it never happens.

Feedback is not an event. It is maintenance. Short. Early. Normal.

The other mistake is overexplaining the feedback, again. Five minutes of context to deliver one sentence. That dilutes it to nothing.

What to do instead

Use: Observation. Impact. Next step. Three lines. Done in 60 seconds.

1. Observation. What happened, specifically. No adjectives. No personality. Just facts. “You missed the client report deadline yesterday. It went out at 6pm instead of noon.”

2. Impact. Why it mattered. One sentence. “That delayed the client review and I had to explain the gap.”

3. Next step. What changes now. Clear and actionable. “Next time, send me a flag by 10am if you’re going to be late. Deadline stays noon.”

That’s it. No lecture. No “I know you’re trying hard”. No apology for giving feedback.

Deliver it within 24 hours. In private. Calm voice. Then move on.

If they get defensive, don’t debate. Repeat the next step once. “Understood. Still need the flag by 10am going forward.” Stop.

Example

Instead of: “Hey, you’re doing great overall, really great, I just think maybe, if possible, could we try to be a bit more punctual with reports? No worries at all if not, just a thought!”

The person hears: nothing is wrong.

Say: “Observation: The report was 6 hours late yesterday. Impact: The client meeting slipped. Next step: Flag me by 10am if you’ll miss noon, every time. Can you do that?”

Clear. Respectful. Done in 45 seconds. The person knows exactly what to fix.

How to apply this this week

1. Give one piece of feedback in the next 24 hours. Pick the smallest real issue you’ve been avoiding. Use Observation/Impact/Next step.
2. Never sandwich. No compliment padding. Start with the observation. It’s kinder to be clear.
3. Keep it under 90 seconds. If your feedback takes longer than 90 seconds, you’re overexplaining. Cut it.
4. Log it. After each feedback conversation, write one line: who, what, date. This stops you from repeating the same conversation three times without noticing.
5. Normalize it. Give positive feedback the same way: Observation/Impact. “You closed that ticket early. That saved us the escalation. Thanks.” When feedback goes both ways, corrective feedback stops feeling scary.

Final note

Feedback does not kill morale. Avoiding feedback kills morale.

The team wants a manager who sees the work and says something clear about it. Early, calm, specific. That is respect.

You are not being harsh. You are being useful.

This article is based on the Plain Act approach to early management pressure.

---