We are talking about it together as a company, but I'm interested in learning from everyone here.
How do you do feedback? What works well? What doesn't?
We are talking about it together as a company, but I'm interested in learning from everyone here.
How do you do feedback? What works well? What doesn't?
9 comments
Giving feedback, more often than not, will constitute a difficult conversation, and the concept helps a lot with navigating those in a way where both parties can learn and grow from both emotional and 'semantic' conflicts.
[1] https://www.amazon.de/Difficult-Conversations-Discuss-What-M... Brief summary here: http://www.fscanada.org/wp-content/uploads/2013/12/Difficult...
Beware of the Halo effect [1]. For example, people are biased towards their first and last impression. That's why you/everyone should write stuff down regularly, so you can at least try to offer more objective and balanced feedback, and not just on the first thing that comes to mind.
I would recommend the book "Managing Humans", which originated from a blog [2]. It has good content on how to talk to people, and which mistakes to look out for. I found it quite entertaining. I believe you can read all content online.
[1] https://en.wikipedia.org/wiki/Halo_effect [2] http://randsinrepose.com/archives/youre-not-listening/
Love the thoughts on Halo effect. I also feel like other peoples perception, if communicated publicly, biases everyone to that same perception of someone.
I'll take a look at the blog post/book.
"If they don’t trust you, they aren’t going to say shit." is great too.
I feel like the blog post is geared towards 1 on 1's. I like 1 on 1's but I feel they're only one part of how feedback can be given.
My original thoughts, which I didn't describe clearly, are more geared towards creating a culture/environment where feedback is given and received in a respectful, mature, productive, and continuous way.
There are usually two hard parts: 1. People love to complain but usually never directly to the person they're complaining about. As a manager you need to kindly direct their feedback and teach them to talk to each other. 2. People suck at giving useful feedback. They generalize, they talk about personality traits instead of specific examples and their feedback is usually not actionable.
What worked well for me so far is the situation-behavior-impact framework. This helps the feedback giver be more objective and actionable. Also, when you want someone to change their behavior it's important that they should come up with a plan. You just give the framework to it.
If you're worried about the frequency use some triggers. Random ideas: end of sprints, end of projects.
Later on, at another company, we had formal meetings to do the peer reviews with software to document the results. The meetings could be brutal. I remember submitting about 1,000 lines for review, which was a bit long, and the only thing the reviewers found wrong was that one line had "while(something)" instead of "while (something)". They kept going on and on about it. I did get an exemption from having the rest of my code reviewed, though.
Personally, I give and ask for feedback on a regular base to a person I worked with in a period of time. I'll send them a mail asking: looking at the past two weeks, what did I do well? And where could I improve?
They just did a series on performance review systems.
> 10 < 25 people and really anything over 15ish people gets harder to manage so you need some formality to it, e.g. schedule and documentation. But don't try to make some great review/feedback system initially. Just set aside more time, talk to people, listen, keep good notes and formalize the process with documentation and scheduled follow up. This is also the time that if you haven't already you should expand the loop where there isn't just one person doing most of the feedback cycle.
> 25 < 50, you absolutely need some formalization and you need to delegate feedback cycles to team leads, or trusted individuals and the founders need to work closely with those leads to make sure they are staying in the loop. For every team < ~10 people have the team lead follow the first version, just with solid documentation and follow up that they are taking care of their teams. If you are a founder/director etc level start reducing your daily influence with team activities so that the team starts to depend more on the lead, this isn't because you are pulling away or inaccessible, but you need to give space for the team to form around the immediate leadership and not just you. If you don't do this, you will fail as a leader and you will cause all your direct reports to fail over time.
> 50 you should by now have hired at least one (possibly a few) dedicated HR staff who can help formalize the process more and grow it sustainably. Usually, I'd recommend this around 35-40 people as you just can't deal with everyone's issues. But over 50 it is really mandatory as the laws generally change as to your employee responsibilities etc.
This is different than some of the other answers, but hopefully gives some insight. Also if you follow this generally the culture revolves around solid constant, quality feedback so it will just be instilled from very early on. Which is really helpful as you grow.
One last point, this works great with knowledge workers and most business types. If you are leading manufacturing, day labor or unions than things change as the personalities and needs are different. Doesn't make either better or worse, you just have to respect that they are different and have different needs.
- what could be better?
Using descriptive terms.