Skip to content

Blog · Development at work

Feedback is most useful while the work can still change

2 min read

Feedback that arrives at the year-end review describes work that is long finished. Feedback that lands on the work while it moves can still change it.

Late feedback is a verdict

Once a year, people hear how a year of work landed. By then the project is shipped, the decisions are made, and the only thing left to do with the feedback is file it. It reads as a verdict, not as help.

Put it on the work

Feedback is easier to give and easier to act on when it is about something specific: this rollout plan, this review, this incident write-up. Attached to the work itself, while it is still moving, it is a conversation about the next step rather than a judgement about a person.

It also does not need a new place to live. Much of the useful conversation already happens in chat, comments and reviews in the tools teams use. Counting that conversation, and letting people give feedback where they already work, removes most of the friction.

Make it something people can act on

Two qualities matter most in feedback: whether it is actionable, and whether it is constructive. Measuring both, for everyone, makes giving good feedback a visible skill rather than a matter of personality.

On the receiving side, a person should be able to see how colleagues see their key and technical skills as the year goes on, and drill down to the feedback behind every figure. That is development they can steer, not a surprise at the review.

Keep the reflection private

Acting on feedback is personal work. In Nextdot, the Development Assistant helps each person structure their own development from their own record, and its conversations are private: no one else in the organization sees them.