The 30/60/90% framework for feedback
Feedback is a good thing, but sometimes it can come at the worst time. There's always that one person nit-picking grammar when you're trying to define what the project actually is. The 30/60/90% framework helps.
As someone that has opinions, this framework really helped me to rein in the feedback I'm giving at certain points in the project. The idea is that you ask for feedback three times within a project:
- 30%: We have a rough idea what the project needs to achieve, and how to achieve it. Good feedback at this point focuses on concepts and scope. Bad feedback would be focused on grammar or sentence structure.
- 60%: The first draft is ready. This is what most people think of when asked to provide feedback. You can still make invasive changes if the base assumptions do not hold, but most people are looking for feedback on their framing at this point.
- 90%: The project is ready to ship. The person asking for feedback is dotting their I's and crossing their T's. Fundamental changes are not possible at this point. Any feedback at this stage is about positioning, and helping the person identify anything that they've missed.
Providing the wrong type of feedback has a negative impact for everyone involved. Either the feedback is accurate, and the author now has a conundrum to deal with, or it's invalid and you look like a troublemaker for no reason.
By focusing on the type of feedback and questions expected in each phase, you can maintain relationships with the people you're collaborating with and ensure that your voice is heard at the most opportune time.