The Computing Series

Real-World Examples

Facebook’s early growth team used a specific activation metric: did a new user add seven friends within ten days? This was not an arbitrary number. Data showed that users who crossed this threshold retained at dramatically higher rates. The metric predicted retention. Everything in the onboarding flow was optimised toward it.

Amazon’s page load time research produced an often-cited finding: every 100 milliseconds of added latency reduced sales by 1%. This is a direct relationship between a technical metric and a lagging business outcome. The finding is real, but it is also specific to Amazon’s scale, user base, and competitive environment. Applying it verbatim to a different product without validation is an example of treating a measurement as a universal law rather than a context-specific proxy.

Google’s HEART framework itself emerged from the recognition that measuring web products only by page views rewarded low-quality, high-volume content. The metric had been gamed. Replacing it with user-centric measures required changing both the measurement infrastructure and the product development process.


Read in the book →