Worked examples — Interpreting model coefficients
Before we work anything, let us earn every symbol from zero.
The scenario matrix
Every cell below is a class of situation this topic can hand you. The worked examples that follow each name the cell(s) they cover, so nothing is left unshown.
| # | Case class | The trap / question it tests | Covered by |
|---|---|---|---|
| A | Linear, positive , continuous feature | plain "add per unit" | Ex 1 |
| B | Linear, negative | sign direction | Ex 2 |
| C | Linear, many units at once () | scale the change | Ex 2 |
| D | Linear, intercept / all-features-zero | is meaningful? | Ex 1, Ex 3 |
| E | Standardized coefficients, comparing importance | different scales | Ex 3 |
| F | Logistic, positive , odds ratio | multiply the odds | Ex 4 |
| G | Logistic, negative , odds ratio | odds shrink | Ex 5 |
| H | Logistic, (degenerate) | , no effect | Ex 5 |
| I | Logistic, small approximation | when it's valid | Ex 6 |
| J | Logistic, log-odds → actual probability | the non-linear jump | Ex 7 |
| K | Dummy (0/1) feature interpretation | "switching on" a category | Ex 4, Ex 9 |
| L | Correlated features / sign flip (exam twist) | ceteris paribus breaks | Ex 9 |
| M | Logistic, continuous | odds | Ex 6b |
| N | Logistic, intercept (all features 0) | baseline odds & probability | Ex 8 |
Worked examples
Example 1 — Linear, positive , and the intercept (cells A, D)
Step 1 — Plug in the base case. Why this step? We need a concrete anchor so "one more hour" has something to compare against.
Step 2 — Add one unit of hours, keep sleep fixed. The rule says the change is exactly .
Why this step? This demonstrates directly: the difference .
Step 3 — Read the intercept (cell D). Set every feature to : . That is the predicted score for a student who studies 0 hours and sleeps 0 hours. Why this step? To flag that may be nonsense (nobody sleeps 0 hours) — the intercept is real for the math but not always a meaningful person.
Verify: ✓ matches . Units: score is unitless points; has units "points per hour," points ✓.
Example 2 — Linear, negative , several units at once (cells B, C)
Step 1 — Read the sign. , so more miles → lower price. Direction settled. Why this step? The sign is the first thing to interpret; getting it wrong reverses the story.
Step 2 — Scale by the actual change (cell C). The per-unit change is , so for units: Why this step? Because linear means the effect scales linearly: 20,000 units cost , not just .
Verify: predict at miles : $30,000. At miles : . Difference ✓. Units: \text{(\/mile)} \times \text{miles} = \text{$}$ ✓.
Example 3 — Standardized coefficients: which feature matters more? (cells D, E)
Step 1 — Recognise the trap. Raw magnitudes aren't comparable because income is measured in tens of thousands while age is in single digits. See Feature Scaling & Standardization. Why this step? The whole point of standardizing: a big-range feature is forced to have a small coefficient, and vice versa. Comparing raw is meaningless.
Step 2 — Compute standardized coefficients . This is the effect per one standard deviation of the feature. Why this step? One SD of income is a "typical spread" of income, one SD of age a typical spread of age — now both are on the same "one typical wiggle" footing.
Step 3 — Compare. : age still wins, but by a factor of , not . Why this step? Only now that both numbers are in the same unit ("-change per one typical wiggle of the feature") is the comparison a fair statement about importance — comparing the raw vs would have compared apples ($-per-$) to oranges ($-per-year). The figure makes the reversal-of-scale visible.

Verify: ✓; ✓; ratio ✓.
Example 4 — Logistic, positive , dummy feature, odds ratio (cells F, K)
Step 1 — Identify the tool: exponentiate. The coefficient sits on log-odds, and . So is the factor by which odds multiply. Why this step? Adding to a log means multiplying the original quantity by — that's the defining property of logs/exponentials, and it's exactly why we reach for here rather than any other operation.
Step 2 — Compute the odds ratio OR (cell F). Why this step? Exponentiation is what converts the additive log-odds change () into the multiplicative odds change: because , the factor is literally the odds ratio. Any other operation would not preserve this "add-in-logs = multiply-in-odds" bridge.
Step 3 — Interpret the dummy (cell K). has_degree goes from to — a "1-unit increase" is literally switching the category on. So having a degree multiplies the odds of approval by . Why this step? For 0/1 features there is no "half a unit"; the coefficient is the whole effect of belonging vs. not belonging to that group.
Verify: odds at no-degree ; odds at degree . Ratio ✓.
Example 5 — Logistic, negative and the degenerate case (cells G, H)
Step 1 — Negative → odds ratio below 1 (cell G). So each extra loyalty year multiplies churn odds by — it roughly halves the odds. Why this step? multiplying by a number below 1 shrinks the odds. The sign of becomes "above or below 1" after exponentiation.
Step 2 — The degenerate (cell H). Multiplying odds by changes nothing: the newsletter feature has no modelled effect on churn odds. Why this step? Zero is the pivot. Left of it (negative ) odds shrink; right of it (positive ) odds grow; exactly at it, no effect.

Verify: ✓ (below 1); ✓.
Example 6 — When is safe? (cell I)
Step 1 — Why the shortcut exists. For small , (the first two terms of its expansion). So a small coefficient means "odds go up by about ." Why this step? It saves mental exponentiation for tiny coefficients, which are extremely common in standardized or fine-grained features.
Step 2 — Test the small one, .
- True: → .
- Shortcut: → .
- Gap: about — negligible. ✓ Safe.
Why this step? We test near first because that is exactly where the tangent line hugs the curve tightest — verifying the gap is tiny confirms the shortcut is licensed here, not just asserting it.
Step 3 — Test the big one, .
- True: → .
- Shortcut: → .
- Gap: about percentage points — wildly wrong. ✗ Do not use.
Why this step? We test a far-from-zero value to expose the failure: the approximation is a straight line tangent to a curve at , so far from the curve races ahead and the line lags. Seeing the 56-point gap gives a concrete "how far is too far" and yields the rule of thumb: fine only for .
Verify: , shortcut , gap ✓; , shortcut , gap ✓.
Example 6b — Logistic, continuous feature, (cell M)
Step 1 — Recall: log-odds is linear, so a change adds . Why this step? Just like the linear car example scaled the effect by , here the log-odds (which is linear) scales the same way before we exponentiate.
Step 2 — Exponentiate the whole change (cell M). Adding to log-odds multiplies the odds by : Why this step? You must exponentiate the total log-odds change, not raise and eyeball it — though note , so " applied three times" gives the same thing.
Verify: ; ✓. So a naive "" would be wrong — odds multiply, they don't add.
Example 7 — Log-odds → actual probability (cell J)
Step 1 — Compute each person's log-odds .
- No degree: .
- Degree: . Why this step? Probability lives at the end of the pipeline; we first get the linear log-odds, then bend it through the sigmoid.
Step 2 — Apply the sigmoid . Why this step? The sigmoid is the only function that turns any real log-odds into a valid probability in — that's why logistic regression uses it and why the effect on probability is not linear.
Step 3 — See why "add 1.1 to probability" is nonsense (cell J). The probability rose by , not . And — impossible for a probability. Why this step? To hammer home that the same additive log-odds bump produces a different probability jump depending on where you start on the S-curve — and can never push probability past 1, unlike naive addition.

Verify: ✓; ✓; difference ✓; and ✓.
Example 8 — The logistic intercept: baseline odds and probability (cell N)
Step 1 — Identify the baseline person (cell N). Set every feature to : here has_degree , i.e. a person without a degree. Then log-odds . Why this step? The intercept is the logistic twin of the linear intercept: it is the prediction (in log-odds) for the all-zeros individual. For a dummy feature, "0" is a real group (no degree), so unlike the sleep-0 case it is meaningful here.
Step 2 — Turn baseline log-odds into baseline odds. Exponentiate: Below 1 → fewer approvals than rejections for the baseline group. Why this step? ; this is the cleanest reading of the intercept — it is the baseline odds.
Step 3 — Turn baseline log-odds into baseline probability. Apply the sigmoid: So a no-degree applicant has about a chance of approval before any positive feature helps. Why this step? To show the intercept can be read three equivalent ways — log-odds , odds , probability — and probability is the one humans understand.
Verify: ✓; ✓; and ✓ (probability and odds agree).
Example 9 — Exam twist: correlated features and a sign flip (cells K, L)
Step 1 — Recall what literally claims. It is the effect of one more room holding sqft fixed — a room added without any extra floor area. In reality sqft and rooms move together, so this "ceteris paribus" move barely exists in the data. Why this step? The interpretation only makes sense if you can actually vary one feature alone. Correlation destroys that. See Multicollinearity & VIF.
Step 2 — Why the signs flip. When two features carry almost the same information, the model can split the shared effect between them in infinitely many near-equivalent ways. A nudge to the data reshuffles the split, so individual 's swing violently and can flip sign — even though the combined prediction is stable. Why this step? This is the concrete mechanism behind "coefficients become unreliable under multicollinearity."
Step 3 — Sanity check the combined effect. Take a realistic joint move: +1 room typically comes with +200 sqft.
- Run 1: .
- Run 2: . Both are positive — rent still rises. The individual coefficients lied; the realistic bundle did not (mostly). Why this step? It shows the prediction can be trustworthy while the per-feature story is not.
Step 4 — The fix (resolving cell L). Concretely: (1) measure the redundancy with a correlation matrix or VIF — a VIF above ~5–10 flags trouble; (2) remove or merge one of the twins (keep sqft, drop rooms, or build a "rooms-per-sqft" feature); (3) shrink the coefficients with Regularization (Ridge & Lasso) — Ridge in particular spreads the shared effect smoothly and stops the wild sign-swings; (4) report bundles, not singletons — quote the effect of a realistic joint move (as in Step 3) instead of a lone coefficient. After any of these, the surviving coefficient becomes stable and interpretable again. Why this step? Without a fix, scenario L stays unresolved: you would keep reading a meaningless lonely coefficient. The fixes restore the ceteris paribus interpretation by removing the thing that broke it.
Verify: Run 1 bundle ✓; Run 2 bundle ✓; both ✓.
Active recall
Recall Cover the answers
Linear: 20,000 more miles at changes price by? ::: -\3000\beta^{\text{std}}_j = \beta_j,\sigma_j\beta = 1.1\text{OR}=e^{1.1}\approx 3.0\beta = -0.7e^{-0.7}\approx 0.50\beta = 0e^0 = 1\beta=0.4e^{0.4\times 3}=e^{1.2}\approx 3.32e^\beta\approx 1+\beta|\beta|\lesssim 0.1\ell=0.1\sigma(0.1)=\frac{1}{1+e^{-0.1}}\approx 0.525\beta_0=-1-1e^{-1}\approx 0.37\approx 0.27$. A single coefficient flips sign between runs — likely cause and fix? ::: multicollinearity; fix by VIF check, dropping/merging a twin, or regularization.
Connections
- Parent: Interpreting model coefficients
- Linear Regression — additive coefficients (Ex 1–3)
- Logistic Regression — sigmoid & log-odds (Ex 4–8)
- Odds and Log-Odds — the transform
- Feature Scaling & Standardization — Ex 3
- Multicollinearity & VIF — Ex 9
- Regularization (Ridge & Lasso) — stabilizing flipped coefficients
- Correlation vs Causation — the causal caveat