Module 3 Lesson: Counts, Rates, Percentages, and Proportions

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 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.

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

1. State the question in one sentence.
2. Name the unit of analysis.
3. Identify the outcome and comparison.
4. Check the denominator, sample, uncertainty, or assumption.
5. Write only what the data supports.
6. Add one limit so the result does not overclaim.

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

When a statistical result feels obvious, pause and ask: what exactly was measured, compared, and assumed?