Module 1 Lesson: Statistical Questions and Data Claims
Classroom Explanation
Imagine we are in class and someone puts a small table on the board. The table looks simple, so it is tempting to jump straight to the answer. In statistics, we slow down first. We ask what question the table can answer, what question it cannot answer, and what kind of claim would be safe.
In this module, the goal is to turn a vague topic into a clear statistical question and a careful claim boundary. The important part is not only the calculation. The important part is the thinking before and after the calculation.
Why This Matters
The common mistake is jumping from a pattern to a cause. A comparison can suggest a difference, but it cannot prove why the difference happened unless the study design supports that claim. This mistake can make a report sound more confident than the evidence deserves.
Key Ideas
1. A data question asks what information is available.
This is the inventory question. It asks what columns, rows, records, charts, or measurements we actually have before we decide what they mean.
2. A statistical question asks about a pattern, comparison, relationship, or uncertainty.
This is the evidence question. It asks whether there is a pattern, difference, relationship, or uncertainty that can be checked from data.
3. A decision question asks what action should be taken after the evidence is reviewed.
This is the action question. It asks what someone should do next, but that action should come after the evidence and limits are clear.
Worked Example
A claim says short lessons help students learn better. A safer question asks whether learners using short lessons have higher checkpoint scores in a defined sample.
Here is the dataset used in this module.
| scenario_id | vague_claim | likely_claim_type | safer_question | boundary_note |
|---|---|---|---|---|
| C01 | Students learn better with short lessons | inferential | In this sample do students using short lessons have higher checkpoint scores than students using long lessons? | Can compare groups but cannot prove lesson length caused the difference. |
| C02 | The new button improves signups | causal | In a randomized A/B test did the new button produce a higher signup rate than the old button? | Needs random assignment and practical-size review. |
| C03 | People who study more always score higher | predictive | In this dataset how strongly are study hours associated with score? | Association is not a guarantee for every learner. |
| C04 | The support team was worse in March | descriptive | Did the March support ticket rate per active account increase compared with February? | Counts alone are not enough without active-account denominators. |
| C05 | The training program works for everyone | inferential | Among learners who completed the training what average score change was observed? | Completion bias may make the result too optimistic. |
Read the table slowly. First name the unit. Then name the variables. Then name the comparison or pattern. Only after that should you write the conclusion.
How To Think Through It
- State the question in one sentence.
- Name the unit of analysis.
- Identify the outcome and comparison.
- Check the denominator, sample, uncertainty, or assumption.
- Write only what the data supports.
- Add one limit so the result does not overclaim.
Common Mistake
The common mistake is jumping from a pattern to a cause. A comparison can suggest a difference, but it cannot prove why the difference happened unless the study design supports that claim.
How To Write The Result
In this sample, the short-lesson group had higher checkpoint scores, but this comparison alone does not prove that lesson length caused the difference.
Practice Prompt
Rewrite three vague claims into statistical questions and add one boundary note for each claim.
Takeaway
When a statistical result feels obvious, pause and ask: what exactly was measured, compared, and assumed?