I'm hoping to get some clarification on the Goal Impact and Insights Impact fields so I don't use them incorrectly or provide incorrect information to my team members. Can someone tell me how we should look at these? I see they are subjective measures, but what should we be thinking about when applying a value? These are both impacts, but impacts on what?
Is the goal impact a measure of how much this particular idea impacts the ability to achieve the goal? I'm less clear on how to think about the insight impact. The thing I keep asking myself is, impact on what?
Thanks for the help!
Well, once again @Jonathan Hau you beat me to it! Thank you 😊
@David We've built the system in a way that lets you define the framework you plan to use to prioritize your roadmap collaboratively and communicate these priorities. The default project template, as well as every field in there, are just here to help you understand the type of use cases we designed the app for.
But what we recommend is you go through it with your team and define what these fields, and their values, mean in your context. Because in the end we don't see prioritization as a numbers game (even when using formulas!). Rating fields, insights impact, ... : these things are just simple primitives to help you answer:
So, for example, we don't recommend prioritizing based on a number of votes. BUT voting can be a very useful exercise to understand if, as a team, or with you're stakeholders, you're aligned or not: