A model can be judged in two ways: how well it predicts, and whether it's worth what it costs. Model performance metrics such as accuracy, precision, recall and F1 score measure the first. Business metrics such as cost per user and return on investment measure the second. The exam asks you to pick the right metric for a scenario, which usually comes down to which mistake is more costly.
Right and Wrong Predictions
Take a model that flags card transactions as fraud. Each prediction lands in one of four boxes, often drawn as a confusion matrix:
- True positive: flagged as fraud, and it really was fraud.
- False positive: flagged as fraud, but it was a genuine purchase (a false alarm).
- False negative: not flagged, but it was fraud (a miss).
- True negative: not flagged, and it was genuine.
Every metric below is a different way of counting these boxes.
Accuracy, Precision and Recall
- Accuracy is the share of all predictions that were right.
- Precision asks: of everything the model flagged, how much was really fraud? High precision means few false alarms.
- Recall asks: of all the real fraud, how much did the model catch? High recall means few misses.
Worked example. Out of 1,000 transactions, 20 are fraud. The model flags 25, and 15 of those are real fraud. Precision is 15 out of 25, which is 60%. Recall is 15 out of 20, which is 75%. Accuracy is 98.5%: 15 caught frauds plus 970 genuine purchases left alone, out of 1,000. But a lazy model that never flags anything would still score 98% accuracy while catching no fraud at all. That's why accuracy misleads when one outcome is rare.
F1 Score
Precision and recall usually pull against each other. Flag more transactions and you catch more fraud (recall rises), but raise more false alarms (precision falls). The F1 score combines both into one number that is only high when both are high. Use it when you need a single figure and both kinds of mistake matter.
Business Metrics
A model with great scores can still be a bad investment. Business metrics connect the model to the goal:
- Cost per user: what it costs to serve each user, including inference and infrastructure.
- Development costs: the people, data and computing time spent building it.
- Customer feedback: whether users find the results helpful, through ratings, complaints or surveys.
- Return on investment (ROI): the value the model creates, such as fraud losses avoided or hours saved, compared with what it costs.
On the Exam
| If the costly mistake is... | Prioritise |
|---|---|
| Missing a real case (disease, fraud, safety defect) | Recall |
| A false alarm (wrongly blocking a customer, spam filter hiding real email) | Precision |
| Both, and you need one number | F1 score |
| Outcomes are balanced and equally costly | Accuracy can be fine |
The classic trap is choosing accuracy for a rare-event problem. If 99% of cases are "normal", a model can be 99% accurate and useless.