The Five-Minute Peer Feedback Chat That Won't Make You Sound Like a Manager

Giving feedback to a colleague is one of those workplace skills nobody teaches you properly. If you are their manager, you have a framework: objectives, reviews, the awkward form on the intranet. If you are their peer, you have a cup of tea and a nagging feeling that something needs saying.

Maybe they interrupted someone in a meeting. Maybe their handover notes left out who owned the invoice query. Maybe they arrived late to the stand-up three days running. You are not their boss. You do not want to act like one. But you also do not want to sit on it until you are quietly annoyed.

Here is a three-step script for peer-to-peer feedback that is honest without being heavy-handed.

Step 1: Pick the moment, not the audience

Timing matters more than wording. Feedback lands badly when it is public, delayed or dropped into a busy moment. Do not put it in the team channel. Do not wait until the Friday afternoon all-hands. Do not ambush them as they are running for a train.

Ask for a short, private conversation. 'Have you got five minutes for a quick chat?' is usually enough. A walk to the kitchen or a short Teams call works well. Avoid 'We need to talk', which sounds like a disciplinary hearing. Make it clear this is a normal, low-stakes conversation.

A useful opener is: 'Nothing heavy — I just wanted to compare notes on the handover.' That tells them the tone before they have time to panic.

Step 2: Describe what you saw, not who they are

This is the bit most people get wrong. We turn a single incident into a character judgement. 'You are dismissive' is not feedback. It is a label. 'In yesterday's client call, you jumped in three times before Priya had finished' is feedback.

Stick to what a camera would have caught. Say what happened, when it happened and what impact it had. Use 'I noticed' rather than 'you always'. Use 'I might have misread it' if you genuinely might have. That is not weakness. It is accuracy.

UK workplace example: 'The notes from Tuesday did not say who owned the invoice query. I spent an hour chasing the wrong team, so I wanted to flag it.' That is specific, factual and hard to argue with. It is also much easier to hear than 'your notes are always vague'.

One incident is usually enough. If there is a pattern, you can mention it once you have named the specific example. Do not open with 'everyone has noticed'. That makes it sound like a group complaint and puts them on the defensive.

Step 3: Ask a question, then listen

A question-led script takes the heat out of the moment. It invites them to explain rather than defend. It also stops you from sounding like you have already decided what they should do.

Try this:

'Can I flag something from the handover? I noticed the note did not name an owner for the Friday deadline. I ended up guessing and nearly sent it to the wrong team. I might have missed some context — how did you see it?'

That script works because it does four things. It asks permission. It names the specific observation. It states the impact on you. It leaves room for their side.

Then stop talking. This is the hard part. Give them a few seconds. If they get defensive, do not match it. Say: 'That is fair. I am not trying to make a thing of it — I just wanted to flag it because I would want someone to tell me.'

Avoid phrases like 'with respect', 'just saying' or 'some people think'. They sound polite but they usually mean you are not saying the thing directly. Also avoid 'Don't take this the wrong way'. It almost guarantees they will.

Agree next steps without acting like their manager

You are not setting objectives. You are not writing a performance improvement plan. You are trying to make the next piece of work easier for both of you.

Ask for a small experiment. 'Could we try adding an owner line to handover notes for the next two weeks?' Or: 'Would it help if I asked for clarification in the channel rather than saving it up?' Or: 'Next time, could you give me a heads-up if the slides are running over?'

Offer something from your side too. 'I will flag it earlier if I am unsure' or 'I will try to ask in the meeting rather than after'. Feedback feels less like an attack when it is a two-way adjustment.

Keep the follow-up light. A quick 'thanks for that — the notes were much easier to follow' goes a long way. If nothing changes and the issue is affecting work, you may need to involve a manager. But that is a separate conversation. Do not use peer feedback as a stealth escalation.

What to avoid

• Saving it up for months and then delivering a speech.
• Giving feedback in front of other people.
• Using email for anything sensitive, where tone gets lost.
• Saying 'you always' or 'you never'.
• Turning it into a joke so nobody has to feel uncomfortable.
• Pretending it is not feedback when it clearly is.

A short script you can borrow

'Hi — got two minutes? I wanted to flag something small from the workshop. When the slides ran over, we did not get to the Q&A, and I think a couple of people had questions. I might be reading too much into it — how did it feel from your side?'

Then listen. Then try: 'Could we set a five-minute warning next time?'

That is it. No job title required. Peer feedback is not about being the boss. It is about being a colleague who says the useful thing early, clearly and kindly. Done well, it stops small problems becoming big ones — and it makes the team less dependent on a manager to notice everything.