Module 3 Lesson: Counts, Rates, Percentages, and Proportions
Classroom Explanation
A count answers "how many". A rate answers "how many out of how many". Confusing them is the most common numerical error in everyday reporting, and it always favours whoever has the larger denominator.
In this module, the goal is to compare counts only after checking the denominator. 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 saying Basic had the worse support month because it had more tickets. That ignores the much larger number of active accounts. This mistake can make a report sound more confident than the evidence deserves.
Key Ideas
1. A count tells how many events happened.
A count is useful for workload or volume. It answers how many, but it does not automatically answer how common or how risky.
2. A rate or percentage needs a denominator.
A number becomes more useful when you know what it is divided by. Two groups can have different sizes, so a larger count is not always a larger rate.
3. Small counts can move percentages sharply, so sample size matters.
A percentage from a small base can swing sharply when one or two cases change. Always look at both the percentage and the count behind it.
Worked Example
In March, Basic has 54 tickets from 1200 active accounts, while Pro has 36 tickets from 450 active accounts. Basic has more tickets, but Pro has the higher ticket rate.
Here is the dataset used in this module.
| month | plan_type | tickets | active_accounts | escalations |
|---|---|---|---|---|
| January | Basic | 42 | 840 | 5 |
| January | Pro | 28 | 350 | 6 |
| February | Basic | 48 | 960 | 7 |
| February | Pro | 30 | 400 | 4 |
| March | Basic | 54 | 1200 | 8 |
| March | Pro | 36 | 450 | 9 |
Find the denominator first, every time. Then decide which of the count and the rate answers the question actually being asked — sometimes it is the count, because workload depends on absolute numbers rather than proportions.
How To Think Through It
- Identify the numerator and the denominator.
- Compute the rate for each group.
- Ask which figure the decision depends on.
- Check whether a percentage change is hiding a small base.
- Report both, and say which one answers the question.
Common Mistake
The common mistake is saying Basic had the worse support month because it had more tickets. That ignores the much larger number of active accounts.
How To Write The Result
Basic had more tickets in March, but Pro had a higher ticket rate per active account.
Practice Prompt
Calculate ticket rates and escalation rates before writing the comparison.
Takeaway
A number without its denominator is not yet a comparison.
