Your first feedback conversation as a manager will probably go badly. Not because you're cruel or incompetent, but because you'll do what almost every new leader does: you'll soften the message so much that the person leaves the room smiling and understood nothing. Three weeks later the same problem shows up in a project review, and you're angrier than the original issue deserved.
I know this because I did exactly that. In my first month leading a team of six, I had a conversation with a developer who kept missing handoff deadlines. I opened with a compliment about his code quality, spent ten minutes on context, and closed with "maybe just try to be a bit more mindful of timelines." He nodded. Nothing changed. When I finally asked him directly, he said: "Honestly, I thought you were just making conversation."
Giving constructive feedback as a new leader is a mechanical skill before it's an emotional one. It has a structure, a vocabulary, and a timing rule. Get those right and the awkwardness drops by half. Get them wrong and no amount of empathy will save you.
Key Takeaways
- Feedback fails most often because of vagueness, not harshness. Name the behaviour, not the personality.
- Use a fixed structure (Situation–Behaviour–Impact) so you don't improvise under stress.
- Deliver within 48 hours of the event. Delayed feedback becomes an ambush.
- As a new leader, your first three months are about observation and expectation-setting, not correction.
- Ask the person to restate the ask in their own words. That single step catches most misunderstandings.
- Never give feedback in front of the team. Praise publicly, correct privately, always.
Why new leaders get feedback wrong (and it isn't what you think)
The standard explanation is "you're too nice" or "you're afraid of conflict." In my experience that's only half true. The real problem is that new leaders haven't yet separated two things that used to be fused: being liked and being useful to the team.
You were promoted from among these people. You ate lunch with them. You may have complained about management with them. And now you have to tell one of them that their work isn't good enough. The discomfort isn't about the message. It's about the role change.
The former-peer problem
This is the specific trap nobody warns you about. Feedback to someone who knew you before you had authority lands differently. They hear your voice, not your title, and your voice still sounds like the person who sat next to them in standup.
What worked for me was a short, unglamorous conversation in week one, with each person individually: "I'm going to be giving you more direct feedback than before. That's not me changing as a person, it's the job. If something I say lands wrong, tell me." Ten minutes each. It cost me a morning and saved months of weirdness.
The credibility trap
New leaders often wait for a "credibility window" before giving hard feedback. It never opens. Waiting is itself a signal, and the team reads it as either indifference or weakness. The longer you wait, the more the first correction feels like a verdict rather than a course correction.
Here's what I'd argue, and I'll hold this position: your first piece of corrective feedback should land inside your first thirty days. Not a big one. Something small and real. It establishes that feedback is normal here, which is the only condition under which hard conversations become survivable later.
The formula you can actually use in the room
Every framework in the world reduces to the same three beats. Situation, behaviour, impact. You describe when it happened, what you observed, and what followed. That's it. The value isn't in the acronym, it's in the fact that you don't have to invent sentence structure while your heart rate is at 110.
Situation, behaviour, impact — with a real script
Here's the version I use now, written out, because "be specific" is useless advice when you're nervous.
Weak version: "I feel like your communication with the design team could be better."
Working version: "In Tuesday's kickoff (situation), you told the design team the spec was 'basically done' (behaviour). They started building against it, and on Thursday we had to redo two screens because the requirements changed (impact). Next time, can you say 'draft, expect changes' until it's signed off?"
Notice what's absent. No "you always," no "you never," no evaluation of character. The person can argue with facts if they disagree, but they can't argue with your feelings, and they shouldn't have to.
The two-sentence version for small stuff
Not every issue deserves a meeting. For minor corrections, I use a compressed form: "When X happened, Y was the result. Can you adjust that next time?" Two sentences, said in the hallway, done. Reserving formal feedback sessions for things that actually matter keeps the formal ones meaningful.
What are good examples of constructive feedback?
Good examples share one feature: they are specific enough to be acted on tomorrow. A sentence that could apply to any employee at any company is not feedback, it's atmosphere. Below are pairs I've actually used or heard used, with the weak version first.
Five pairs, from vague to usable
- "You need to be more proactive." → "In the last three sprint reviews, you flagged blockers during the meeting rather than before it. Flagging them a day earlier would let me unblock you instead of us losing the sprint."
- "Your emails are too long." → "Your update email on Monday was nine paragraphs. I read the first two and skimmed the rest. A three-line summary at the top would get more people to act on it."
- "You're not a team player." → "In Wednesday's review, you cut across Sam twice before they finished their point. Sam stopped contributing after that. I want to hear their full thought next time."
- For a strong performer with one rough edge: "Your analysis is the best on the team. The thing that's costing you is how you deliver it — you opened the last review with 'this doesn't work' and the room shut down. Lead with what does work, then the problem."
- Positive, and specific: "You rewrote the onboarding doc without being asked, and the two new hires got through setup in one day instead of three. That's the kind of thing I want to see more of."
That last one matters more than new managers think. Praise that is generic ("great work") trains people to ignore praise. Praise that names a behaviour and a consequence trains them to repeat it.
The closing move almost everyone skips
End with a question, not a statement: "What's your read on this?" or "What would make that easier?" You'll get two kinds of answers. Sometimes the person explains a constraint you didn't know about, and your feedback was aimed at the wrong target. Sometimes they just agree. Either way, you learn something, and they leave with agency rather than a verdict.
Then — and this is the part I kept forgetting — ask them to say back what they're going to do differently. Not to test them. To check whether your sentence survived the trip from your mouth to their understanding. Mine frequently didn't.
What is the 30-60-90 rule for managers?
The 30-60-90 rule breaks a new leader's first three months into three phases with different goals: the first 30 days are for listening and observing, the next 30 for diagnosing and forming your own view, and the final 30 for acting on it. The point is sequencing. You can't correct what you haven't understood, and most new managers start correcting in week two.
What each phase means for feedback
| Phase | Your job | Feedback posture |
|---|---|---|
| Days 1–30 | Meet everyone individually, read old project docs, watch how work actually flows | Ask questions. Give almost no corrective feedback. Note patterns privately. |
| Days 31–60 | Form your own view of what's working and what isn't, independent of your predecessor's opinions | Start with small, low-stakes corrections. Test how the team receives them. |
| Days 61–90 | Set expectations explicitly and address the patterns you identified | Full feedback conversations. This is when the real ones happen. |
I'll be honest about where I broke this. In my second management role I skipped the listening phase because I "already knew the team" from working alongside them. I gave a corrective note in week two about a process that, as I learned in week five, existed for a legal reason. I had to walk it back publicly. That cost me more credibility than the original problem ever would have.
What are the 5 C's of leadership?
The 5 C's of leadership are commonly listed as communication, collaboration, commitment, confidence, and compassion. They're a reasonable set of headings, and every one of them shows up in a feedback conversation whether you plan for it or not.
Communication is the mechanics — clear, timely, specific. Collaboration is whether the person feels you're solving the problem with them rather than about them. Commitment is following up, which is where most feedback dies. Confidence is your willingness to say the uncomfortable sentence without a paragraph of preamble. Compassion is remembering that the person across from you has a whole week you know nothing about.
Where I'd push back: these lists tend to make leadership sound like a personality. It isn't. Compassion in a feedback conversation isn't a feeling, it's a behaviour — choosing a private room, choosing a time when neither of you is about to run to another meeting, choosing to name the behaviour and not the person. Those are decisions, and decisions can be practised.
What are the top 3 weaknesses of a leader?
The three weaknesses that do the most damage, in my experience, are avoiding difficult conversations, taking credit that belongs to the team, and changing direction without explaining why. All three are feedback problems in disguise.
Avoidance, and how it compounds
Avoided feedback doesn't disappear. It accumulates. The person keeps doing the thing, you keep resenting it, and eventually you deliver a summary of six months of irritation in one sitting. To them, it comes out of nowhere. To you, it's overdue. That gap is where trust dies, and it takes far longer to rebuild than it would have taken to have a ten-minute conversation in month one.
Credit, and silent pivots
The other two are quieter. A leader who absorbs team wins into their own status loses the room slowly and then all at once. A leader who changes priorities without a sentence of explanation teaches the team that effort is unreliable, and effort is the one thing you can't buy back once it's gone.
Both are fixable with the same habit: narrate your decisions. "We're dropping X because Y changed. Here's what that means for your week." Thirty seconds. It reads as respect, because it is.
The habits that make it stick
Two practical things, then I'll stop.
First, keep a running note. One line per observation, dated, no interpretation: "Tue 14th — pushed back on scope in review, no alternative offered." When a pattern appears after three or four entries, you have evidence instead of an impression. This single habit took my feedback from "I feel like" to "here are three instances," and the difference in how it was received was enormous.
Second, give positive feedback with the same structure. Same specificity, same timeliness, same private-or-public rule. If the only structured conversations you have are corrective ones, people will learn to dread your calendar invites. That's a real cost, and it's one I paid for about four months before I noticed.
The thing that stays with me is how little it takes. The conversations I dreaded most, the ones I rehearsed for twenty minutes in the car, were almost never as bad as the dread. Twice, the person thanked me. Once, they told me something about their workload that changed how I ran the whole quarter.
And the ones I avoided? Those are the ones I still think about.
