Managing a team
Feedback, praise, nudges and the conversations most managers postpone. Filter by role or search for the situation.
10 templates · free · no sign-up
I'm a…
Sending it as…
Name the behaviour and the effect. 'Great job' teaches nothing.
[Name] — the way you handled [specific situation] was excellent. Specifically: [what they did]. The result was [effect on the team, customer or project]. That's exactly the judgement I'd want on anything difficult. Thank you.
Observation, effect, request. No sandwich.
[Name], can I give you some feedback on [situation]? What I noticed: [specific, observable behaviour — not a character judgement]. The effect: [consequence]. What I'd like instead: [concrete alternative]. How does that land with you? Happy to hear if I've read it wrong.
Give them the agenda in advance so it's their meeting, not yours.
Hi [Name] — our one-to-one is [day] at [time]. It's your time, so bring whatever's on your mind. Things I'd like to cover if there's room: • [Topic] • [Topic] Anything you want added, drop it in here beforehand.
Ask about the blocker, not the delay.
Hi [Name] — how's [task] looking for [date]? If something's in the way, tell me now and I'll help clear it rather than find out on the day.
Before they burn out, not after they resign.
Hi [Name] — you've had a lot on lately: [list what you've noticed]. I'd rather we drop or delay something than have you carrying all of it. If you had to take one thing off the list this week, what would it be? No wrong answer here.
Send it the morning they start. First impressions compound.
Welcome, [Name]! Really glad you're here. Your first week, roughly: • Today: [what] • This week: [what] • By Friday: [realistic first win] [Buddy name] is your go-to for anything day-to-day. My door's open for everything else — and no question is too basic in your first month.
State the outcome and the constraints, then get out of the way.
[Name], I'd like you to take [task]. **What good looks like:** [outcome] **By:** [date] **Constraints:** [budget, tools, anyone to involve] **Decisions you can make alone:** [scope] — come to me only for [exceptions] How you get there is yours. Shout if you want a sounding board.
Explain the reasoning or they stop bringing you ideas.
[Name] — thanks for putting [idea] together, genuinely. We're not going to do it this quarter. The reason is [honest constraint: priorities, cost, timing], not the quality of the thinking. Keep it — if [condition changes] it becomes a much easier yes. And keep bringing me these.
Fix first, learn second, blame never.
[Name] — thanks for flagging this quickly, that's the right instinct. Right now: [immediate fix, who's doing what]. Once it's stable, let's work out what made it possible. I'm interested in the gap in the process, not in whose hands were on it.
Say the decision first. Burying it reads as evasion.
Subject: A change to [thing]
Team, From [date], [the change]. Why: [the honest reason, including the trade-off you accepted]. What it means day to day: [specifics]. What isn't changing: [reassurance, where true]. I know [the part people will dislike] is unwelcome. I'm around [when] to talk it through — and if there's something I've missed, I'd rather hear it than not. [Your name]
Nothing matches that
Try a plainer word, or clear the filters above.
Useful feedback names what you observed, what it caused, and what you would like instead. Drop any one and it fails: observation alone is nitpicking, effect alone is blame, and a request without either is arbitrary.
The first part must be observable. The report arrived after the deadline twice can be discussed and explained. You are disorganised can only be defended against, because it is a claim about identity rather than behaviour. Sticking to what actually happened is not a softening technique — it is what makes the problem solvable.
Great work signals approval but teaches nothing. Naming the behaviour and its effect turns a pleasant moment into a repeatable instruction.
Specific praise is also much harder to dismiss as politeness. People discount general compliments from managers almost automatically, assuming a technique. A detailed observation cannot be discounted that way because it is evidence of attention. Public praise amplifies the effect, but check first, since some people find it excruciating and the gesture then costs more than it gives.
Burying criticism between two compliments is common enough that people hear the praise as packaging and discount it, and the actual message frequently does not register at all.
Give praise on its own and correction on its own. Both are taken more seriously when neither is cushioning the other. The sandwich survives because it makes the manager more comfortable rather than the recipient, and if the conversation feels difficult, that discomfort is the cost of doing it properly — considerably smaller than someone learning at a review that there had been a problem for months.
The most common failure is that they become status updates, which is a meeting the manager needs. Status can go in writing; the conversation should be for what does not fit in writing.
Send the agenda in advance and make clear it is their time. Protect the slot, because repeatedly cancelling communicates a priority ranking more clearly than anything you say. And leave silence — the useful part often arrives after a pause the manager was tempted to fill, and learning to wait through it is most of the skill.
Handing over work badly produces either paralysis or a manager who takes it back halfway. Being explicit about three things avoids both: what good looks like, the constraints, and which decisions they can make alone.
That third one is what determines whether they are genuinely free to act, and it is the one most often skipped. Say what they can decide without asking and honour it. Checking progress is fine; reversing a delegated decision is not, and doing it once teaches the person to seek permission for everything. The point of delegating is to move the judgement, not just the task.
A performance conversation should never be the first time someone hears there is a problem. Ongoing feedback is what makes the formal version survivable.
When it comes, be specific about the gap, clear about what must change and by when, and honest about the consequence. Vagueness here is a kindness that is not kind. Afterwards, write a short factual note of what was discussed and agreed and send it. Both parties will remember the conversation differently, and the written version protects everyone including the person receiving it.
