Feedback
Practice
A conversation that tells someone what worked and what to change while the work is still fresh, so the next round goes differently.
Why it exists
There was a long stretch where the only place to say what went well and what didn't was review season. One meeting every six months, and in it six months of material delivered at once. Information that arrives that late is usually unusable.
Take one case. In April someone cut across a colleague three times in a retrospective, and two people stopped talking for the rest of it. Nobody said anything that day. In August the manager finally raises it: listening in meetings needs work. The person can't place which meeting, and in the meantime has run eight more retrospectives the same way. Eight chances to change something went by untouched.
Good work disappears in the same gap. Someone stays up through the night in March to fix an outage, it becomes one line in an August review document, and the signal that the company wanted exactly that behavior arrives five months late.
The word feedback exists to pull this conversation out of the review. Grading a period and assigning a rating is batch work that waits for the period to end. Telling someone how something landed belongs to the week it happened. Put both in the same meeting and the second one always loses.
How it runs
One round of feedback moves through four beats: state the fact, name the effect, hear the other side, and agree on one thing to do differently. Five minutes is normal and fifteen is long.
- Start with what was observed. Stick to what anyone in the room would write down the same way. "In yesterday's retrospective you came in three times before someone had finished" is a fact. "You're domineering in meetings" is already an interpretation, and it invites an argument about character instead of behavior.
- Add the effect the behavior produced. "Two people stopped contributing after that, and the retro ended with one action item" is the part the other person probably couldn't see. Without it there is no reason to change anything.
- Hear the explanation. There were five minutes left on the clock; it was the third time the same point had come up. Reasons surface here, and if the fact turns out to be wrong the rest of the conversation stops.
- Agree on exactly one thing to do differently. Three things means none of them happens. "Next retro, wait until everyone has been around once before adding anything" is about the right size.
- Check that one thing next time. Feedback nobody follows up on reads as criticism and nothing else.
Praise runs on the same four beats. "You found the cause and rolled back within thirty minutes, so nobody hit it during the morning rush" is what makes the judgment repeatable. "Nice work" leaves no record of what was good, so there is nothing to repeat.
The posture that keeps all of this moving has its own name, radical candor. Recite facts without caring about the person and they will remember the tone instead of the content. Soften it to protect the relationship and they walk away not knowing a problem existed.
Who joins and when
It usually runs from manager to team member, but the direction isn't fixed. Peers who worked together trade it most often, and it travels upward too. Upward feedback rarely appears on its own, though, which is why companies add a structured collection point such as 360-degree feedback, where input is gathered from several directions at once.
Timing defaults to the same week. After a few days the details blur, and after two weeks the other person starts merging the event with other ones. Short items get handled in a minute right after the meeting ends. Anything that needs sitting down — a pattern repeating over several weeks, for instance — goes into the recurring one-on-one that is already on the calendar. Raising something for the first time two weeks before review season is late, and what gets said there sounds like an explanation of a rating rather than feedback.
The setting splits too. Praise is better said with other people in the room. Anything to correct is said with exactly two people present. The same sentence in front of a third listener gets processed as embarrassment first, and after that only defensiveness is left.
The receiver's state is a condition as well. On a team where psychological safety is low — where people don't feel safe admitting mistakes or disagreeing — a plain statement of fact reads as a reprimand. Plenty of managers open with a sentence separating the two: this is feedback, it isn't your rating.
How it sounds at work
"You came in twice during yesterday's retro and Noa stopped talking after that. Next time, want to wait until everyone's been around once?"
Fact, effect, and one next action packed into a single sentence.
"Can I give you one piece of feedback? It'll take five minutes."
Checking whether the receiver is in a state to hear it before the content arrives.
"Don't put that in the review document first — tell them this week."
A request not to raise something in a written review that was never said during the period.
At Pagedeck, retrospectives started running twenty minutes over once Theo began facilitating them. On the afternoon of the third one, Mia pulled him aside with two things: that holding discussion open on every item had turned a fifteen-minute meeting into thirty-five, and that the last two items had gone by without discussion as a result. Theo said he had assumed every item deserved equal treatment, and the two of them agreed on a single change — a three-minute timer per item.
The next retro, two weeks later, finished in eighteen minutes. What the manager did here was not judge; it was hand over a consequence Theo couldn't see from where he stood.
What people get wrong
The most common reading is that feedback is a polite word for criticism. The habit forms because a dedicated conversation usually only gets scheduled when something needs correcting. But running the same four beats on good work is the more reliable half of the practice, since it tells someone which behavior to repeat. Left as is, an offer to give feedback reads as a warning, and people start avoiding the conversation entirely.
The other common belief is that wrapping a correction in two compliments softens it. It does make the sentence easier to say. After two or three rounds, though, the receiver reads the opening compliment as a trailer for what's coming. From then on real praise gets heard as a setup, and the correction lands as the quietest part of the exchange.
Easily confused with
| Term | When it happens | How it differs |
|---|---|---|
| Performance review | After a quarter or half closes | Judges a closed period and connects to ratings and pay. Feedback makes no judgment and aims to change behavior mid-period |
| One-on-one | On a fixed recurring interval | A standing container for an open agenda. Feedback travels inside it but isn't tied to it, and often happens right after the event, anywhere |
Where to go next
- Performance management
see where this conversation sits inside the cycle
- One-on-one
the recurring meeting that carries feedback most often
Last updated 2026-09-16