Skip to main content
Inferential Statistics for Managers

Hypothesis Testing

📅 Published: 2026-07-06
🎓 Level: postgraduate
👥 Audience: Postgraduate management students studying inferential statistics

Hypothesis Testing

11.1 What Is Hypothesis Testing?

Every time you read "clinically proven," "studies show," or "9 out of 10 dentists recommend," someone made a claim about a whole population after looking at only a handful of data points. How do they get away with that? Hypothesis testing is how.

11.1.1 Definition and Intuition

A hypothesis is a statement or claim about a population — not about a sample, but about the entire group you care about. For example: "The average life of this product is two years." "Smoking causes cancer." "This two-wheeler gives 55 km per litre." These are all hypotheses — general statements that claim something about a whole population.

Hypothesis testing (or testing of hypothesis) is the statistical procedure for validating such claims. You cannot test every unit in a population — that would mean testing every product ever made, or every person who ever smoked. Instead, you take a sample, analyse it, and then infer back to the population. This is why hypothesis testing sits under inferential statistics — you infer about the population from a sample.

Think of it like buying fabric for a suit. The tailor claims the entire roll of cloth is excellent quality. You cannot inspect every inch of the roll. You take a small swatch, test that piece — pull it, feel it, check the weave — and from that one swatch you decide whether the whole roll is good. If the swatch passes, you accept the tailor's claim. That is hypothesis testing in everyday terms.

The swatch is your sample. The roll is your population. The tailor's claim is your hypothesis. Your decision to buy or walk away is the test conclusion.

Where the analogy breaks: in real fabric-testing you might accept the roll if the swatch is good. In hypothesis testing, the logic is flipped — you start by assuming the claim is true (), and you only reject it if the sample evidence is strong enough against it. This is more like "innocent until proven guilty" than "good until proven bad."

11.1.2 Population, Sample, and the Core Logic

The population (size ) is the whole group. The sample (size ) is the part you actually observe. You use the sample to make a decision about the population-level claim.

The flow of every hypothesis test follows the same four-stage logic:

Someone makes a claim about the population. You draw a sample. You compute something from that sample — a mean, a proportion, a test statistic. Then you ask: if the claim were true, how likely is it that I would see a sample like this one? If it is very unlikely, you reject the claim. If it is plausible, you do not reject it.

Scope: Hypothesis testing only works when you have a properly drawn random sample. If your sample is biased — say you only surveyed people who walk past your store — then no amount of statistical wizardry can save your conclusion. The math assumes your sample represents the population. Garbage sample in, garbage decision out.

Assumption: The sample must be drawn from the population about which the claim is made. Testing a claim about "all smartphones" using only iPhone users violates this assumption.

11.1.3 Visual Intuition

Picture a courtroom. The defendant stands accused. The starting assumption — the "null" position — is that the defendant is innocent. The prosecution brings evidence (sample data). The jury asks: "If the defendant were truly innocent, how likely is it that we would see evidence this damning?" If the answer is "very unlikely," the jury rejects the presumption of innocence and convicts. If the evidence is weak, the jury does not reject innocence — which is not the same as declaring the defendant innocent, only that the evidence did not meet the burden of proof.

This courtroom logic is exactly the logic of hypothesis testing. The null hypothesis is "innocent until proven guilty." The sample data is the evidence. The significance level is the standard of proof.

11.1.4 Pitfalls

  • Hypothesis testing does not prove a claim true. "Do not reject " means the evidence was not strong enough to knock it down — not that is definitely true. Absence of evidence is not evidence of absence.
  • A hypothesis is about a population, never a sample. If you say "the average score in my class is 72," that is a sample statistic, not a hypothesis. A hypothesis would be "the average score of all students who ever take this course is 72."
  • Sample size matters enormously. A tiny difference can be "statistically significant" with a huge sample even if it is practically meaningless. Conversely, a large meaningful difference may not reach significance with a tiny sample. Do not confuse statistical significance with practical importance.

11.1.5 Recap and Bridge

Hypothesis testing is the formal machinery for deciding whether sample evidence contradicts a claim about a population. The next question is: what exactly are the two competing claims we set up, and how do we write them down? That is the null and alternative hypothesis pair.

11.1.6 Student Questions and Answers

Q: How do we validate a hypothesis?

A: You cannot test the entire population. You take a sample, compute relevant statistics from it, and then compare those sample results against what the hypothesis predicts. Based on that comparison, you either reject the claim or you do not. The comparison is formalised through a test statistic and a decision rule — the full machinery we build across this lecture.

11.1.7 Real-World & Domain Connection

Hypothesis testing is the backbone of evidence-based decision-making in every quantitative field. Pharmaceutical companies use it to prove a new drug works better than a placebo before the FDA will approve it. Manufacturing plants use it to decide whether a production batch meets quality specifications. Political pollsters use it to determine whether a candidate truly leads or the gap is just sampling noise. In machine learning, A/B testing — comparing two model versions on live traffic — is hypothesis testing in disguise. Mastering this framework means you can separate signal from noise in any data-driven claim you encounter.

11.2 Null and Alternative Hypotheses

You are a quality-control engineer. A cereal box says "500 g." You pull 30 boxes off the line and find they average 497 g. Is the company lying, or is this just random variation? To answer that, you need two competing statements: one that says "everything is fine" and one that says "something is wrong." Those are the null and alternative hypotheses.

11.2.1 Definition

Every hypothesis test involves two competing statements:

  • Null hypothesis (): The statement you set out to test. It represents the status quo, the existing belief, or the claim being validated. It must contain an equality sign (, , or ). The word "null" means "no effect, no difference, no change" — it is the boring, default position.
  • Alternative hypothesis ( or ): The complement of . If the data forces you to reject , then is what you conclude instead. This is often what the researcher wants to prove — the "exciting" result. and are mutually exclusive — they cannot both be true.

For example, if you are testing whether the average life of a product equals two years:

The null hypothesis always gets the benefit of the doubt. Think of it as the defendant in a criminal trial — innocent until proven guilty. You only reject when the sample evidence against it is overwhelming. The alternative hypothesis is what you conclude when the evidence crosses that threshold.

This asymmetry is by design. It is safer to stick with the status quo unless the data screams otherwise. In scientific research, is often called the "researcher's hypothesis" — it is the claim the researcher hopes to validate, but must earn through strong evidence.

Analogy — The smoke detector. Your smoke detector has a null hypothesis: "There is no fire." The alternative is "There is a fire." The detector stays silent (does not reject ) most of the time. It only alarms (rejects ) when the smoke evidence is strong enough. You would rather it stay silent during a small fire (Type II error) than scream during your cooking (Type I error) — the cost of false alarms shapes where you set the threshold.

11.2.2 The Equal-to-Sign Rule — Why Must Contain Equality

This is a critical practical rule. When you compute a test statistic like , you substitute with the value from . This substitution is only justified if contains an equality sign.

The term (called the null value) must be a specific number. If were strictly (no equality), you would have no specific number to plug in for . The test statistic formula simply would not work.

Therefore, always ensure is written with , , or . This sometimes means swapping the natural reading of the problem statement. The worked example on light bulb life (Section 11.10) demonstrates this swap in detail.

The hypothesis swap rule: When the natural claim uses a strict inequality ( or ), swap the pair so gets the equality-containing form ( or ) and the strict inequality becomes . Then interpret the conclusion back in terms of the original claim at the end.

Example — A manufacturer claims mean life is less than 750 hours. Natural reading: claim is . But needs equality, so you swap:

  • (now contains — works in the formula)
  • (the manufacturer's claim becomes )

The test result is then mapped back: if you reject , you support the manufacturer's claim. If you do not reject , the claim is not supported.

11.2.3 Three Standard Forms for Comparing Two Means

When comparing two population means ( and ), there are three standard hypothesis pairs:

CaseTest Type
1Left-tailed
2Right-tailed
3Two-tailed

You do not pick arbitrarily. The problem statement dictates which pair applies. The alternative hypothesis determines whether the test is one-tailed (left or right) or two-tailed.

The null hypothesis for two-population tests is almost always (no difference). The alternative expresses the direction of the difference you are testing for:

  • "Is A worse than B?" → (left-tailed)
  • "Is A better than B?" → (right-tailed)
  • "Are A and B different?" → (two-tailed)

11.2.4 Visual Intuition

Imagine a balance scale. says the scale is perfectly balanced — the two sides weigh the same (). Your sample data is a small weight you place on the scale. A one-tailed test asks: "Did the scale tip in this specific direction far enough that it cannot be chance?" A two-tailed test asks: "Did the scale tip in either direction far enough?" The rejection region is how far the scale must tip before you declare it genuinely unbalanced.

11.2.5 Pitfalls

  • Writing without an equality sign is the most common beginner mistake. If your is , stop — you cannot plug that into any formula. Rewrite it as and make the .
  • Swapping and mid-problem. Set them once at the start and stick with them. The test type, critical value, and conclusion all cascade from this choice.
  • Confusing the claim with . The claim in the problem is not automatically . The claim goes into only if it contains an equality sign. Otherwise, it becomes after the swap.
  • Forgetting that and must be mutually exclusive and exhaustive. They must cover all possibilities between them. The pair and is fine because together they cover all possible values of . What the problem asks you to decide between determines the pair, even if it does not exhaust all logical possibilities. The test is designed to discriminate between those two specific statements.

11.2.6 Recap and Bridge

is the status quo with an equality sign. is what you conclude when evidence overthrows . When the natural claim is a strict inequality, swap the pair so gets the equality. The form of then dictates whether the test is left-tailed, right-tailed, or two-tailed.

11.2.7 Student Questions and Answers

Several students asked essentially the same question:

Q: Why does determine the tail direction and not ? Why not use the null hypothesis directly?

A: The rejection region is built around evidence against . The alternative hypothesis tells you what kind of evidence you are looking for. If says , you care about sample means far above 920 — so the rejection region sits in the right tail. If says , you care about sample means far below 750 — rejection region in the left tail. If says , evidence in either direction matters — rejection region split across both tails.

The null hypothesis alone () does not tell you which direction to look — it only gives you the centre. provides the direction. For a deeper justification: the test is designed to maximise power (the probability of correctly rejecting ) in the direction of , which is why the rejection region aligns with .

11.2.8 Real-World & Domain Connection

The null/alternative framework underpins every regulatory decision you have ever benefited from. The FDA requires drug trials to test : "new drug = placebo" against : "new drug > placebo." Only when is rejected at (or stricter) does a drug reach the market. Environmental agencies test : "emissions ≤ legal limit" against : "emissions > legal limit." The burden of proof always sits on the alternative — you must prove something is wrong, not assume it. This conservative design protects consumers, patients, and the environment from false alarms and from reckless claims alike.

11.3 Parametric vs Non-Parametric Tests

"If you know the shape of the data, use a parametric test. If you do not, use a non-parametric test." That is the one-line rule. But why does knowing the shape matter, and what do you lose when you do not?

11.3.1 Definition

Tests fall into two broad categories:

  • Parametric tests: The hypothesis involves a parameter of the population — typically the mean () or proportion (). You also know (or assume) the population follows a specific distribution, usually the normal distribution. The name comes from the fact that you are testing a parameter of a known distributional form. Examples: Z-test, T-test, ANOVA (F-test).
  • Non-parametric tests: The hypothesis is a general statement, not tied to a specific parameter like the mean. Or you have no knowledge of the population's distribution. These tests make fewer assumptions and are sometimes called "distribution-free" tests. Examples: Chi-square test, Mann-Whitney U test, Kruskal-Wallis test.

A statement like "average life = 2 years" involves — it is parametric because is a parameter of the normal distribution you are assuming. A statement like "smoking causes cancer" involves no specific parameter — it is a general association claim, best tested with a non-parametric method like Chi-square.

The trade-off: parametric tests are more powerful (more likely to detect a real effect) when their assumptions hold. Non-parametric tests are more robust (less likely to give wrong answers) when assumptions are violated. You pay for robustness with slightly lower power.

11.3.2 Tests Covered

CategoryTestUsed ForAssumes
ParametricZ-testLarge samples ()Normality (or large via CLT)
ParametricT-testSmall samples ()Normality of population
ParametricANOVA (F-test)Several means (3+ populations)Normality, equal variances
Non-parametricChi-square ()Several proportions / independenceLarge enough expected frequencies

Analogy — The tailored suit vs the one-size-fits-all. A parametric test is like a tailored suit: it fits perfectly if your measurements (assumptions) are right, and it looks sharp. A non-parametric test is like an adjustable one-size-fits-all garment: it works on almost any body shape, but it will never look quite as sharp as a well-tailored suit on the right person. If you know your distribution is normal, use the parametric test — you get more statistical power. If you are unsure, the non-parametric test is the safer choice.

11.3.3 Visual Intuition

Draw two distributions side by side. On the left, a clean bell-shaped normal curve — this is the world where parametric tests thrive. Every parametric formula (Z, T, F) was derived assuming data looks roughly like this. On the right, a jagged, skewed, multi-modal mess — real-world data often looks more like this. Non-parametric tests work here because they do not assume any particular shape. They rely on ranks, counts, and order statistics instead of means and variances.

11.3.4 Pitfalls

  • Using a parametric test when the normality assumption is violated with a small sample. The Central Limit Theorem rescues you for large , but for you genuinely need near-normal data for Z/T tests to be valid.
  • Assuming "non-parametric" means "no assumptions." Non-parametric tests still have assumptions — they are just weaker. The Chi-square test, for example, assumes observations are independent and expected frequencies are not too small.
  • Confusing "proportion tests" as non-parametric. A test about a proportion is parametric — is a parameter of the binomial distribution. The Chi-square test for several proportions is non-parametric because it tests a general association, not a specific parameter value.

11.3.5 Recap and Bridge

Parametric = you know the distribution and are testing a parameter (mean, proportion). Non-parametric = you make minimal distributional assumptions. The decision tree in Section 11.8 will show you exactly when to use which. Next: once you pick a test, you need to know whether to look at one tail or both.

11.3.6 Real-World & Domain Connection

In clinical trials, the choice between parametric and non-parametric can affect whether a drug gets approved. A t-test might show significance where a Mann-Whitney test does not, or vice versa. Regulatory agencies like the FDA often require both as a sensitivity check. In data science, non-parametric methods like bootstrap confidence intervals have become popular precisely because they do not assume normality — they let the data speak for itself. The rise of computing power has made non-parametric methods practical for datasets where, fifty years ago, you would have been forced to assume normality just to get a closed-form answer.

11.4 One-Tailed vs Two-Tailed Tests

A two-tailed test is like asking "Is this coin fair?" — you would be surprised by too many heads OR too many tails. A one-tailed test is like asking "Is this coin biased toward heads?" — only too many heads would surprise you. The difference is not just academic; it changes your critical value from 1.96 to 1.645, which can flip your conclusion.

11.4.1 Definition

The alternative hypothesis determines the tail structure:

  • Two-tailed test: uses . The rejection region is split equally across both tails. Example: . If the sample mean is far above 3 OR far below 3, you reject .
  • One-tailed test: uses or . The entire rejection region sits in one tail.
    • Right-tailed: uses . Rejection region in the right tail. You only reject if the sample statistic is far above the null value.
    • Left-tailed: uses . Rejection region in the left tail. You only reject if the sample statistic is far below the null value.

The total rejection area always equals . In a one-tailed test, all goes into one tail. In a two-tailed test, is split: in each tail. This is why, for the same , the one-tailed critical value is 1.645 while the two-tailed critical value is 1.96 — the two-tailed test needs a more extreme value to achieve the same tail probability because the area is halved.

11.4.2 Visual Interpretation

For a right-tailed test at , the rightmost 5% of the normal curve is the rejection region. The remaining 95% is the acceptance region. The boundary Z-value separates them.

For a two-tailed test at , each tail gets . The boundaries are .

Analogy — The suspicious coin. You suspect a coin is biased toward heads. You flip it 100 times and get 58 heads. Under a two-tailed test (, ), you ask: "Is 58 heads far enough from 50 in either direction to be suspicious?" The critical value is — 58 heads corresponds to , so you do not reject. The coin seems fair.

Now suppose you specified before flipping that you only care about heads-bias. Under a one-tailed test (, ), you ask: "Is 58 heads far enough above 50?" The critical value is 1.645 — and , so you still do not reject. But you got closer. With 60 heads (), the one-tailed test would reject while the two-tailed would not. The moral: one-tailed tests are more powerful for detecting effects in the specified direction, but they are blind to effects in the opposite direction. Choose carefully — and choose before seeing the data.

11.4.3 Common Z Critical Values

These are the most-used values — worth memorising:

ConfidenceRight-tailedLeft-tailedTwo-tailed
0.1090%+1.645−1.645±1.645
0.0595%+1.645−1.645±1.96
0.0199%+2.33−2.33±2.58

Notice a pattern: the two-tailed critical value at equals the one-tailed critical value at . For example, the two-tailed 0.05 value () equals the one-tailed 0.025 value. This is because the two-tailed test splits between both tails.

For a left-tailed test, simply take the negative of the right-tailed value: at , left-tailed critical value is . The normal curve is symmetric, so the left-tail critical value is the mirror image.

11.4.4 Pitfalls

  • Choosing one-tailed after seeing the data. This is statistical cheating. If you see the sample mean is higher and then decide to run a right-tailed test, you have doubled your effective . The tail direction must be chosen based on the research question, not the data.
  • Using a one-tailed test when the effect could go either way. If a new drug could plausibly make patients worse, a two-tailed test is appropriate — you need to detect harm as well as benefit. One-tailed tests are only justified when effects in the opposite direction are either impossible or irrelevant.
  • Forgetting that the critical Z for two-tailed 0.05 is 1.96, not 1.645. This single swap is the most common arithmetic error on exams. 1.645 = one-tailed; 1.96 = two-tailed.
  • Confusing the 0.10 two-tailed value with the 0.05 one-tailed value. Both are ±1.645, but they mean different things. 0.10 two-tailed means 5% in each tail. 0.05 one-tailed means 5% in one tail. Same number, different , different interpretation.

11.4.5 Recap and Bridge

One-tailed = all in one direction, critical value 1.645 at . Two-tailed = in each direction, critical value 1.96 at . dictates which you use, and you must decide before looking at the data. Next: what are the two ways your decision can be wrong?

11.4.6 Real-World & Domain Connection

One-tailed tests are common in quality control and regulatory compliance: "Is the impurity level above the legal limit?" — you only care about one direction. Two-tailed tests dominate academic research: "Does this intervention have any effect?" — you must be open to surprise in either direction. The choice has real consequences: in 2020, several COVID-19 treatment trials used one-tailed tests to maximise the chance of detecting a benefit, prompting debate about whether potential harm was adequately monitored. The statistical choice encodes a value judgment about which errors you are willing to tolerate.

11.5 Type I and Type II Errors

Every time you make a decision under uncertainty, you risk being wrong in two different ways: seeing a pattern that is not there, or missing one that is. Statisticians call these Type I and Type II errors. The entire machinery of hypothesis testing is built around managing this trade-off.

11.5.1 The Four Possibilities

When you make a decision about , there are four possible outcomes:

is actually True is actually False
Do not reject Correct decision ✓Type II Error ()
Reject Type I Error ()Correct decision ✓
  • Type I Error (): Rejecting when it is actually true. A false positive — you cry wolf when there is no wolf. The probability of this error is , the significance level, which YOU choose.
  • Type II Error (): Failing to reject when it is actually false. A false negative — the wolf is there but you stay silent. The probability is , which depends on the true effect size, sample size, and .

Power (): The probability of correctly rejecting a false . A test with high power is good at detecting real effects. Power increases with larger sample sizes and larger true effects.

Analogy — The fire alarm. Your building's fire alarm has two failure modes. Type I error: the alarm goes off when there is no fire (false positive). You evacuate for nothing — annoying and costly, but everyone is safe. Type II error: there IS a fire but the alarm stays silent (false negative). Catastrophic. Which error is worse depends on context, which is why you tune the alarm's sensitivity — that is .

11.5.2 Which Error Is More Critical?

Type I error (rejecting a true ) is generally considered more serious in the hypothesis testing framework. The professor gave two powerful analogies:

The grading analogy: A student writes a correct answer (so : "answer is correct" is true). The faculty member marks it wrong and gives zero marks (rejects ). This is a Type I error. The consequence: the student may fail, lose a job offer, or delay graduation. Compare this with the reverse — a wrong answer marked correct (Type II error). That reflects poorly on the faculty member but has less devastating consequences for the student. Type I hurts the student more.

The medical diagnosis analogy: A patient has chest pain that is actually a heart attack (: "patient has heart disease" is true). The doctor dismisses it as gastric trouble (rejects ). This is a Type I error — the true condition is missed. The patient goes home, ignores the symptoms, and the next episode is critical. Compare with the reverse: the patient's chest pain is NOT a heart attack, but the doctor says it is and recommends surgery (Type II error). Both are bad, but the first can be fatal.

Notation note: In standard medical statistics, the null hypothesis is usually "patient does NOT have the disease" (the conservative assumption). Under that convention, missing a real disease is a Type II error, not Type I. The professor's framing above uses : "patient has heart disease" to make the pedagogical point about Type I being more serious. On exams, follow the professor's convention as stated in the problem. In practice, always check which direction points before assigning error types.

11.5.3 Why Focus on Type I Error?

In hypothesis testing, the primary focus is on controlling Type I error. The probability of Type I error is , the level of significance — and you get to choose it. You set the bar for how much false-positive risk you are willing to tolerate before you declare a finding "significant."

Type II error (probability ) is also important — it tells you how sensitive your test is — but it is not the primary decision-making tool in introductory hypothesis testing. The reason is practical: is a single number you control directly, while depends on the unknown true effect size. You can always reduce by increasing the sample size, but you must fix before the test.

11.5.4 Visual Intuition

Draw two overlapping normal curves side by side. The left curve is the sampling distribution of the test statistic when is true (centred at the null value). The right curve is the distribution when is true (centred at some true effect). The vertical line is your critical value — the decision boundary.

The area under the curve to the right of the critical value is (Type I error region). The area under the curve to the left of the critical value is (Type II error region). As you slide the critical value to the right, shrinks but grows — this is the fundamental trade-off. You cannot reduce both simultaneously without increasing the sample size, which narrows both curves.

11.5.5 Pitfalls

  • Confusing which error is which. Mnemonic: Type I = "I see something that Is not there" (false positive). Type II = "II blind to see it" (false negative). Or: Type I = you convict an Innocent person. Type II = you let a guilty person go free.
  • Thinking that not rejecting proves true. It might just mean your sample was too small ( was high). A non-significant result is not proof of no effect — it is a failure to detect one.
  • Treating Type I and Type II as equally important in all contexts. In a safety inspection of an aircraft engine, a Type II error (missing a crack) could kill hundreds. The acceptable and depend entirely on the cost of each error in the specific domain.
  • Forgetting that and are probabilities, not certainties. Setting does not mean you will make a Type I error exactly 5% of the time across a small number of tests. It is a long-run frequency statement.

11.5.6 Recap and Bridge

Type I = false positive (reject true ), controlled by . Type II = false negative (fail to reject false ), measured by . The framework prioritises controlling Type I error because we prefer to stick with the status quo unless evidence is overwhelming. Next: has a formal name — the level of significance.

11.5.7 Real-World & Domain Connection

The Type I / Type II trade-off shapes legal systems, not just statistics. "Innocent until proven guilty" means the legal system sets very low — it would rather let guilty people go free (Type II) than convict the innocent (Type I). In contrast, airport security screening sets very low — it would rather pat down innocent passengers (Type I) than let a weapon through (Type II). Every decision system that operates under uncertainty implicitly chooses its tolerance for these two errors. Hypothesis testing makes that choice explicit and quantifiable.

11.6 Level of Significance and Confidence Level

You are about to reject a claim that has stood for years. Before you pull the trigger, you need to answer one question: what probability of being wrong are you willing to accept? That probability is .

11.6.1 Definition

  • Level of significance (): The probability of making a Type I error — rejecting when it is actually true. It is your self-imposed tolerance for false positives. You choose before seeing the data.
  • Confidence level (): The probability of NOT making a Type I error when is true. It quantifies how sure you are that your rejection is correct.

Common pairings:

Confidence LevelMeaning
90%0.101 in 10 chance of false rejection
95%0.051 in 20 chance of false rejection
99%0.011 in 100 chance of false rejection

So means: "If were true and I ran this experiment 100 times, I would wrongly reject about 5 times." Or equivalently: "I am 95% confident that my rejection is not a false alarm."

11.6.2 Where Comes From

The problem statement typically gives explicitly — "test at 5% level of significance" means . If not specified, common practice uses .

Analogy — Setting the thermostat. Your air conditioner has a tolerance band. If you set it to 72°F, the AC kicks in when the room hits 73°F and stops at 71°F. That ±1°F band is your — how much deviation you tolerate before taking action. A narrower band (smaller ) means you react to smaller deviations, but you also react more often to random fluctuations. A wider band (larger ) means you react less often, but you might miss a genuine temperature rise. There is no objectively correct setting — it depends on how much you hate being slightly warm versus how much you hate the AC cycling on and off.

11.6.3 Why 0.05?

The convention of traces back to R.A. Fisher in the 1920s, who suggested that a 1-in-20 chance was a reasonable threshold for "significant" evidence. It is not a mathematical truth — it is a cultural convention that stuck. Some fields (physics, genomics) now use much smaller thresholds ( or even for genome-wide significance) because they run millions of tests and need to control the overall false-positive rate. The key insight: is a choice, not a law of nature. Pick the value that matches the cost of being wrong in your domain.

11.6.4 Pitfalls

  • Treating as a magic number. A result with is not meaningfully different from one with . The 0.05 threshold is a convention, not a cliff. In practice, report the exact p-value and let readers judge.
  • Confusing confidence level with the probability that is true. "95% confidence" does NOT mean "there is a 95% chance is false." It means: "if were true, there is a 95% chance I would correctly not reject it." These are fundamentally different statements — the first is about the hypothesis, the second is about the procedure.
  • Choosing after seeing the data. If you get and then decide to use instead of 0.05, you are effectively inflating your Type I error rate. Set before the test.

11.6.5 Recap and Bridge

is the probability of a false positive — your tolerance for wrongly rejecting . is your confidence level. The standard default is , but this is a choice, not a mathematical necessity. Now that you have , the next step is to walk through the full six-step testing procedure.

11.6.6 Real-World & Domain Connection

Different industries set differently because their error costs differ. Pharmaceutical trials typically use for primary endpoints. Manufacturing quality control often uses (or even Six Sigma's 3.4 defects per million, which corresponds to a very tiny ). Algorithmic trading systems may use to avoid acting on spurious patterns that would lose money. The choice of is not a statistics question — it is a business decision about risk tolerance, dressed in mathematical clothing.

11.7 The Hypothesis Testing Procedure

There is a six-step recipe that turns any word problem into a statistical decision. Master this recipe and every hypothesis testing problem becomes a fill-in-the-blanks exercise. Here it is.

11.7.1 Purpose

The six-step procedure standardises every hypothesis test into a repeatable workflow. It separates the conceptual work (steps 1–4: what are we testing and what is our rule?) from the computational work (step 5: plug in numbers) from the interpretive work (step 6: what does it mean?). Following these steps in order prevents the most common errors: wrong hypothesis direction, wrong critical value, wrong conclusion language.

11.7.2 Inputs & Outputs

Inputs: A problem statement containing a claim about a population parameter, sample statistics (, , , ), and a significance level .

Outputs: A binary decision — either "reject " or "do not reject " — along with the computed test statistic that justifies it.

11.7.3 The Six Steps

Step 1 — Set up : Identify the null hypothesis from the problem. Ensure it contains an equality sign (, , or ). This is the status quo claim you are testing against.

Step 2 — Set up : Write the complementary alternative hypothesis. These two must be mutually exclusive. The form of (, , or ) determines whether the test is left-tailed, right-tailed, or two-tailed.

Step 3 — Choose : Take the level of significance from the problem (e.g., "test at 5%" means ). If not specified, default to . This is your tolerance for Type I error.

Step 4 — Determine decision criteria (critical region): Based on three inputs — (a) one-tailed or two-tailed from , (b) , and (c) Z-test vs T-test — find the critical value(s) from the appropriate table. This defines exactly when you reject . For example: at , right-tailed Z-test, reject if .

Step 5 — Compute the test statistic: Plug the sample data into the appropriate formula to get (or ). Use the decision tree (Section 11.8) to pick the right formula.

Step 6 — Compare and conclude: Does the computed statistic fall in the rejection region? If yes, reject . If no, do not reject . State the conclusion in plain language that answers the original question.

11.7.4 Trace — Sodium Example (Preview)

Apply the six steps to the sodium content problem (fully worked in Section 11.9):

Step 1: (restaurant's claim: sodium ≤ 920 mg)
Step 2: (sodium is more than claimed) → right-tailed
Step 3:
Step 4: Reject if
Step 5:
Step 6: → Reject . The restaurant's claim is not supported.

Notice that each step feeds directly into the next. Step 2 determines the tail. Step 4 uses the tail and to set the threshold. Step 5 computes a number. Step 6 compares the number to the threshold. The logic chain never breaks.

11.7.5 Decision Criteria / Critical Region in Detail

The decision criteria (or critical region) is the rule that tells you when to reject . It depends on three things:

  • Whether the test is one-tailed or two-tailed (from )
  • The level of significance
  • Whether you are using Z or T

For example: at , right-tailed Z-test, the decision criteria is: reject if . This is because the rightmost 5% of the standard normal curve begins at .

The entire normal curve together with this boundary forms the decision framework. If your computed Z falls in the shaded tail, you reject. If it falls in the unshaded body, you do not reject.

The critical region is defined BEFORE you compute the test statistic. This is crucial — otherwise you could adjust the boundary to get the answer you want, which would invalidate the -level guarantee. In practice: write down your decision rule in step 4, THEN compute in step 5, THEN compare in step 6. Never reorder.

11.7.6 The "Do Not Reject" Language

Pure statisticians do not say "accept ." They say "do not reject " or "there is not enough evidence to reject ." This is a precise phrasing that reflects an important philosophical point: failing to find evidence against is not the same as proving true.

Analogy — "Not guilty" vs "Innocent." A court does not declare a defendant "innocent." It returns a verdict of "not guilty" — meaning the prosecution did not meet the burden of proof. The defendant might actually be innocent, or the evidence might simply have been too weak. "Do not reject " is the statistical equivalent of "not guilty." It means the data did not provide enough evidence to overturn the status quo.

For practical problem-solving, "do not reject " = "accept " = " stands." The distinction matters philosophically, but operationally the decision is the same: you continue to treat as true until stronger evidence arrives.

11.7.7 Pitfalls

  • Skipping steps. Students often jump straight to computing the test statistic without writing and first. This leads to wrong-tailed tests and wrong critical values. Write all six steps, in order, every time.
  • Computing the test statistic before determining the critical region. If you see your Z = 2.0 and THEN look up the critical value, you have already biased your interpretation. Step 4 before Step 5, always.
  • Writing "accept " when you mean "do not reject ." On exams, the professor will accept either phrasing, but "do not reject" is technically more correct. When in doubt, use the professor's language from the lecture.
  • Forgetting to state the conclusion in plain English. "Reject " is not a conclusion. "The evidence suggests the mean sodium content exceeds 920 mg" is a conclusion. Always answer the original question.

11.7.8 Recap and Bridge

Six steps: → critical region → compute statistic → compare and conclude. The procedure is mechanical, but choosing the right test in step 5 requires the decision tree. That is coming next.

11.7.9 Real-World & Domain Connection

This six-step procedure is not just an academic exercise — it is the template used by regulatory agencies worldwide. When the FDA reviews a new drug application, the statistical analysis plan must pre-specify , , , the test statistic, and the critical region before any data is unblinded. Deviating from this order is considered scientific misconduct. The procedure exists to prevent analysts from subconsciously (or consciously) tuning their method to get a desired result — a phenomenon called "p-hacking" that has contributed to the replication crisis in psychology, medicine, and economics.

11.8 The Complete Decision Tree for Choosing a Test

The professor put it best: if you understand this one flow chart, you can solve virtually any hypothesis testing problem. Every problem in this course traces a single path through this tree. Your job is to learn to trace it.

11.8.1 Purpose

The decision tree answers the single most common confusion in hypothesis testing: "Which formula do I use?" Instead of memorising a dozen disconnected formulas, you learn one branching logic. Given a problem statement, the tree tells you the correct test, the correct formula, and whether to use Z or T — all from the words in the problem.

11.8.2 The Master Flow Chart

Testing of Hypothesis
├── MEAN (discussion involves average/mean/μ)
│   ├── One Mean (one population)
│   │   ├── Large sample (n ≥ 30) → Z-test
│   │   └── Small sample (n < 30) → T-test
│   ├── Two Means (comparing two populations)
│   │   ├── Large sample (n₁ + n₂ - 2 ≥ 30) → Z-test
│   │   └── Small sample (n₁ + n₂ - 2 < 30) → T-test
│   └── Several Means (3+ populations) → ANOVA (F-test)
│
└── PROPORTION (discussion involves percentages, fractions, rates — no mean)
    ├── One Proportion
    │   ├── Large sample → Z-test
    │   └── Small sample → T-test (rare in practice)
    ├── Two Proportions → Z-test (large sample formula)
    └── Several Proportions → Chi-square (χ²) test

11.8.3 How to Trace the Tree

Read the problem statement. Ask four questions, in order:

  1. Does it talk about a mean/average? → Go down the MEAN branch. Does it talk about percentages, rates, fractions? → Go down the PROPORTION branch. This is the first fork — and the most important one. "Average," "mean," "μ" → MEAN. "Rate," "percentage," "proportion," "fraction" → PROPORTION.
  2. One population or two (or more)? → Determines the sub-branch. "A company claims its product..." → one population. "Compare Brand A and Brand B..." → two populations. "Compare three teaching methods..." → several populations.
  3. What is the sample size? → Large (Z-test) or small (T-test). For one mean, use as the threshold. For two means, use the combined rule (see below).
  4. Look up the formula. → Once you know the branch, the formula is fixed. The formula reference table (Section 11.8.5) gives you the exact equation.

11.8.4 The Two-Means Sample Size Rule

For two means, do NOT judge each sample individually. Instead, compute:

If , treat as large sample (Z-test). If , treat as small sample (T-test).

Example 1: , → large sample → Z-test. Even though each individual sample is only 20, the combined degrees of freedom cross the threshold.

Example 2: , → large sample → Z-test. One sample being small does not automatically make it a small-sample test.

Example 3: , → small sample → T-test.

The rationale: when you pool two samples, you are estimating two means. You lose one degree of freedom for each mean estimated — hence . The combined degrees of freedom determine how much uncertainty remains, which drives whether the normal approximation (Z) is good enough or you need the heavier tails of the T-distribution.

11.8.5 Formula Reference for Z-Tests

SituationFormulaNotes
One mean (σ known)Exact if population is normal
One mean (σ unknown, use s)Valid for large n via CLT
Two means (variances known)Denominator is the SE of the difference
Two means (variances unknown)Use sample variances
One proportion, Uses from , not , in the denominator

Critical note: When states , the term and drops out of the numerator. You are testing whether the observed difference is far enough from zero to reject the null. If the problem stated a specific non-zero difference (e.g., "test whether exceeds by at least 5 units"), you would use that value instead of zero.

Also, for the proportion test, the denominator uses the null-hypothesis proportion , NOT the sample proportion . This is a deliberate choice: under , the standard error of is , not . Using the null value keeps the test statistic's distribution tied to .

11.8.6 T-Distribution vs Z-Distribution

The T-distribution is also bell-shaped and symmetric, but slightly flatter (more spread out) than the normal distribution. It accounts for the extra uncertainty when is small and you must estimate with .

The T-distribution depends on degrees of freedom (df). For a one-sample T-test, . For a two-sample T-test, .

As df increases, the T-distribution approaches the Z-distribution. At , the difference is negligible for most practical purposes — which is why is the Z-test threshold. At , T and Z are identical.

11.8.7 Pitfalls

  • Forgetting the first fork. The most expensive mistake: using a mean formula for a proportion problem, or vice versa. Scan for the word "average" (→ MEAN) or "rate/percentage" (→ PROPORTION) before anything else.
  • Judging two-means sample size individually. Two samples of size 15 each → each is "small," but → T-test. You must compute , not look at each separately.
  • Using instead of in the denominator of the proportion Z-test. The formula is , not . Under , the null proportion is the assumed truth, so the standard error is computed under that assumption.
  • Assuming all proportion problems are non-parametric. A single proportion test is parametric — is a parameter. Chi-square is for comparing several proportions (contingency tables).

11.8.8 Recap and Bridge

Trace the tree: MEAN or PROPORTION → One/Two/Several → Large (Z) or Small (T) → Formula. The first fork (mean vs proportion) is the most critical. The two-means rule uses , not individual sample sizes. With this tree in hand, the worked examples that follow are just applications of the branching logic.

11.8.9 Real-World & Domain Connection

Decision trees like this one are not just for classrooms. Statistical software (R, Python's scipy.stats, SAS) implements exactly this branching logic internally when you call a function like ttest_ind or ztest. Knowing the tree means you understand what the software is doing under the hood. More importantly, you can catch it when it does the wrong thing because you gave it the wrong data type. In industry, being able to look at a business question and say "that is a two-sample Z-test for proportions" is worth more than computing the formula by hand.

11.9 Worked Example 1 — Sodium Content (One Mean, Right-Tailed Z-Test)

A restaurant says its breakfast sandwich has at most 920 mg of sodium. You test 44 sandwiches and find they average 925 mg. Just 5 mg over — is that random kitchen variation or a real problem? This is your first fully worked hypothesis test.

11.9.1 Problem Statement

A food restaurant estimates that the mean sodium content in one of its breakfast sandwiches is not more than 920 milligrams. A random sample of 44 breakfast sandwiches has a mean of 925 mg with a standard deviation of 18 mg. Test at .

11.9.2 Tracing the Decision Tree

  • Involves "mean sodium content" → MEAN branch
  • One product, one population → One mean
  • → Large sample → Z-test

11.9.3 Setting Up Hypotheses

The claim to test: mean sodium ≤ 920 mg.

  • (the restaurant's claim — contains , works in the formula with )
  • (sodium is more than claimed)

Since uses , this is a right-tailed test.

11.9.4 Decision Criteria

At , right-tailed Z-test:

  • Reject if

The Z value 1.645 comes from the standard normal table: the point where the right-tail area is 0.05, meaning the body area (to the left) is 0.95.

11.9.5 Computing the Test Statistic

Given: , , , .

Population standard deviation is not available, so use :

Step-by-step:

  1. Difference from claim: mg above
  2. Standard error:
  3. Test statistic:

The Z-value of 1.842 means the sample mean is 1.842 standard errors above the claimed value.

11.9.6 Conclusion

Computed is greater than the critical value . It falls in the rejection region.

Reject . The restaurant's claim that sodium is ≤ 920 mg is not supported. The evidence suggests the mean sodium content is greater than 920 mg.

Sense-check: The difference was only 5 mg (0.54% above claim), but with sandwiches, the standard error is small enough that even 5 mg is statistically significant. This illustrates why "statistically significant" does not always mean "practically important" — 5 mg of sodium is nutritionally trivial, but the test correctly flags that the process mean is not at the claimed level.

Pitfall specific to this example: The restaurant claimed "not more than 920" — this is , which naturally contains the equality sign. So no hypothesis swap was needed. The claim goes straight into because it already has . If the claim had been "less than 920" (strict inequality), you would have needed the swap.

11.9.7 Real-World & Domain Connection

This is exactly how food regulatory bodies enforce labelling laws. The FDA and similar agencies periodically sample products from shelves, run hypothesis tests on nutritional content, and issue violations when (the label claim) is rejected. The standard means they accept a 5% chance of wrongly accusing a compliant manufacturer — a trade-off between consumer protection and business fairness.

11.10 Worked Example 2 — Light Bulb Life (One Mean, Left-Tailed Z-Test, with Hypothesis Swap)

This is the example where the equal-to-sign rule forces you to swap and . The manufacturer claims "less than 750 hours." But needs an equality sign. So the claim becomes , and you interpret the result backward at the end. This swap is the single most common source of confusion on exams — master it here.

11.10.1 Problem Statement

A light bulb manufacturer guarantees that the mean life of a certain type of light bulb is less than 750 hours. A sample of 36 bulbs has a mean life of 745 hours with a standard deviation of 60 hours. Test at .

11.10.2 The Hypothesis Swap — Critical Discussion

The natural reading: the manufacturer claims . So you might think:

But must contain an equality sign. The statement (strict inequality) does not allow you to plug into the Z formula. Therefore, you must swap:

  • (now contains equality — )
  • (the manufacturer's claim becomes )

The interpretation at the end maps backward:

  • If you reject (), you support () — the manufacturer's claim stands.
  • If you do not reject , the manufacturer's claim is not supported.

Several students asked about the swap:

Q: Isn't swapping contrary to what the problem states? The guarantee says "less than 750."

A: Yes, originally the claim is , which would be . But because needs an equality sign for the formula to work, we make the and the . The conclusion from the test will then be interpreted back in terms of the original claim. The swap is a mechanical necessity — it does not change what you are testing.

Q: Since we swapped, don't we also swap the final decision?

A: No. You follow the procedure with the swapped pair. If the test says "do not reject " (meaning stands), that means the original claim () is rejected. The interpretation step at the end maps the result back to the original question. Always trace the logic: stands → is rejected → original claim (which became ) is rejected.

11.10.3 Setting Up Hypotheses (Final Form)

Since uses , this is a left-tailed test.

11.10.4 Decision Criteria

At , left-tailed Z-test:

  • Reject if

The critical value is from the standard normal table. For a left-tailed test at , the left-tail area is 0.01, corresponding to (symmetric to the right-tail value ).

11.10.5 Computing the Test Statistic

Given: , , , .

Step-by-step:

  1. Difference from null value: hours (5 hours below claim)
  2. Standard error:
  3. Test statistic:

The sample mean is only 0.5 standard errors below 750. For rejection at , you need at least 2.33 standard errors below.

11.10.6 Conclusion

Computed is greater than (it falls in the acceptance region — to the right of the critical value).

Do not reject . That means stands. Translating back to the original claim: the manufacturer's guarantee that mean life is less than 750 hours is rejected. The data does not support the claim.

Sense-check: The sample mean (745) is only 5 hours below the claimed 750, and the standard deviation (60) is large relative to this difference. With , the standard error is 10 — so 5 hours is just half a standard error. At the strict level, this is nowhere near significant. The manufacturer would need a much larger sample or a much lower sample mean to support their guarantee.

Q: The slide says "we don't have enough evidence to prove" — but we rejected the claim. Isn't that contradictory?

A: The statistical phrasing is always "do not reject " rather than "accept ." Here, is , and we do not reject it. That means the alternative (the manufacturer's original claim) is rejected. The statement "not enough evidence to support the manufacturer's claim" is the correct interpretation. Do not get confused by the diplomatic wording — "do not reject " means the status quo wins, which here means the guarantee is not credible.

11.10.7 Real-World & Domain Connection

This type of test — where a manufacturer's claim becomes via the swap — is standard in false-advertising litigation. A company says "our product lasts less than X" (which sounds bad, but maybe they mean it degrades safely). Regulators test and only act if they can prove the opposite. The burden of proof is on the regulator to show the claim is false, not on the manufacturer to prove it true. The swap encodes a legal principle: the accuser must prove guilt.

11.11 Worked Example 3 — Package Delivery (One Mean, Two-Tailed Z-Test)

A delivery company says "3 days." You sample 50 packages and get 3.4 days. The difference is 0.4 days — about 10 hours. Is that bad luck or a broken promise? This time, you do not know which direction to look, so you use a two-tailed test with the stricter ±1.96 boundary.

11.11.1 Problem Statement

A company claims the average delivery time for its packages is 3 days. A sample of 50 packages has a mean delivery time of 3.4 days with a standard deviation of 1.2 days. Test at .

11.11.2 Tracing the Decision Tree

  • Involves "average delivery time" → MEAN branch
  • One company, one population → One mean
  • → Large sample → Z-test

11.11.3 Setting Up Hypotheses

The claim to test: mean delivery time = 3 days. The question is simply: is this true or not?

Since uses , this is a two-tailed test. You would reject if delivery is significantly faster OR significantly slower than 3 days.

11.11.4 Decision Criteria

At , two-tailed Z-test:

  • Reject if or

The total is split: in each tail. The critical values bound the middle 95% of the standard normal.

Compare with Example 1: for the same , the two-tailed critical value (1.96) is stricter than the one-tailed (1.645). The two-tailed test demands more extreme evidence because you are "spending" half your on each side.

11.11.5 Computing the Test Statistic

Given: , , , .

Step-by-step:

  1. Difference from claim: days
  2. Standard error:
  3. Test statistic:

The sample mean is 2.36 standard errors above the claimed 3 days.

11.11.6 Conclusion

Computed is greater than . It falls in the right-tail rejection region.

Reject . The company's claim that average delivery time is 3 days is not supported. The evidence suggests the mean differs from 3 days (specifically, it appears to be greater — deliveries are taking longer than promised).

Sense-check: would also have been significant under a one-tailed test (1.645 threshold), but just barely at two-tailed (2.58 threshold — not significant). The two-tailed framing is appropriate here because the company's promise is simply "3 days" — a deviation in either direction (faster or slower) would contradict the claim.

Pitfall specific to two-tailed tests: Do not halve when looking up the critical value — the table already accounts for the split. At two-tailed, use ±1.96 directly. Some students mistakenly use ±1.645 for a two-tailed test, which inflates the Type I error rate from 5% to 10%.

11.11.7 Real-World & Domain Connection

Delivery time testing is a standard operations-analytics use case. E-commerce companies continuously run hypothesis tests on delivery promises. If is rejected, either the promise is updated or the logistics chain is investigated. Two-tailed tests are appropriate here because being consistently faster than promised can also be a problem — it might mean you are over-spending on premium shipping that customers did not pay for.

11.12 Worked Example 4 — Tire Brands (Two Means, Two-Tailed Z-Test)

Two tire brands. Brand 1 averages 38,600 km, Brand 2 averages 40,100 km. That is a 1,500 km gap — about 4%. Is it a real difference between brands, or just the luck of which tires you sampled? This is your first two-population test.

11.12.1 Problem Statement

Is there a significant difference between two brands of tires? Sample from Brand 1: , km, km. Sample from Brand 2: , km, km. Test at .

11.12.2 Tracing the Decision Tree

  • Involves "mean" (tread life in km) and comparison between two brands → Two means
  • → Large sample → Z-test

11.12.3 Setting Up Hypotheses

"Significant difference" means testing whether the means are equal or not equal:

  • (no difference between brands)
  • (there IS a difference)

Two-tailed test — you are open to Brand 1 being either better or worse.

11.12.4 Decision Criteria

At , two-tailed: reject if .

11.12.5 Computing the Test Statistic

Use the two-means formula with sample standard deviations (population variances unknown):

Under , the term and drops out.

Verified computation: . The slide may report a slightly different Z-value (possibly 2.30 with different rounding), but the conclusion is identical — both values exceed the 1.96 threshold. The procedural flow is what matters: identify two means, compute df, use the two-means Z formula, compare against ±1.96.

11.12.6 Conclusion

Reject . There is a statistically significant difference between the two tire brands. Brand 2 appears to have a higher mean tread life.

Sense-check: The 1,500 km gap is about 4% of the average tread life. The denominator (standard error of the difference) is 733 km, so the gap is about 2 standard errors — enough to be significant at the 5% level but not overwhelming. With larger samples, even smaller gaps would become significant.

11.12.7 Student Q&A

Q: In the formula, why does disappear?

A: Because states , so . The numerator becomes simply . You are testing whether the observed difference between sample means is far enough from zero to reject the null. If the problem said something like "test whether Brand 2 exceeds Brand 1 by at least 250 km," then you would use 250 instead of zero in the numerator.

11.12.8 Pitfalls

  • Forgetting that the denominator is the standard error of the difference. The variances add — you do NOT subtract them. The formula is , not . Variances of independent samples always add.
  • Using the wrong df rule. For two means, use , not or either individual .
  • Confusing which mean goes first. It does not matter as long as you are consistent. If you swap the order, Z changes sign but stays the same, and for a two-tailed test the conclusion is unchanged.

11.12.9 Real-World & Domain Connection

Tire manufacturers and automotive magazines run exactly these tests. Consumer Reports, for example, buys tires off the shelf, mounts them on test vehicles, measures tread wear under controlled conditions, and publishes comparisons. A two-sample Z-test (or more commonly, a two-sample T-test) determines whether the observed differences are "real" or within the margin of sampling error. The result directly affects purchasing recommendations read by millions of consumers.

11.13 Worked Example 5 — Academic Performance (Two Means, Right-Tailed Z-Test, with Hypothesis Swap)

Group A averages 78, Group B averages 74. Is Group A genuinely better, or is the 4-point gap just sampling noise? This example combines two concepts: the two-means test AND the hypothesis swap for a strict-inequality claim.

11.13.1 Problem Statement

Students in Group A performed better on average than students in Group B. Sample: Group A — , , . Group B — , , . Test at .

11.13.2 Tracing the Decision Tree

  • Means involved, comparing two groups → Two means
  • → Large sample → Z-test

11.13.3 Setting Up Hypotheses

The claim: Group A > Group B → (strict inequality, no equality). Following the equal-to-sign rule — swap so gets the equality:

  • (Group A is not better — contains , so equality sign present)
  • (Group A IS better — the original claim becomes )

Right-tailed test. As with the light bulb example, you will interpret the result backward: if you reject , you support the claim that Group A is better.

11.13.4 Decision Criteria

At , right-tailed: reject if .

11.13.5 Computing the Test Statistic

Verified: — confirmed. The computation is correct.

11.13.6 Conclusion

Reject . Accept : Group A performs significantly better than Group B.

Sense-check: The gap is 4 points. Group A's standard deviation (8) and Group B's (6) are both substantial relative to the gap. But with and , the combined df = 73, making the standard error of the difference small enough (1.62) that 4 points is 2.47 standard errors — easily significant.

Pitfall: When the claim is a strict inequality like "A is better than B," it MUST become . The null becomes . Do not write — that has no equality sign and you cannot plug a specific number into the test statistic.

11.13.7 Real-World & Domain Connection

This is the standard setup for educational research: compare test scores between a treatment group (new teaching method) and a control group (traditional method). The hypothesis swap is standard here because the researcher's claim ("the new method is better") is a strict inequality that becomes . A significant result means the new method is adopted; a non-significant result means sticking with the status quo. The burden of proof is on the innovation, not on tradition.

11.14 Worked Example 6 — Disease Survival (One Proportion, Right-Tailed Z-Test)

18 out of 20 people survived — that is 90%. The claim is "85% or more." With just 20 people, is 90% convincing evidence that the true survival rate exceeds 85%, or could this just be a lucky roll of the dice? This is your first proportion test.

11.14.1 Problem Statement

20 people were attacked by a disease and only 18 survived. Test whether the survival rate is 85% or more at . Use a large sample test.

11.14.2 Tracing the Decision Tree

  • No mean discussed. The problem talks about "survival rate" — a percentage/fraction → PROPORTION branch
  • One disease, one population → One proportion
  • would normally be a small sample, but the problem explicitly says "use a large sample test" → Z-test

Note: For proportion tests, the large-sample condition is typically and . Here and . The condition is not fully met, which is why this is a borderline case. The problem explicitly instructs to use a large-sample test for pedagogical purposes.

11.14.3 Setting Up Hypotheses

The problem asks: is the survival rate 85% or is it more than 85%?

  • (contains equality — works in the formula)
  • (the question: is it MORE than 85%?)

Right-tailed test.

Q: If the null and alternative don't add up to the entire problem space, is that a problem?

A: The pair vs does not cover , but that is fine — the specific question is "is it 85% or more?" The test discriminates between these two candidate statements. The is forced to be the one with the equality sign (), and the remaining option () becomes . This is a common exam scenario.

11.14.4 Decision Criteria

At , right-tailed: reject if .

11.14.5 Computing the Test Statistic

Sample proportion:

Population proportion under : ,

Critical detail: The denominator uses (from ), NOT (from the sample). This is a deliberate choice — under , the standard error of is , computed at the null value. Using instead would give a different standard error and a different Z. The formula ties the test statistic's distribution to .

11.14.6 Conclusion

Do not reject . The hypothesis that the survival rate is 85% stands. There is not enough evidence to say the survival rate is more than 85%.

Sense-check: The sample proportion is 90% — visually that looks higher than 85%. But with only observations, a single additional death (17/20 = 85%) would drop the sample proportion to exactly the null value. The evidence is just too thin. This is a perfect illustration of why sample size matters: 90% from 20 people is far less convincing than 90% from 200 people would be. With and the same proportions, would be about 1.98 — significant.

Key pitfalls for proportion tests:

  • Using in the denominator instead of . The formula is , not . Using changes the test and is incorrect.
  • Forgetting . Simple arithmetic error but very common.
  • Treating proportions like means. The proportion Z-test has its own formula and its own sample-size conditions (, ). Do not use the mean formula for a proportion problem.

11.14.7 Real-World & Domain Connection

Survival rate testing is standard in medical research. A Phase II clinical trial might test (the current standard-of-care survival rate) against (the new treatment improves survival). With only 20 patients, the trial is underpowered — even a 5-percentage-point improvement cannot be detected. This is why medical trials typically require hundreds or thousands of patients: to have enough power to detect clinically meaningful improvements. Sample size planning (power analysis) is the tool that determines how many patients you need BEFORE running the trial.

11.15 Worked Example 7 — Two Judges (Two Proportions, Z-Test)

11.15.1 Problem Identification

This problem involves comparing proportions between two judges — two populations, proportions, large sample → two-proportion Z-test. The professor presented this as a quick identification exercise to confirm understanding of the decision tree.

Tracing the tree for this problem:

  • Talks about "proportion of cases judged guilty" → PROPORTION branch
  • Two judges being compared → Two proportions
  • Large sample → Z-test for two proportions

The formula for a two-proportion Z-test:

where is the pooled proportion: . Under , the term .

Note: the two-proportion Z-test uses a pooled estimate of the standard error (unlike the two-means test, which uses separate variances). This is because under , both populations share the same true proportion .

Note: The full numerical walkthrough for this example was not present in the recorded lecture — the professor presented it only as a classification exercise to practise tracing the decision tree. The two-proportion Z-test formula and procedure above are provided for completeness. Refer to the course slides for the specific numbers used in this example.

11.15.2 Real-World & Domain Connection

Two-proportion tests are used extensively in legal analytics: comparing conviction rates between judges, between jurisdictions, or before and after a policy change. They also appear in A/B testing for conversion rates — does landing page A convert more visitors than landing page B? The pooled proportion formula accounts for the fact that, under , both groups are drawn from the same underlying conversion rate.

Exam Guidance Summary

Exam note: The professor indicated the next session will include 10–15 more numerical problems. Be prepared to trace any problem through the decision tree, set up hypotheses (including swaps), compute the test statistic, and draw the correct conclusion in plain language.

What to prioritise

  • The master flow chart (Section 11.8) is your single most important reference. If you understand how to trace any problem through that tree, you can solve virtually any hypothesis testing question. Print it out. Memorise the branching logic.
  • Common question types (roughly in order of exam frequency):
    1. One mean, large sample — Z-test (most common)
    2. One mean, small sample — T-test
    3. Two means — Z-test (large) or T-test (small)
    4. One proportion — Z-test
    5. ANOVA and Chi-square — separate topics, covered next session

High-risk concepts

  • The equal-to-sign rule for is the most frequent source of confusion. When the natural claim is a strict inequality ( or ), swap the pair so gets the equality ( or ). Then interpret back at the end. Practice the light bulb example (Section 11.10) until the swap feels automatic.
  • The two-means sample size rule uses , not individual sample sizes. Exam questions may deliberately give you one small and one large sample to test whether you apply the rule correctly.

What to memorise

One-tailedTwo-tailed
0.10±1.645±1.645
0.05±1.645±1.96
0.01±2.33±2.58

These six numbers appear in nearly every problem. Know them cold.

Language conventions

Statistical language uses "do not reject " rather than "accept ." For problem-solving, treat them as equivalent — the professor accepts both phrasings on exams. But in your conclusion sentence, always answer the original question in plain English: "The evidence suggests the mean sodium content exceeds 920 mg," not just "Reject ."

Looking ahead

  • Chi-square and ANOVA will be covered in the next session. These handle "several proportions" and "several means" respectively — the bottom branches of the decision tree.
  • The next session will include 10–15 more numerical problems to solidify concepts. The worked examples in Sections 11.9–11.15 cover every major problem type that will appear.

Key Industry Applications

Hypothesis testing is not just an academic exercise — it is the decision engine behind quality assurance, medical approvals, and policy evaluation across every quantitative industry.

Quality Control & Manufacturing

Testing whether mean sodium content, product life, or fill volume meets specifications. Every production line in the world uses some form of hypothesis testing — often automated — to decide whether to stop the line, adjust a process, or release a batch. The Z-test and T-test are the mathematical backbone of Statistical Process Control (SPC).

Medical Research & Pharmaceuticals

Testing survival rates and treatment efficacy, where Type I vs Type II error trade-offs have life-or-death implications. The FDA's drug approval process is, at its core, a hypothesis test: : new drug = placebo vs : new drug > placebo, tested at (or stricter). False positives mean dangerous drugs reach the market. False negatives mean effective drugs never do.

Education & Social Science

Comparing academic performance between groups (teaching methods, curricula, demographics). Every "statistically significant" finding in an education journal traces back to the same six-step procedure covered in this lecture. The hypothesis swap (Section 11.10) is particularly common here because research hypotheses are almost always directional ("the new method is better").

Evaluating agreement between judges using two-proportion tests. Are two judges ruling consistently, or does one have a significantly different conviction rate? These tests have been used in appellate cases to demonstrate judicial bias. The two-proportion Z-test is the standard tool.

Marketing & E-Commerce

Testing whether a campaign improved response rates (proportion tests) or whether a new website layout increases average order value (mean tests). A/B testing — the dominant experimental method in tech — is hypothesis testing with a different name. Every time Google, Amazon, or Netflix shows you a variant and measures your response, a Z-test or T-test is running behind the scenes.

Food Industry & Regulatory Compliance

Validating nutritional label claims against sample testing. When a cereal box says "10g protein per serving," that number came from lab tests, and regulatory agencies verify it using the exact procedure from Section 11.9. The level is chosen to balance consumer protection against the cost of false accusations — a policy decision dressed in statistical clothing.

ISM Lecture 11 notes · Hypothesis Testing

Introduction to Statistical Methods· postgraduate· 2026-07-06

Sections Breakdown

111.1 What Is Hypothesis Testing?

Definition of hypothesis testing, population vs sample, the core logic flow, pitfalls, and the courtroom analogy for the null hypothesis.

211.2 Null and Alternative Hypotheses

Setting up H0 and H1, the equal-to-sign rule, hypothesis swap rule, three standard forms for two-means tests, and common mistakes.

311.3 Parametric vs Non-Parametric Tests

Distinction between parametric (Z, T, ANOVA) and non-parametric (Chi-square) tests, when to use each, and the trade-off between power and robustness.

411.4 One-Tailed vs Two-Tailed Tests

How H1 determines tail direction, critical values for one-tailed (1.645) vs two-tailed (1.96), and the suspicious coin analogy.

511.5 Type I and Type II Errors

False positives vs false negatives, the error matrix, why Type I is prioritised, and the fire alarm and courtroom analogies.

611.6 Level of Significance and Confidence Level

Definition of alpha as false-positive tolerance, confidence level as 1-alpha, the origin of alpha=0.05, and domain-specific thresholds.

711.7 The Hypothesis Testing Procedure

The six-step recipe: H0, H1, alpha, critical region, compute test statistic, compare and conclude. The do not reject language explained.

811.8 The Complete Decision Tree for Choosing a Test

Master flow chart: Mean vs Proportion, One/Two/Several, Large (Z) vs Small (T). Formula reference table and two-means sample size rule.

911.9 Worked Example 1 — Sodium Content

One mean, right-tailed Z-test with real numbers. Restaurant sodium claim tested at alpha=0.05.

1011.10 Worked Example 2 — Light Bulb Life

One mean, left-tailed Z-test with hypothesis swap. Manufacturer guarantee tested at alpha=0.01.

1111.11 Worked Example 3 — Package Delivery

One mean, two-tailed Z-test. Delivery time claim tested against both faster and slower deviations.

1211.12 Worked Example 4 — Tire Brands

Two means, two-tailed Z-test comparing tread life between brands. Two-sample variance formula.

1311.13 Worked Example 5 — Academic Performance

Two means, right-tailed Z-test with hypothesis swap. Comparing group averages.

1411.14 Worked Example 6 — Disease Survival

One proportion, right-tailed Z-test. Survival rate claim with sample proportion and null-hypothesis standard error.

1511.15 Worked Example 7 — Two Judges

Two proportions Z-test classification. Pooled proportion formula and decision tree tracing.

16Exam Guidance Summary

Exam strategy: prioritise the master flow chart, memorise critical values, master the equal-to-sign rule, and practice the two-means sample size rule.

17Key Industry Applications

Real-world use of hypothesis testing in quality control, medical research, education, legal analytics, marketing, and food regulation.

Postgraduate management students studying inferential statistics

Exam Revision Notes

Below is the distilled, exam-ready core of this lecture. Every entry is built from the full textbook notes above. Use this section for rapid review — but if something doesn't make sense, go back to the full explanation in the main content.

What Is Hypothesis Testing?

Must-know: A hypothesis is a claim about a population parameter. Hypothesis testing uses sample data to decide whether to reject that claim. The logic is "innocent until proven guilty" — you assume the null hypothesis is true and reject it only if the sample evidence is strong enough.

Top pitfall: Confusing a population claim with a sample statistic. A hypothesis must be about the population, never about the sample.

Self-check: If a tailor claims a roll of fabric is good quality and you test one swatch, what is the sample, the population, and the hypothesis?

Connects to: Null and Alternative Hypotheses, The Hypothesis Testing Procedure

Null and Alternative Hypotheses

Must-know: H0 must contain an equality sign (=, ≤, or ≥). When the natural claim is a strict inequality (< or >), swap the pair so H0 gets equality. H1 determines whether the test is left-tailed, right-tailed, or two-tailed.

Top pitfall: Writing H0 without an equality sign or forgetting to swap when the natural claim uses a strict inequality.

Self-check: A manufacturer claims a product lasts less than 750 hours. Write the correct H0 and H1 pair after applying the swap rule.

Connects to: One-Tailed vs Two-Tailed Tests, Worked Example 2 — Light Bulb Life

Parametric vs Non-Parametric Tests

Must-know: Parametric tests (Z, T, ANOVA) assume a known distribution and test a parameter like the mean. Non-parametric tests (Chi-square) make minimal distributional assumptions. Parametric tests are more powerful when assumptions hold; non-parametric tests are more robust when they do not.

Top pitfall: Using a parametric test when the normality assumption is violated with a small sample (n < 30).

Self-check: You have 15 data points from an unknown distribution and want to test a claim about the mean. Should you use a Z-test, T-test, or non-parametric test?

Connects to: The Complete Decision Tree, Type I and Type II Errors

One-Tailed vs Two-Tailed Tests

Must-know: One-tailed: all alpha in one direction, critical value 1.645 at alpha=0.05. Two-tailed: alpha/2 in each direction, critical value 1.96 at alpha=0.05. H1 dictates the tail. Always choose before seeing the data.

Top pitfall: Using 1.645 (one-tailed) for a two-tailed test or choosing one-tailed after seeing the data.

Self-check: At alpha=0.05, what is the critical Z value for (a) a left-tailed test, (b) a two-tailed test?

Connects to: Null and Alternative Hypotheses, The Hypothesis Testing Procedure

Type I and Type II Errors

Must-know: Type I (alpha): reject a true H0 — false positive. Type II (beta): fail to reject a false H0 — false negative. Power = 1 - beta. The framework prioritises controlling Type I error because you must earn the right to reject the status quo.

Top pitfall: Thinking 'do not reject H0' proves H0 is true. It might just mean your sample was too small and beta was too high.

Self-check: A fire alarm fails to ring during a real fire. Is this a Type I or Type II error?

Connects to: Level of Significance and Confidence Level, The Hypothesis Testing Procedure

Level of Significance and Confidence Level

Must-know: Alpha is the probability of a Type I error — your self-imposed false-positive tolerance. Confidence level = 1 - alpha. Alpha = 0.05 is a convention, not a law. Always set alpha before seeing the data.

Top pitfall: Treating alpha=0.05 as a magic number or choosing alpha after seeing the p-value.

Self-check: If a test uses alpha=0.01, what is the confidence level? What does it mean in plain English?

Connects to: Type I and Type II Errors, The Hypothesis Testing Procedure

The Hypothesis Testing Procedure (Six Steps)

Must-know: Step 1: Set up H0 (must have equality). Step 2: Set up H1 (determines tail). Step 3: Choose alpha. Step 4: Determine critical region. Step 5: Compute test statistic. Step 6: Compare and conclude in plain English. Steps 1-4 before Step 5, always.

Top pitfall: Computing the test statistic before determining the critical region, or writing 'accept H0' instead of 'do not reject H0.'

Self-check: List the six steps in order and explain why Step 4 must come before Step 5.

Connects to: Null and Alternative Hypotheses, The Complete Decision Tree

The Complete Decision Tree

Must-know: First fork: Mean (average, mu) vs Proportion (rate, percentage). Second fork: One/Two/Several populations. Third fork: Large sample (Z-test) or Small sample (T-test). For two means, df = n1 + n2 - 2; if df ≥ 30, use Z-test.

Top pitfall: Forgetting the first fork (mean vs proportion) or using individual sample sizes instead of df for two-means tests.

Self-check: A problem discusses 'percentage of customers who return.' Trace this through the decision tree to the correct test.

Connects to: Parametric vs Non-Parametric Tests, All Worked Examples

Worked Examples — Z-Test for Means

Must-know: Right-tailed (sodium): H0: μ ≤ 920, H1: μ > 920, Z=1.842 > 1.645, reject. Left-tailed with swap (light bulb): H0: μ ≥ 750, H1: μ < 750, Z=-0.5 > -2.33, do not reject. Two-tailed (delivery): H0: μ = 3, H1: μ ≠ 3, Z=2.36 > 1.96, reject.

Top pitfall: Forgetting the hypothesis swap when the claim is a strict inequality. Using the wrong tail's critical value.

Self-check: For the sodium example, why is 5 mg statistically significant when it is so small? What would happen with a sample of only 10 sandwiches?

Connects to: The Hypothesis Testing Procedure, One-Tailed vs Two-Tailed Tests

Worked Examples — Two Means and Proportions

Must-know: Two means (tires): H0: μ₁=μ₂, H1: μ₁≠μ₂, |Z|=2.05>1.96, reject — significant difference. Proportion (survival): H0: P=0.85, H1: P>0.85, Z=0.63<1.645, do not reject — sample too small. Denominator always uses P from H0, NOT p̂.

Top pitfall: Using p̂ instead of P in the denominator of the proportion test, or subtracting variances instead of adding them for two-means tests.

Self-check: Why is 90% survival from 20 patients not significant while the same percentage from 200 patients would be? Compute both Z values.

Connects to: The Complete Decision Tree, Type I and Type II Errors

Was this lecture useful?

Loading comments…
🤖

BitsNotes AI Assistant

Subject Notes Assistant

Configure AI Chat

Choose how to access the chatbot
Have your own API key?

Switch to "Bring Your Own Key" tab above for unlimited access with any OpenAI-compatible provider.

🔑 Enter API key above to fetch live models from provider, or enter model name manually.
OpenAI-Compatible API Support

Choose any provider preset (Gemini, DeepSeek, Kimi, GLM, MiniMax, Qwen, OpenAI, Groq, Ollama, etc.) or enter a custom endpoint URL.

Security & Privacy First

Your API key is sent directly from your browser to your specified provider. BitsNotes servers never store or see your key.