When validation results stop matching the best product choice
Question: Describe a situation in which the validation set and scoring metric point to one model as best, even though the team believes a different model would serve the product better. What is the clearest warning sign of this problem, and what are the three broad reasons it can happen?
Sample answer: The clearest warning sign is a mismatch between the model favored by the validation metric and the model the team would actually choose for the product. In other words, the numbers say one system is better, but practical judgment says another system is the better fit.
Three common reasons explain this:
- The validation and test data do not reflect the real deployment setting, so the models are being judged on the wrong distribution.
- The team has tuned repeatedly against the validation set, so performance on that set is no longer a reliable guide.
- The metric captures only part of the real goal, so it rewards improvements that do not matter as much for the project.
Key points:
- Warning sign: the evaluation score prefers one model, but the team would deploy a different one.
- Cause 1: the data used for evaluation differs from the data the system will face in practice.
- Cause 2: repeated tuning has made the validation set less trustworthy.
- Cause 3: the metric is not aligned with the true product objective.
Rubric: A correct response must name the mismatch between metric-based ranking and the team’s preferred model as the warning sign, and must list all three causes: data-distribution mismatch, overfitting to the validation set, and a metric that does not fully match the project’s goal.
0
1
Tags
Machine Learning
Deep Learning
Supervised Learning
Dive into Deep Learning @ D2L
Data Science
Machine Learning Strategy
Machine Learning Yearning @ DeepLearning.AI
Related
When Evaluation Data Does Not Match Deployment Data
When Repeated Validation Checks Distort Model Selection
When the Metric Rewards the Wrong Goal
When should your validation setup be revised?
True or False: If your initial validation split or evaluation metric turns out to be poorly chosen, you cannot revise it without abandoning the project.
If your evaluation metric no longer reflects your main objective, what should you change?
What is the clearest sign that your dev/test set or evaluation metric may need revision?
If a validation set or metric turns out to be poorly matched to the real goal, the team should rebuild the whole project before making any changes.
What to revise when the evaluation no longer matches the goal
Match each reason a validation metric can mislead the team to the recommended remedy.
What should a team do when its evaluation setup stops matching its goal?
When Validation Data Does Not Match Deployment Data
After revising your dev/test sets or evaluation metric, updating the project documentation is enough; the team does not need to be told about the new direction.
What should be expanded after repeated tuning to the validation set?
Match each situation to the underlying problem category it illustrates.
Order the reasoning steps for deciding whether to replace an evaluation metric that no longer matches the product goal.
When validation results stop matching the best product choice
When Evaluation Scores and Product Needs Disagree
What should a team do after the development set stops guiding decisions?