HumachLearnLearn · explore · apply
Start learning
Reporting & Reproducibility · Lesson 84

Tables That Answer Questions

A reporting table should be designed around a comparison, not around every column that happens to exist.

ConceptWorked examplePracticeKnowledge check
Textbook walkthrough

Tables That Answer Questions

A reporting table should be designed around a comparison, not around every column that happens to exist. Row and column structure should make the unit, measure, denominator, time period and grouping clear; totals and percentages should be internally consistent and sortable without changing meaning.

Learning goal: explain why Tables That Answer Questions behaves this way, apply it to a small example, and verify the result independently. Begin by being able to justify this first step: Write the question the table must answer.

Deeper walkthrough

Read Tables That Answer Questions as a mechanism, not a recipe

Treat this as a sequence of observable decisions rather than one opaque command. Stage 1: Write the question the table must answer. Stage 2: Choose one row grain and only necessary dimensions/measures. Stage 3: Put units in labels and define denominators for percentages/rates. Final checkpoint: Check totals, weighted averages and rounding against source calculations.

Mechanism

Follow the transformation

Write the question the table must answer.

Choose one row grain and only necessary dimensions/measures.

Put units in labels and define denominators for percentages/rates.

Evidence

Know what would convince you

  • Recompute one result from a handful of source rows or an independent formula.
  • Check row counts, group totals and units before interpreting differences.
Useful distinctionDefinition: The exact metric/selection/comparison being computed.
How it works

Trace the mechanism step by step

  1. Write the question the table must answer.
  2. Choose one row grain and only necessary dimensions/measures.
  3. Put units in labels and define denominators for percentages/rates.
  4. Sort or group rows to expose the comparison.
  5. Check totals, weighted averages and rounding against source calculations.
Worked demonstration

Question-driven table

Question: Which region grew most?
Columns: Region | Prior revenue | Current revenue | Growth %
Expected / illustrative result
Every column contributes directly to the comparison instead of reproducing the raw dataset.
Interpret the result.

For Tables That Answer Questions, identify exactly what each reported quantity represents, including its units/denominator, and independently recompute one part of the result.

Distinctions & related ideas

Place the concept correctly

DefinitionThe exact metric/selection/comparison being computed.
EvidenceTable, formula or visual that answers the question.
AuditIndependent count/total/rule check that can reveal an error.
Use deliberately

When it is appropriate

Use Tables That Answer Questions when it answers a defined question in Reporting & Reproducibility and its inputs/assumptions match the current data or program state.

Boundary conditions

When to stop or reconsider

Reconsider Tables That Answer Questions when the required information is unavailable, the operation would violate a validation/data boundary, or a simpler operation answers the question more transparently.

Common mistakes

Failure modes to recognise

  • Changing the population/grain without noticing it.
  • Using an undefined denominator, time window, unit or category rule.
  • Presenting a number/plot without reconciling it to source counts or totals.
Verification

How to check the result

  • Recompute one result from a handful of source rows or an independent formula.
  • Check row counts, group totals and units before interpreting differences.
  • Change one source value and predict which reported value/mark should change.
Hands-on practice

Demonstrate understanding

Try this:

Construct a tiny example of Tables That Answer Questions. First write the question the table must answer. Then choose one row grain and only necessary dimensions/measures. Predict the result before execution and explain one boundary or failure case.

Use a very small example and calculate one quantity manually. Separate sample evidence from population/causal claims.
Knowledge check

Check reasoning, not memorisation

Which approach best demonstrates understanding of Tables That Answer Questions?

Quick reference

Remember the logic

Step 1Write the question the table must answer.
Step 2Choose one row grain and only necessary dimensions/measures.
Step 3Put units in labels and define denominators for percentages/rates.
Step 4Sort or group rows to expose the comparison.
Lesson summary

What to remember

  • A reporting table should be designed around a comparison, not around every column that happens to exist. Row and column structure should make the unit, measure, denominator, time period and grouping clear; totals and percentages should be internally consistent and sortable without changing meaning.
  • Write the question the table must answer.
  • Changing the population/grain without noticing it.
  • Recompute one result from a handful of source rows or an independent formula.