We’ve all been there. Metrics behind target, under pressure to fix ASAP. Here’s a framework that should help you get to the bottom of it.
Adapted from Linda Zhang’s article, What to do when your metrics dip, with edits from my own experience.
- Importance: Does this metric even matter?
- Do a gut check of why we decided to track this metric in the first place
- Are we just tracking this metric because the boss made us, even though it doesn’t make sense? Did the boss’s boss assign it to the boss? Is the boss willing to have a true conversation?
- Look back at the business' North Star metric. Does this metric derive from the North Star, or is it irrelevant?
- Even if it doesn't directly contribute to the North Star metric, does it still contribute to some other goal?
- What features were launched recently that may have affected one of these metrics?
- Is the old metric more important than the new feature?
- Should the metric be updated because the new functionality improves the North Star KPI more directly?
- This is a great motivator to track the historical trends of a metric.
- Is this fluctuation normal? Has this ever happened before? Is it linked to seasonality?
- First, what is the equation that is leading to this metric? E.g.:
- Dissect the equation to find out which individual component changed.
# comments = # published articles * # views/article * # comments/view
- For example, in the formula above, see how published articles, views/article, and comments/view changed in the last month
The 5 Whys
- Project goals should be aggressive, but not too aggressive. Does the metric exceed the throughput of our existing processes?
- Will adding more resources increase the output, even if the increase is marginally lower? Is the marginal increase still cost effective?
- Can we create more small projects that will directly chip away at the larger metric?