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.
278 Views
Top Product Management Mentors
Laurent Gibert
Unity Director of Product Management
Farheen Noorie
Grammarly Monetization Lead, Product
Deepak Mukunthu
Salesforce Senior Director of Product, Generative AI Platform (Einstein GPT)
Mike Flouton
GitLab VP, Product
Tara Wellington
BILL Senior Director of Product Management
JJ Miclat
Zendesk Director of Product Management
Paresh Vakhariya
Atlassian Director of Product Management (Confluence)
Aaron Bloom
Bluevine Senior Director of Product Management
Clara Lee
PayPal VP, Product
Natalia Baryshnikova
Atlassian Head of Product, Enterprise Strategy and Planning
Related Questions
What are some of the *worst* KPIs for Product Managers to commit to achieving?How do you measure the performance of the product team, considering only product managers, group product managers and product head?Have you leveraged Gen AI to communicate and report on things internally to stakeholders? What has been the most valuable artifact that AI has helped you create?how do you think about building products for a developer audience? what ways have you adjusted your product development process for the developer persona?How to make sure KPIs are not 'proxies' to what we want to achieve but directly measure it?One thing we've always struggled with ongoing communication about the success of previous launches. Do you have a framework for revisiting and communicating out things like "hey here's how that thing we launched 3, 6, 12 months ago is performing"?