📚 Personal bits of knowledge
davidgasquez.com
1# Feedback
2
3Feedback is the core of personal and professional growth. Feedback helps us be better at what we do by establishing clear communications and expectations.
4
5All feedback is good feedback. If you agree with it, it tells you something about yourself which you can work on correcting. If you don't agree with it, it tells you that there is an incorrect perception about you in the other person's mind. You can also work on correcting that.
6
7- When someone tells you something is wrong, they're almost always right.
8- When someone tells you how to fix it, they're almost always wrong.
9- Collect feedback from everybody.
10
11Your goal is not to do what _you_ think is best, it's to help _others_. This includes respecting their preferences, and respecting their autonomy. It's key that you listen to feedback, be open to the possibility that your actions are systematically unhelpful, and work to build better models of your friends and their preferences. In an ideal world I'd only take the actions that are net good, and avoid all of the ones that are net bad, but in a limited information world this is impossible. And empirically, actually trying _far_ outweighs not trying at all. But you still want to get as net good as possible!
12
13## Taking Feedback
14
15- Use the word advice instead of feedback to get more results.
16- The only constant in the world is change. Be open to it and accept it with a smile.
17- Understand and accept that you will make mistakes.
18- Be mindful. Develop meta-awareness around the areas that you received feedback.
19 - Look for opportunities to _stop doing_ or _start doing_ critiqued behaviors.
20
21### Technical Feedback
22
23- You are not your work (code, design, ...).
24- No matter how much you know about something, someone else will always know more.
25- Treat people who know less than you with respect, deference, and patience.
26- True authority stems from knowledge, not from position.
27- Critique code instead of people — be kind to the coder, not to the code.
28- Focus on [Empathy](http://bravenewgeek.com/engineering-empathy/).
29
30## Giving Feedback
31
32- Feedback needs to be informal, frequent, and done authentically.
33- Feedback should be offered with a willingness to listen in return. Those giving feedback should also ask for it.
34- Challenge ideas, not people. Address behavior, but don't label people.
35- Most feedback you deliver should be positive. This makes the negative feedback more important.
36- Prepare. What do you value in someone? Where do you think are their biggest opportunities to improve?
37- **Keep the feedback actionable, specific, and kind.** Be as specific as possible and contain concrete suggestions on how to improve.
38- Imagine what things feel like from the other perspective.
39- Criticize in private, praise in public.
40- You can use a [feedback model](https://jacobian.org/2021/apr/22/three-feedback-models/). These are behavioral and impact focused.
41 - Situation-Behavior-Impact: Describe the situation, then the action of the person and finally, the impact it had.
42 - Manager Tools Feedback Model: Ask for permission, describe the behavior and its impact, finally offer some potential alternatives.
43- How to compose a successful critical commentary (_from_ [_Daniel Dennett_](https://en.wikipedia.org/wiki/Daniel_Dennett)):
44 - You should attempt to re-express your target's position so clearly, vividly, and fairly that your target says, _"Thanks, I wish I'd thought of putting it that way"_.
45 - You should list any points of agreement (if they are not matters of general or widespread agreement).
46 - You should mention anything you have learned from your target.
47 - Only then are you permitted to say so much as a word of rebuttal or criticism.