Case Study

Updating Evaluation Criteria When Product Goals Shift

Case context: A data science team is training a model for customer support routing. They choose a validation split and a scoring rule early in the project so they can compare ideas efficiently. After several weeks, they learn that the product will be used in a different workflow than expected, and the current evaluation setup rewards behavior that is no longer the main priority.

Question: How should the team respond to the mismatch between their validation/test setup and the real objective, and what should happen immediately after they decide on the change?

Sample answer: They should revise the validation and test setup, along with the evaluation metric, so that the project is judged against the goal that actually matters. Updating these targets partway through a project is a normal and acceptable step when the original choice stops matching the task. After the change is approved, the whole team should be told about the new evaluation direction.

Key points:

  • Replace the misaligned validation/test setup or evaluation metric.
  • Treat the update as a normal project adjustment.
  • Communicate the new direction to everyone on the team.

Rubric: Grading should verify that the student: 1. Recommends changing the validation/test setup or metric because it no longer matches the goal. 2. Recognizes that this kind of change is a common and reasonable project decision. 3. States that the team must be informed of the updated direction.

0

1

Updated 2026-08-12

Contributors are:

Who are from:

Tags

Machine Learning

Deep Learning

Supervised Learning

Dive into Deep Learning @ D2L

Data Science

Machine Learning Strategy

Machine Learning Yearning @ DeepLearning.AI

Related