Skip to content
ML Academy

Classical ML, validation, metrics, interpretation, debugging · insight-0166

Plot a learning curve before asking for more data

Evidence type
documented fact
Difficulty
easy
Roles
Data scientist, ML engineer
Industries
cross-industry

Summary: situation, action, reason, boundary

  1. Situation

    Stakeholders ask whether another year of history or more labelling budget will improve the model.

  2. Action

    Plot training and validation scores against training size with the final pipeline; if the gap is open and validation still rising, more data should help; if both have converged low, improve features or model class.

  3. Reason

    The shape of the two curves separates variance problems, which data reduces, from bias problems, which it does not.

  4. Boundary

    Labelling budget decisions, history-length choices and model-capacity choices.

Symptom or risk

Money is spent on data when the model is bias-limited, or on model complexity when it is variance-limited.

Exceptions

For drifting data, older history may hurt; extrapolate learning curves only within a stable period.

Trade-offs

Learning curves need repeated fits; subsample sizes on a log scale to keep cost manageable.

Pitfalls

Building the curve with a random split on temporal data, which hides drift effects.

Lessons and concepts

Claims and their sources