Team and Culture · Published July 19, 2026
Feedback Should Not Wait for Year-End
Criticism first heard in a year-end review is already six months late.
In one annual review a colleague said: I actually thought that approach was wrong early on, but planned to mention it at year-end. That sentence made us realise how much value deferred feedback loses.
Make feedback small
After each collaboration, spend two minutes on one specific good thing and one specific improvement, aimed at work, never at the person.
Project retrospectives include a fixed collaboration-feedback segment: whose work helped you, and where you got stuck.
Managers hold a twenty-minute monthly chat with everyone about state and growth, not task status.
What the receiver does
Say thank you first, and resist explaining. Explanations teach people to stop telling you things.
Decide within a week whether to adopt it, and tell the giver. Adopt and change, or decline with a clear reason.
Publicly credit useful feedback. Make truth-telling cheap.
Feedback decays with time. One sentence said the same day beats three pages written in December.
← Previous post
Retrospective: The Cost of Compressed Testing
Next post →
The Next Phase of the Mini Program Ecosystem
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →