AIght_
ToolsCompareLearnUniverseWorkflowsSignalHuman
Take the quiz
← All concepts

Concept

Evaluation Metrics

Accuracy lies. Here's what to measure instead.

Moon·Updated Jun 10, 2026
◈ Learn it interactively8 steps · ~5 min →

Where this idea lives

PREREQUISITESEvaluation MetricsClusteringClustering — Finding structure nobody labelled.Training vs TestingTraining vs Testing — Why you never grade a model on questions it has seen.EvalsEvals — How you measure whether a model is good at the thing you actually care about.Bias in DataBias in Data — Why models inherit the world's blind spots.Common misconception: 99% accuracy means an excellent model.Common misconception: There is one correct metric for a task.
prereqsrelatedtoolsmisconceptions
You might think:99% accuracy means an excellent model.There is one correct metric for a task.

Common misconception

“99% accuracy means an excellent model.”

A disease affects 1% of patients. A "model" that just says healthy to everyone scores 99% accuracy — while missing every single sick person. On imbalanced data, accuracy measures the imbalance, not the model.

The most dangerous number in machine learning is a high accuracy score, because it ends conversations that should be starting.

Accuracy — the fraction of predictions that were right — silently assumes all mistakes cost the same and all categories are common. Both assumptions are usually false. The interesting failures live in which mistakes a model makes, and that takes a slightly richer vocabulary.

The two mistakes, and the two questions

Every yes/no classifier can fail two ways: a false positive (cried wolf — flagged the innocent email) and a false negative (missed the wolf — let the fraud through). These mistakes almost never cost the same. A false positive in spam filtering buries a job offer; a false negative in cancer screening buries a diagnosis.

Two metrics give each mistake its own dial:

  • Precision — of everything the model flagged, how much was really there? (When it cries wolf, is there a wolf?)
  • Recall — of everything really there, how much did the model catch? (How many wolves got past it?)

They fight. Flag more aggressively and recall rises while precision falls. The model's threshold lets you slide between them — which is why "what should we optimize?" is a question about your costs, not your code. The F1 score smooshes both into one number when you must rank models, at the price of hiding the trade-off again.

Beyond the single number

Whatever the metric, the deeper habit is disaggregation: a model that's 95% accurate overall can be 99% on one group and 70% on another — the overall number hides exactly the failures that matter most. (This is how biased models pass review.) Serious evaluation reports performance per slice, not per average.

And for systems with fuzzy outputs — translations, summaries, chat answers — clean metrics run out entirely, and the field reaches for human ratings and model-judging-model schemes. That mess has its own essay: evals.

What to read next

Foundations laid. The deep learning track opens with the object at the center of the modern era: neural networks — layers of simple math that add up to something strange.

◈ Check yourself

You just read it — now see if it stuck. No score, no penalty for a wrong pick.

Question 1 of 3

Why isn't raw accuracy always a good metric?

Question 2 of 3

For a cancer-screening model, which error is usually worse?

Question 3 of 3

Precision and recall pull against each other. Why?

← Prerequisite

Clustering

Next →

Neural Networks

by Moon · poet · engineer · third-year CS, Chandigarh University · Updated Jun 10, 2026

← Back to all conceptsBrowse tools →
beginner
Read time6 min read
UpdatedJun 2026
Sources3

Read next

  1. Training vs Testing →
  2. Evals →
  3. Bias in Data →