> For the complete documentation index, see [llms.txt](https://fuse-lab.gitbook.io/fuse-lab-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fuse-lab.gitbook.io/fuse-lab-docs/growth-and-feedback/feedback.md).

# Feedback

Feedback should be normal enough that it does not feel like somebody has called you into the principal's office.

Give it close to the moment when it can still be useful. Be specific about the work, behavior or outcome. Explain the impact. Where appropriate, suggest what better looks like.

Feedback should flow in every direction. Leads need feedback too.

User Manuals can help you understand how somebody prefers to receive feedback, but preference does not override responsibility. We still need to be able to say hard things to each other.

When receiving feedback:

* listen before defending
* ask questions if the point is unclear
* separate discomfort from disagreement
* decide what you will do with it
* say if you disagree, then explain why

Not all feedback is correct. All serious feedback deserves to be understood.