4 Evaluating what makes a good recommendation
This chapter covers
- Evaluation of recommendations
- Definition of metrics
- Splitting datasets
- Offline evaluation
Evaluating recommendations isn't just for competitive data scientists or engineers. The numbers that come out of an evaluation rarely provide an objective answer — they only become meaningful when compared against metrics from other models and systems. This makes evaluation fundamentally a communication tool: a way for engineers and stakeholders to align on whether a change is worth shipping.
Stakeholders don't want to hear about state-of-the-art algorithms from lengthy scientific papers. They want to know whether an improved recommender will attract more loyal users, increase engagement, or boost revenue. These evaluations directly affect strategic decisions — whether to ship a new feature, invest in more AI infrastructure, or stick with what's already working.
Poor evaluation wastes engineering resources on models that don't improve the user experience, or worse, quietly degrade it. Good evaluation helps teams ship effective features confidently and learn quickly from mistakes.
4.1 Why Evaluation is Different for Recommender Systems
In image classification, a picture of a cat is objectively a cat — the ground truth is clear and unchanging. In recommender systems, the "right" recommendation depends on unobservable context that changes from moment to moment and varies across users in ways we can only partially model.