VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Why Mathematics? | Median Polish, Row–Column Effects and Resistant Residuals

Why is mathematics important when a table varies across both rows and columns, and a few cells may be unusual? Median polish repeatedly removes row and column medians, leaving a common level, additive effects and residuals. It is a robust way to expose structure in a multi-factor table.

The method connects medians, subtraction, iteration and model residuals. It also teaches an essential modelling limit: an additive decomposition does not automatically capture interactions.

Did you know? Median polish is called “polish” because each pass removes another layer of row and column pattern from the table until the remaining residual structure changes little.

Full chapter index

Chapters 1–3 · Understand the question
  1. The table question
  2. The NIST model
  3. A worked two-by-three table
Chapters 4–7 · Reproduce the example
  1. Remove row medians
  2. Remove column medians
  3. What the residual pair reveals
  4. Common term and centred effects
Chapters 8–13 · Check assumptions
  1. Iteration
  2. Why medians add resistance
  3. Additivity and interactions
  4. Balanced and unbalanced designs
  5. Raw data versus cell summaries
  6. Missing cells
Chapters 14–18 · Explore applications
  1. Translation invariance
  2. A classroom activity
  3. Spreadsheet workflow
  4. Coding workflow
  5. Residual diagnostics
Chapters 19–26 · Study and verify
  1. Limits and misconceptions
  2. Applications and careers
  3. Connection to recent mathematics articles
  4. Guidance for students and parents
  5. Practice questions
  6. Frequently asked questions
  7. Useful next reading and source checks
  8. Closing perspective

CHAPTER 1 OF 26 · Understand the question

1. The table question

Back to contents

Suppose rows represent laboratories and columns represent methods, times or materials. A cell can be high because its row tends high, its column tends high, both, or because that cell behaves unusually.

Median polish separates these additive components using medians rather than means.

Contents · Next chapter

CHAPTER 2 OF 26 · Understand the question

2. The NIST model

Back to contents

NIST writes data = common value + factor effects + residual. For two factors, this becomes common + row effect + column effect + residual.

Its implementation can extend to one through five factors, but it does not compute interaction terms.

RowColumn 1Column 2Column 3
A101214
B202240
Two-factor teaching table.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 26 · Understand the question

3. A worked two-by-three table

Back to contents

Consider row A: 10, 12, 14 and row B: 20, 22, 40. The final cell is deliberately high relative to the simple additive pattern.

Begin one transparent row-and-column sweep by finding each row median.

QuantityRow ARow B
Row medians1222
Final residuals0, 0, −80, 0, 8
One row-and-column sweep.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 26 · Reproduce the example

4. Remove row medians

Back to contents

Row A has median 12 and becomes −2, 0, 2 after subtraction. Row B has median 22 and becomes −2, 0, 18.

The accumulated row effects are therefore 12 and 22 in this uncentred teaching pass.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 26 · Reproduce the example

5. Remove column medians

Back to contents

The residual column medians are −2, 0 and 10. Subtracting them leaves row A residuals 0, 0, −8 and row B residuals 0, 0, 8.

The additive prediction for A-column3 is 12 + 10 = 22, leaving 14 − 22 = −8. For B-column3 it is 22 + 10 = 32, leaving 40 − 32 = 8.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 26 · Reproduce the example

6. What the residual pair reveals

Back to contents

The third column contains opposite residuals after additive row and column patterns are removed. That suggests a row-by-column interaction or another cell-specific mechanism.

Median polish exposes the pattern; it does not decide its cause.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 26 · Reproduce the example

7. Common term and centred effects

Back to contents

Formal median-polish software repeatedly centres and accumulates effects, often reporting a grand-median common term plus centred row and column effects.

Adding a constant to all row effects and subtracting it from the common term leaves fitted values unchanged. Compare fitted values and residuals, not parameter labels alone.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 26 · Check assumptions

8. Iteration

Back to contents

NIST alternates factor-level medians and subtraction until a residual-change ratio is below a cutoff. Often only a few passes are needed.

The worked table reaches zero row and column medians after the displayed sweep, though the residual interaction remains.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 26 · Check assumptions

9. Why medians add resistance

Back to contents

A mean row effect can be pulled strongly by one large cell. The median row effect depends on the middle order position and is more resistant.

Repeated median removal carries that resistance through the additive decomposition.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 26 · Check assumptions

10. Additivity and interactions

Back to contents

The model assumes row and column effects add. If one row responds differently across columns, residuals can show a patterned interaction.

NIST notes that its median-polish command does not calculate interaction terms. Residual inspection is therefore essential.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 26 · Check assumptions

11. Balanced and unbalanced designs

Back to contents

NIST’s Dataplot median polish can work with balanced or unbalanced designs. The meaning of a cell summary still depends on how many raw observations and what uncertainty lie behind it.

Do not treat a sparse cell mean as equally reliable without review.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 26 · Check assumptions

12. Raw data versus cell summaries

Back to contents

Median polish can use raw data or one summary per cell. If summaries are used, the choice of mean, median or other statistic becomes another modelling decision.

Preserve cell counts and within-cell variability.

Contents · Previous chapter · Next chapter

CHAPTER 13 OF 26 · Check assumptions

13. Missing cells

Back to contents

Missing combinations can complicate interpretation and convergence. A software result should state how missing values were handled.

Do not fill cells with convenient zeros unless zero is a genuine observation.

Contents · Previous chapter · Next chapter

CHAPTER 14 OF 26 · Explore applications

14. Translation invariance

Back to contents

Adding 100 to every cell changes the common term by 100 while leaving row contrasts, column contrasts and residuals unchanged under an equivalent parameterisation.

This is a useful check of the decomposition.

Contents · Previous chapter · Next chapter

CHAPTER 15 OF 26 · Explore applications

15. A classroom activity

Back to contents

Students can write row medians beside the table, subtract them, then write column medians below the residual table. Colour the final ±8 pair.

Ask whether a row effect, column effect or interaction best describes that remaining pattern.

Contents · Previous chapter · Next chapter

CHAPTER 16 OF 26 · Explore applications

16. Spreadsheet workflow

Back to contents

Create a new residual table for every pass. Store row medians, column medians and accumulated effects separately.

Never overwrite the raw table. Stop only under a stated convergence rule.

Contents · Previous chapter · Next chapter

CHAPTER 17 OF 26 · Explore applications

17. Coding workflow

Back to contents

Represent factor levels explicitly, compute medians by level, subtract, accumulate effects and iterate. Return fitted values, residuals, convergence information and cell counts.

Unit-test the teaching sweep to produce final residuals [0,0,−8] and [0,0,8].

Contents · Previous chapter · Next chapter

CHAPTER 18 OF 26 · Explore applications

18. Residual diagnostics

Back to contents

Plot residuals by row and column, inspect large cells and look for structured signs. A residual heatmap can reveal interaction patterns hidden by a single summary.

Residuals are evidence for follow-up, not automatic exclusions.

Contents · Previous chapter · Next chapter

CHAPTER 19 OF 26 · Study and verify

19. Limits and misconceptions

Back to contents

Median polish is not a robust replacement for every ANOVA, does not create causal effects and does not model interactions automatically.

It also cannot rescue confounded factors or non-representative sampling.

Contents · Previous chapter · Next chapter

CHAPTER 20 OF 26 · Study and verify

20. Applications and careers

Back to contents

Median polish is useful in exploratory experiments, interlaboratory tables, agriculture, manufacturing and other multi-factor settings. Similar additive decompositions appear in recommender systems and data normalisation.

The transferable skill is separating main patterns from residual structure.

Contents · Previous chapter · Next chapter

CHAPTER 21 OF 26 · Study and verify

21. Connection to recent mathematics articles

Back to contents

The Mandel h and k guide examines laboratory-level consistency. The Youden-plot guide uses two results to separate persistent and run-specific patterns. Median polish extends robust decomposition across factor tables.

Contents · Previous chapter · Next chapter

CHAPTER 22 OF 26 · Study and verify

22. Guidance for students and parents

Back to contents

Students should narrate each subtraction: what pattern was removed, and what residual remains? This turns a table algorithm into reasoning.

Parents can encourage the habit of checking residuals rather than trusting only fitted effects.

Contents · Previous chapter · Next chapter

CHAPTER 23 OF 26 · Study and verify

23. Practice questions

Back to contents

Perform one sweep on rows [5,7,9] and [15,17,31]. Add 10 to every cell and verify residual invariance. Create a perfectly additive table and show that residuals vanish.

Construct a table with an interaction and explain the residual pattern.

Contents · Previous chapter · Next chapter

CHAPTER 24 OF 26 · Study and verify

24. Frequently asked questions

Back to contents

### Is median polish the same as taking the median of all cells? No. It repeatedly removes factor-level medians and analyses residuals.

### Does it estimate interactions? The cited NIST command does not; interactions can remain as residual patterns.

### Can it handle more than two factors? NIST documents one through five factors, though interpretation becomes more complex.

### Are the effects causal? No. Causality depends on study design and assumptions, not the decomposition alone.

Contents · Previous chapter · Next chapter

CHAPTER 25 OF 26 · Study and verify

25. Useful next reading and source checks

Back to contents

Read the official NIST Dataplot median-polish manual, the NIST exploratory-data handbook and the NIST measures-of-location page. The worked table and uncentred teaching sweep are original and explicitly labelled.

Explore the Mathematics Learning Hub and How Mathematics Works for related foundations.

Contents · Previous chapter · Next chapter

CHAPTER 26 OF 26 · Study and verify

26. Closing perspective

Back to contents

Median polish shows how repeated subtraction can reveal structure. By separating additive row and column patterns from residuals, mathematics helps a student see what a table explains and what it still leaves unanswered.

Contents · Previous chapter · Mathematics Learning Hub

Extended practice laboratory

Practice case 1: Find row medians

Setup: Use the article’s median-polish example and change one declared input for case 1. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 2: Subtract row medians

Setup: Use the article’s median-polish example and change one declared input for case 2. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 3: Find column medians

Setup: Use the article’s median-polish example and change one declared input for case 3. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 4: Subtract column medians

Setup: Use the article’s median-polish example and change one declared input for case 4. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 5: Accumulate row effects

Setup: Use the article’s median-polish example and change one declared input for case 5. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 6: Accumulate column effects

Setup: Use the article’s median-polish example and change one declared input for case 6. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 7: Compute fitted cells

Setup: Use the article’s median-polish example and change one declared input for case 7. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 8: Compute residual cells

Setup: Use the article’s median-polish example and change one declared input for case 8. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 9: Check residual medians

Setup: Use the article’s median-polish example and change one declared input for case 9. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 10: Run another pass

Setup: Use the article’s median-polish example and change one declared input for case 10. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 11: Add a constant

Setup: Use the article’s median-polish example and change one declared input for case 11. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 12: Scale the table

Setup: Use the article’s median-polish example and change one declared input for case 12. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 13: Create an additive table

Setup: Use the article’s median-polish example and change one declared input for case 13. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 14: Create an interaction

Setup: Use the article’s median-polish example and change one declared input for case 14. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 15: Inspect a large residual

Setup: Use the article’s median-polish example and change one declared input for case 15. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 16: Plot residual heatmap

Setup: Use the article’s median-polish example and change one declared input for case 16. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 17: Handle missing cells

Setup: Use the article’s median-polish example and change one declared input for case 17. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 18: Handle unbalanced cells

Setup: Use the article’s median-polish example and change one declared input for case 18. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 19: Preserve cell counts

Setup: Use the article’s median-polish example and change one declared input for case 19. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 20: Compare ANOVA carefully

Setup: Use the article’s median-polish example and change one declared input for case 20. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 21: Audit convergence

Setup: Use the article’s median-polish example and change one declared input for case 21. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 22: Avoid causal claims

Setup: Use the article’s median-polish example and change one declared input for case 22. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 23: Name the model limit

Setup: Use the article’s median-polish example and change one declared input for case 23. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.

Practice case 24: Write a table-decomposition conclusion

Setup: Use the article’s median-polish example and change one declared input for case 24. Task: Recalculate from raw values, preserve units and state which mathematical or design condition changed.

Check: Check the relevant invariant, separate the number from its claim, and name the next diagnostic or source of evidence. Rebuild the relevant counts before interpreting the coefficient, preserve the stated design, and write one sentence separating the numerical result from the claim it can support. Then vary one defensible assumption, calculate again, and explain whether the conclusion changes because of new data, a new reference model, or a new decision purpose. Finish by naming the unit, tolerance, and evidence needed for transfer. Record one graph or table that would expose failure hidden by the summary.