HumachLearnLearn · explore · apply
Start learning
Cleaning & Imputation · Lesson 30

Simple Imputation

Simple Imputation is a data-quality decision, not merely a cleaning command.

ConceptWorked examplePracticeKnowledge check
Textbook walkthrough

What Simple Imputation actually means

Simple Imputation is a data-quality decision, not merely a cleaning command. The correct treatment depends on how the issue arose, whether it carries information, and how the treatment changes the population or downstream model.

Simple Imputation matters because missingness changes both the available sample and the information contained in each feature. Imputation is a modelling decision whose assumptions and validation boundary can affect bias and predictive performance.

Deeper walkthrough

Read Simple Imputation as a mechanism, not a recipe

Treat this as a sequence of observable decisions rather than one opaque command. Stage 1: Measure the problem by column, row group and time/segment. Stage 2: Investigate the data-generating process before choosing a fix. Stage 3: Choose deletion, correction, imputation, transformation or retention with an explicit reason. Final checkpoint: Record an indicator or audit trail when the fact that a value was missing/changed may itself matter.

Mechanism

Follow the transformation

Measure the problem by column, row group and time/segment.

Investigate the data-generating process before choosing a fix.

Choose deletion, correction, imputation, transformation or retention with an explicit reason.

Evidence

Know what would convince you

  • Compare missingness, distributions, row counts and key constraints before and after the change.
  • Inspect representative changed rows and confirm the rule with domain/data documentation.
Useful distinctionDeletion: Removes affected rows/columns; can bias the population.
Visual demonstration of Simple Imputation
Visual demonstration: use the diagram to trace the main objects and state changes involved in Simple Imputation.
Click a stage to inspect what happens, what changes, and what should be checked before moving on.
Stage 1

Measure the problem by column

Measure the problem by column, row group and time/segment. For Simple Imputation, identify the exact state before this stage, the operation or rule applied here, and the observable state afterwards so the mechanism remains inspectable.

State focus: identify exactly what changed at this stage and what observable evidence confirms that change.
How it works

Trace the mechanism step by step

  1. Measure the problem by column, row group and time/segment.
  2. Investigate the data-generating process before choosing a fix.
  3. Choose deletion, correction, imputation, transformation or retention with an explicit reason.
  4. Fit learned preprocessing only on training data when predictive modelling is involved.
  5. Record an indicator or audit trail when the fact that a value was missing/changed may itself matter.
Worked demonstration

Make the concept concrete

Demonstration

Python / pandas example

# Step 1 — Import the module so its functions/classes are available to the rest of this example.
import pandas as pd
# Step 2 — Compute the right-hand expression and store its result in `s` for the next step.
s = pd.Series([10, 11, None, 40])
# Step 3 — Display the current value explicitly so the result/state can be inspected during execution.
print("mean fill:", s.fillna(s.mean()).tolist())
# Step 4 — Display the current value explicitly so the result/state can be inspected during execution.
print("median fill:", s.fillna(s.median()).tolist())
Expected / illustrative result
Mean and median produce different imputations because 40 pulls the mean upward.
Interpret the result.

For Simple Imputation, trace representative source rows/columns into the result and reconcile row counts, dtypes, keys or missing values that the operation could change.

Distinctions & related ideas

Know what this is — and what it is not

DeletionRemoves affected rows/columns; can bias the population.
Simple imputationUses a fixed statistic/category; easy but shrinks variability.
Model-based imputationUses relationships with other variables; more assumptions and leakage risk.
Missing indicatorPreserves information about whether a value was missing.
Use deliberately

When it is appropriate

Use Simple Imputation when it helps diagnose, document or correct a data-quality issue without destroying information needed for the downstream question.

Boundary conditions

When to stop or reconsider

Do not “clean” automatically when the apparent anomaly may carry signal, reflect data collection, or require domain adjudication; preserve an audit trail of changes.

Common mistakes

Failure modes to recognise

  • Treating missing values, outliers or labels as purely technical defects without investigating how they were generated.
  • Applying learned cleaning/imputation using information from validation/test data.
  • Changing values without recording which rows changed and how distributions/counts were affected.
Verification

How to check the result

  • Compare missingness, distributions, row counts and key constraints before and after the change.
  • Inspect representative changed rows and confirm the rule with domain/data documentation.
  • In predictive work, fit learned cleaning only on training data and verify the pipeline reproduces that boundary.
Hands-on practice

Demonstrate understanding

Try this:

Build a tiny, inspectable example of Simple Imputation. First measure the problem by column, row group and time/segment. Then investigate the data-generating process before choosing a fix. Write the expected result before running it, and explain one condition that would make the result misleading or invalid.

Start by measuring the problem, not fixing it. Keep a before/after table of counts or distributions and inspect the exact records affected by the rule.
Knowledge check

Check reasoning, not memorisation

Before trusting a result from Simple Imputation, which check provides the strongest evidence that you understand and applied it correctly?

Quick reference

Keep the important distinctions visible

Step 1Measure the problem by column, row group and time/segment.
Step 2Investigate the data-generating process before choosing a fix.
Step 3Choose deletion, correction, imputation, transformation or retention with an explicit reason.
Step 4Fit learned preprocessing only on training data when predictive modelling is involved.
Lesson summary

What to remember

  • Simple Imputation is a data-quality decision, not merely a cleaning command. The correct treatment depends on how the issue arose, whether it carries information, and how the treatment changes the population or downstream model.
  • Measure the problem by column, row group and time/segment.
  • Treating missing values, outliers or labels as purely technical defects without investigating how they were generated.
  • Compare missingness, distributions, row counts and key constraints before and after the change.