6.3.1 · D2Interpretability & Explainability

Visual walkthrough — Importance of interpretability

3,120 words14 min readBack to topic

This is a visual walkthrough of the central result in the parent topic. Read it top to bottom; every symbol is built before it is used.


Step 1 — What does "accuracy" even draw?

WHAT. Before we can trade accuracy against anything, we need a picture of what accuracy is.

WHY. People say "90% accurate" as if it were one number floating in the air. But a percentage is really a count of correct answers out of a whole. To weigh it against costs later, we must see it as an area — a slice of a bar — not a floating number.

PICTURE. Look at the figure. We have 100 decisions the model made (the full bar). The blue slice is the fraction it got right. "Accuracy" is just: how much of the bar is blue?

  • correct decisions — how many times the model matched reality.
  • all decisions — the total number of predictions (the whole bar).

Figure — Importance of interpretability
Figure s01 — A horizontal bar of 100 decisions: a large blue slice (correct, 0.90 of the bar) and a small grey remainder. Accuracy is read off as the blue length divided by the whole bar length.


Step 2 — The hidden cost of the "wrong" slice

WHAT. We now colour the other part of the bar — the mistakes — and give it a price.

WHY. Accuracy quietly assumes every mistake is equally cheap. That is the lie. A mistake that blocks a real customer's honest payment is not the same as a mistake in a photo-tagging app. To compare models fairly, each mistake must carry a weight, a number saying "this is how much it hurts."

PICTURE. The orange slice is the wrong decisions. Above it we stack a red bar whose height is the pain-per-mistake. Cost is area = how many mistakes × how much each hurts.

  • — the fraction that is not blue, i.e. the orange mistakes (a number in ).
  • — the pain of one mistake, itself normalized to (0 = harmless, 1 = worst harm we track) so that Raw Cost stays a unit-less number on the same ruler as accuracy.

The symbol is here because "total damage" is always count of bad events times damage each — that is what multiplication answers: repeated addition of the same cost.

Figure — Importance of interpretability
Figure s02 — The same bar, now with the wrong decisions coloured orange, and a red "pain per mistake" bar of height stacked above them. Raw Cost is the shaded area = orange fraction height .


Step 3 — Splitting the pain into named channels

WHAT. We split that single "pain per mistake" into the three named costs the parent named: Deployment Risk, Compliance Cost, Trust Gap. Then we fold the mistake-fraction into each channel so the picture and the algebra agree.

WHY. In the real world, a mistake hurts in distinct ways at once: it can cause an operational failure (deployment risk), trigger a legal/audit expense (compliance cost), and erode users' willingness to use the system (trust gap). Lumping them into one hides which one dominates in a given domain. We break the red bar into three coloured segments so we can tune each independently.

PICTURE. From Step 2 the total cost was . First we split the per-mistake pain into three per-mistake pieces:

  • — the per-mistake pain in each channel (deployment, compliance, trust), each in .
  • — the domain dials weighting each channel.

Now multiply the whole thing by the mistake fraction , exactly as Step 2 demands — the multiplier does not vanish, it gets absorbed into each channel:

We define the three total channel penalties to already include the mistake fraction:

  • = Deployment Risk — the total deployment pain across all mistakes (already ). A hidden bug like the snow-detecting husky classifier blowing up in production. Normalized to .
  • = Compliance Cost — the total legal/audit pain across all mistakes (see Model Cards and Documentation). Normalized to .
  • = Trust Gap — the total adoption loss across all mistakes. Normalized to .

So the "" multiplier never disappears — it lives inside , , . With this bookkeeping the total penalty is simply

and this is the whole cost across all mistakes (not per-mistake), so it can be subtracted from accuracy directly in Step 4.

Figure — Importance of interpretability
Figure s03 — The single red pain bar splits into three stacked segments (red = deployment , orange = compliance , grey = trust ). Each segment's height already has the mistake fraction baked in, so their sum is the total cost.


Step 4 — Where interpretability enters the picture

WHAT. We connect interpretability to those three penalties. This is the key move.

WHY. So far nothing mentioned interpretability. But look at what each penalty depends on: you can only shrink Deployment Risk if you can see what the model learned; you can only pay less Compliance Cost if you can explain decisions to auditors; the Trust Gap shrinks only when humans can check the reasoning. All three shrink as understandability rises. That is precisely why the parent note calls interpretability essential.

PICTURE. Two knobs on the left: Accuracy and Interpretability. Arrows show Accuracy feeds the blue "reward" bar, while Interpretability pulls down on all three penalty segments. More understandability = shorter red bars. Because , , already carry the mistake fraction from Step 3, the subtraction below is clean — no stray factor is needed:

  • — accuracy from Step 1 (the blue reward), in .
  • — interpretability: a unit-less number from (opaque) to (fully transparent), the transparency axis.
  • — each total penalty (mistake fraction already included) is now also a function of : as goes up, each goes down.

We write the penalties as functions of because that is exactly the question we care about: "if I make the model more understandable, what happens to my costs?" A function is the tool that turns "depends on" into arithmetic.

Figure — Importance of interpretability
Figure s04 — Three downward lines plot , , against interpretability (0 opaque → 1 transparent). All slope downhill (slope ), so higher can only shrink each penalty.


Step 5 — The crossover: 85% beats 90%

WHAT. We finally put two real models on the same axes and find where the interpretable one wins.

WHY. This is the parent's shocking claim, made concrete. We take the banking-fraud example: an interpretable model (, high ) versus a black box (, near-zero ), and compute each one's Value.

PICTURE. Two full bars side by side. Blue = accuracy reward. Red = total penalty. The black box has a taller blue but a much taller red. The interpretable model has shorter blue but tiny red. Net height (Value) — the black arrow — is taller for the interpretable model.

Plug the parent's regulated-banking dials, say with an opaque model incurring each, and an interpretable model incurring near :

  • / — the two accuracies (blue rewards).
  • vs — the two penalty totals (red bars).
  • — the interpretable model wins by of Value.

Figure — Importance of interpretability
Figure s05 — Two models as bars: blue reward up, red penalty down. Black box (0.90 blue, 0.30 red) nets Value 0.60; interpretable (0.85 blue, 0.00 red) nets Value 0.85. The interpretable bar's net height is taller.


Step 6 — The degenerate cases (never leave a gap)

WHAT. We check the edges: what happens when the dials are extreme.

WHY. A formula you trust must survive its corner cases. If it gives silly answers when or when accuracies tie, it was never really understood.

PICTURE. Four mini-panels, one per corner.

  1. All (low-stakes photo app). Penalties vanish: . Formula collapses back to plain accuracy — so the black box's extra does win. Correct: low stakes, use the black box + post-hoc explanation.
  2. Huge (heavily regulated). One giant red segment. Even a tiny compliance gap makes any opaque model lose. Matches GDPR/FCRA pressure toward interpretability.
  3. Equal accuracy (). Blue bars tie, so whoever has the shorter red bar wins — interpretability decides. This is why, all else equal, prefer an inherently interpretable model.
  4. Interpretable model also more accurate. No trade-off at all — it dominates on both bars. The "trade-off" was never a law, only a common case.

Figure — Importance of interpretability
Figure s06 — Four small bar-pair panels: (1) all so only blue matters and the box wins; (2) huge so a towering red penalty sinks the box; (3) equal blue bars so the shorter red bar (interpretable) wins; (4) interpretable model taller in blue and shorter in red, dominating outright.


The one-picture summary

WHAT. One figure compresses all six steps: knobs (Accuracy, Interpretability) → reward bar minus three shrinking penalty bars → net Value → crossover point.

WHY. If you remember one image from this page, remember this: Value is a tug-of-war between one blue reward and three red penalties, and interpretability is the hand pulling the red bars down.

Figure — Importance of interpretability
Figure s07 — The full story in one bar: blue reward on top, three red penalty segments (, , ) subtracted below, a green arrow marking that interpretability shrinks the red segments, and the net Value (0.60) labelled.

Recall Feynman retelling — say it like you'd tell a friend

Start with a bar: the blue part is how often the model is right. Everybody stops here and says "bigger blue wins." But the leftover part — the mistakes — costs money, and how much depends on where you use the model. So paint the mistakes red. That red is "how many mistakes times how much each hurts." Now split that pain into three stripes: one for stuff breaking in production, one for lawyers and auditors, one for people refusing to trust it — and keep the "how many mistakes" factor tucked inside each stripe so the bookkeeping stays honest. First we agree everything is measured on the same 0-to-1 ruler, so subtracting is fair. Now here's the trick: making the model understandable is like a hand that reaches over and squishes all three red stripes shorter (never taller — that's the rule, "slope points downhill"). So the real score isn't the blue bar — it's blue minus the whole red stack. A slightly shorter blue bar (85% instead of 90%) can still win if its red stripes are tiny. Turn the "how much do I care" dials to zero (a meme app) and only blue matters — use the black box. Turn any one of them way up (a hospital, a bank, a self-driving car) and that red stripe dominates — you must be able to explain. And sometimes the clear model is even more accurate, so there's no fight at all. That's the whole story: Value = one reward minus three penalties, and interpretability shrinks the penalties.

Recall Quick self-test

What does the blue bar represent? ::: The model's accuracy — the fraction of decisions it got right, a number in . What do the three red segments represent? ::: Deployment Risk , Compliance Cost , and Trust Gap — the three ways a mistake hurts, each with the mistake fraction already baked in, each normalized to . Where did the mistake-fraction multiplier go? ::: It did not vanish — it is folded inside , , , so the penalties are total costs and can be subtracted from accuracy directly. What does mean? ::: The derivative — the instantaneous rate of change (slope) of as increases; required to be so penalties only shrink. Why is subtracting penalties from accuracy legal? ::: Because every term is put on the same unit-less ruler, so the subtraction is dimensionally consistent. What do subscripts and mean? ::: = the black-box model, = the interpretable model. Under the parent's banking numbers, who wins and by how much? ::: The interpretable model, vs — a margin of . When does the black box correctly win? ::: When all (low stakes), so Value collapses to plain accuracy and its extra decides.