A few weeks ago @doctolib we had a great workshop about giving and receiving feedback.
We shared a lot of tips that I had never thought of and wanted to share them with you! 🤓
A feedback is a return of experience from another person on yourself that helps you grow
💡 It has to be either:
- positive or
- constructive: give the receiver insights into improving
- 👯 With your peers:
- via code reviews, peer-programming...
- 👔 With your manager:
- during 1:1 sessions, code reviews...
- 🎨 With your product owner or designer:
- during planning poker estimation, when working on a ticket, when delivering a feature...
- 🤝 With your client(s) or user(s):
- through user interviews, A/B testing...
Implementing a feedback culture will:
- 🌱 allow people to improve and grow
- 🤲 reinforce trust
- 💪 boost motivation
💡 Plus it's a virtuous circle: you get feedback, you get better, you feel more motivated, you give feedback to others...
- Know what you will talk about and how you will illustrate your feedback
- For constructive feedbacks: prefer 1:1 sessions
- For positive feedbacks: spontaneous or public feedbacks are a good option if the person is comfortable with
- Make sure you are available: present and listening
- Make sure your interlocutor is physically and emotionally ready
- Find a calm place
- Support your feedback with concrete examples and figures, not only with your feelings
- Praise efforts and not just results
- Don't judge directly but talk about perception: by using the first person 'I'. You could for instance use
it seems to me that...rather than
you are this way...
- Make sure you give clear next steps for the person to improve
- But don't enforce them: it's way better if you can define them together
- Ask how the other person feels after receiving your feedback
- Make sure he/she understands and agrees on the actions
- Understand how the person works and what's the best way for them to receive feedback
- Don't make assumptions: if you assume what the other people are thinking, you’ll never get their truth but only your version of it... which leads to misunderstandings! Better ask the other person how they feel
- Make it a habit in order to demystify the process
- If you have a regular dedicated time, you won't apprehend a 1:1 as a potential fearful encounter
On that topic, another Doctoliber wrote this fun article How to ruin a 1:1, in which he lists the worst things you can do to sabotage a 1:1 😈.
Receiving feedback is not only hearing it without being mad or hurt. It also means being able to build on it, find meaningful actions and ask for advice.
- Avoid interrupting your interlocutor
- Make sure you understood, rephrase if necessary
- But don't feel obligated to say something back!
- For having the courage to give you feedback!
- Remember it can be uncomfortable on both sides...
- Write it down or just keep it in mind, so you can go back to it when necessary
- Be proactive: don't hesitate to ask for feedback
- Suggest having regular 1:1 sessions when necessary
💡 If you don't feel comfortable with a feedback you received:
- don't hesitate to reschedule until you're prepared
- change the scenery: go grab a coffee, go for a walk...
I hope you enjoyed this article 🥳.
I am particularly interested in the topic of Code Reviews and giving / receiving feedback is definitely key in that process!
If you're interested too, I wrote an article about it:
Also, feel free to reach out to me if you want to add anything on that topic or have tips! I'd love to hear about them 🙌