News for hackers. Stuff that matters.
Re:You Have Too Many Metrics by sanderjd on Sunday December 18, 2022 @01:40PM (#34041053)
Let me give a concrete example. Say it's a subscription service. Say you track three metrics:

- Revenue. - Subscription renewal / cancellation by monthly cohort. - Signups.

Say the second metric shows that you have a meaningful subscription drop-off after 18 months. By comparing that metric with the signup metric, you might be able to successfully foresee a revenue drop-off months before it materializes in the revenue metric alone, buying valuable time to figure out what to do.

Tracking a revenue metric alone always runs the risk of surprising you in real time when it ticks down and you have no idea why.

Re:You Have Too Many Metrics by marcosdumay on Monday December 19, 2022 @12:52PM (#34055141)
Hum... That metric doesn't tell whether the users are having a good experience.

If that was your point, I misunderstood your comment. Yes, there are metrics that will help you predict problems. My comment wasn't about this.

Re:You Have Too Many Metrics by sanderjd on Monday December 19, 2022 @08:16PM (#34060277)
Ah I see. Yep that other comment I made was uselessly hand-wavy.

The point I was trying to make, starting with my initial comment in the thread, is that there is a middle ground between "we're spending way too much time devising and implementing really fancy fine grained metrics" and "we only look at revenue".

My concrete example makes this point much better, and it seems like we're in agreement, so carry on :)