Feedback is a gift. Feedback has a vital role in product development. Not only it can nurture the product, but it also could nurture the people who build the product. Yet as we’re all know, giving good constructive feedback is damn hard. Hence, I have been experimenting with this framework to make myself better at it; which hopefully can be useful for you too.
Analyze, Discuss, and Suggest
This framework helps me navigate when I’m reviewing works. I’ll explain a little bit of each point and guiding principles on each. Let’s dig into it.
The first thing you’ll need to do is to listen and analyze the work. What I mean here is to see if anything stand out from work presented, which can be both good things and bad things.
A few things to keep in mind:
- First thing first, the intent of the feedback should always be helpful and not be offensive nor destructive. Be respectful to the team presenting. Sure, you can analyze everything, but if the presenter asks for specific feedback, you should respect that and make that as a priority. Also, be sincere, it’s not quite useful to give any insincere compliment (like sandwich method) and focus on what matters.
- If you spot something that doesn’t feel right, pay attention to that and try to complete the blank of this statement: “I’m not sure about X because…”
A few questions that I’ll try to answer while analyzing:
- What is the goal of this project?
- What human problem is this trying to solve?
- How close is this design achieve the goal?
- How do I feel about this in general?
Now it’s the time to discuss what you’ve analyzed. Whenever possible, try to spark the conversation around the room rather than giving a statement.
A few things I’d pay attention at this point:
- Now, let’s say the work presented is 180-degrees from where you think it needs to be or maybe there’s an aha-idea in your head. Well, hold on. Ask questions first, try to understand why the team did that in the first place. Maybe the team has thought about that and have a rationale on why not to pursue that idea. And most importantly, do not dominate the conversation so you can learn and read the room better, this can be a good opportunity to do a gut check.
Once you analyze and discuss, it could be helpful to suggest a sort of direction or guidance. This part often blends together with the discussion. And, by the way, this doesn’t mean you always have to give a suggestion.
A few things I’d pay attention at this point:
- When suggesting a direction, try to make it solution-agnostic, which mean the suggestion should not imply any sort of specific solution because you want to give a room for the team to explore. At the same time, you have to be articulate, you have to be clear on what you think needs to be improved. Otherwise, it will be very hard for anyone to know what do they need to improve upon.
- Once the discussion started, things can get pretty messy. Maybe some people in the room start to raise different philosophies or opinions about which direction to take, which is normal. When it happens, what I find useful is to lay out all the options on the table and this can be helpful for the team or the decision maker to weigh on what’s the best direction moving forward.
I don’t feel great about the last feedback session I had, what should I do?
Don’t worry, we’re all been there! Try again. With this framework, you can analyze which part you are at the most? It’s all about the balanced seasoning.
- Analyze 20%, Discuss 10%, Suggest 70% = Possibly destructive
If you spend more time suggesting your thought, that can lead to destructive feedback because you spend a lot of time articulating your thought without trying to understand the context or the situation of that team.
- Analyze 30%, Discuss 60%, Suggest 10% = Somewhat balance
This is the combination that I’d prefer. If you spend more time to discuss and understand, chances are, you will be able to help the team in the area they struggle with.
Sometimes, I suggest a solution, is it a bad thing?
Although I’ll try to avoid that. Sometimes, I do that too when I’m running out of time or maybe I’m running out of patience. But, this shouldn’t happen often. Giving a solution-agnostic suggestion is healthier for the team because it will let them go through the process.
Closing chat to the reader
I hope this is useful. You can try it, maybe experiment with it a little bit. I’d love to hear if you have another framework, or maybe you have questions – you know you can reach me out. And as always, if you think the post is worth sharing, share it with your friends, colleagues, or (maybe) the rest of the world!