Quick search for:
When will you consider creating a new metric and accepting the cost of getting it implemented? What makes it worth it vs not worth it?
1 Answer
Unity Director of Product Management • December 13
See question: “What are good OKRs for product management?” for a general introduction to the topic.
I think the metric cost falls naturally into making a solid business case. See question: “How do you approach setting crisp KPIs and targets for Engine features and linking them to your topline metrics?” for my step by step process for realistic OKRs.
Now if the cost of implementing or tracking a metric is unusually high, this might result in wasting efforts, and losing stakeholders confidence. See question “What are some of the worst KPIs for Product Managers to commit to achieving?” for thoughts on “The (nearly) impossible to update number” pattern.
566 Views
Related Questions
What do you report on to build early internal confidence with the product strategy? And how often do you report on this?How do you think about shared KPI’s with your engineering team? And what are ones that product teams often miss?What's your process for figuring out what metrics to hold product management accountable for?What framework has worked for you to help you structure your thought processHow to you handle the end of life (EOL) of libraries?Setting KPIs can often feel arbitrary, especially when entering new markets. How do you get past this uncertainty to set realistic goals?