Responsible AI
Explainability: Intrinsic, Local, Global, and Counterfactual
Compare intrinsic models, feature attribution, example-based, global surrogate, counterfactual, concept, and procedural explanations.
By the end you can
- Explain why explainability methods differ by target, scope, fidelity, stability, actionability, and audience; the user question should determine the method
- Distinguish Feature attribution, Counterfactual explanation, and Process explanation
- Identify evidence that connects intrinsic structure to procedural explanation
- Design a review that moves from define the user question to connect to action
Visual
Where explainability method selection enters the lifecycle
Explanations come in five kinds, from the structure of the model itself to the procedure around the decision. They are not interchangeable. The last kind is not a simpler register for readers who cannot follow the mathematics. It is the one a binding European regulation reaches for, and the one an affected person can act on.
- 1
Intrinsic structure
Coefficients, rules, monotonic terms, sparse trees, or additive components.
- 2
Local attribution
Assigns contribution to input features for one prediction.
- 3
Global behavior
Summarizes patterns across a population or model surface.
- 4
Counterfactual and example
Shows alternative inputs or comparable cases.
- 5
Procedural explanation
Describes data, policy, workflow, review, and rights around the decision.
Example
The Epic Sepsis Model, externally validated at Michigan Medicine
A clinician asks why a patient was flagged. The flag in the wards is not hypothetical. The Epic Sepsis Model is a proprietary sepsis prediction model deployed at hundreds of US hospitals. In 2021 JAMA Internal Medicine published an external validation of it, run at Michigan Medicine over 27,697 patients and 38,455 hospitalizations between December 2018 and October 2019. Sepsis occurred in 2,552 of those hospitalizations, 7% of the total.
The numbers came back poor. Area under the curve 0.63 (95% CI, 0.62–0.64). Sensitivity 33%, specificity 83%, positive predictive value 12%. The model raised alerts on 18% of all hospitalizations and still missed 1,709 of the 2,552 sepsis patients, 67% of them. At an ESM score of at least 6, the number needed to evaluate was 8. Wong and colleagues put the finding in one sentence: “This external validation cohort study suggests that the ESM has poor discrimination and calibration in predicting the onset of sepsis.”
Ask the vendor of a model like that why this patient was flagged, and what comes back is a global feature-importance chart. Average model behaviour. Not the patient’s case, and not the reliability of the flag.
- Question mismatch: The clinician asks about one alert on one patient. The chart answers a question about a population.
- Explanation supplied: Aggregate importance across that population — a summary of a model whose discrimination, in the one external validation, was an area under the curve of 0.63.
- Evidence gap: The chart shows no local factors, no data quality, no uncertainty, no alternatives. Nothing printed on it says that 1,709 of 2,552 sepsis hospitalizations went unflagged.
- Clinical risk: A visually persuasive graph may anchor the clinician. Alerts on 18% of all hospitalizations and a positive predictive value of 12% are what an alert is actually worth at the bedside.
- Governance failure: The method was selected for availability rather than the user’s decision.
Accurate and useless in the same moment
Explainability methods answer different questions. A reader has to know which question is being answered before the answer means anything. How does the model work globally? Which inputs influenced this one output? What examples are similar? What change would alter the result? How did the process and the data produce the decision? The question should choose the method. An intrinsic explanation reads the structure of the model itself. A post-hoc method builds a second, simpler account of how the first one behaved, after it has already been trained. Local attribution, global importance, surrogates, counterfactuals, examples, concepts, and process traces differ in scope, fidelity, stability, actionability, and vulnerability to misuse.
That line between intrinsic and post-hoc is not a neutral taxonomy. It carries a stake, and in 2019 Cynthia Rudin named the stake in Nature Machine Intelligence: stop explaining black box machine learning models for high stakes decisions, and use interpretable models instead. A second, simpler account fitted after training is not the model, she holds. Systems making high-stakes decisions should be designed to be inherently interpretable. The paper puts the risk plainly: “People have hoped that creating methods for explaining these black box models will alleviate some of these problems, but trying to explain black box models, rather than creating models that are interpretable in the first place, is likely to perpetuate bad practices and can potentially cause catastrophic harm to society.”
The clinician facing an ESM alert asks a local question and receives global importance. That is how a chart can be accurate and useless in the same moment.
Nothing in a correct chart warns the reader that it answered a different question than the one they asked.
Case
LIME at KDD 2016, Shapley values at NeurIPS 2017
LIME explains one prediction by fitting an interpretable model in a local neighbourhood around it — Local Interpretable Model-agnostic Explanations. Ribeiro and colleagues introduced it at KDD in 2016. A year later at NeurIPS, Lundberg and Lee unified that whole family, bringing additive feature-attribution methods, LIME among them, under Shapley values from cooperative game theory. Two methods, a year apart, both aimed at a single prediction.
Case
Three questions, and the clinician asked the first
Both of those methods answer a local question: why this output, for this input. Global feature importance answers a different one — what the model tends to weigh across 38,455 hospitalizations. The clinician had asked the first. Counterfactuals are a third register again: what would have had to differ.
Steps
Turn explainability method selection into an operating control
The question the user is actually asking comes first, and the method comes last. Reverse those two and the project ends up holding an explanation that nobody can use.
Step four is the one usually left as a list of nouns, so here is a test with a published result. Randomization-based sanity checks for explanation methods come in two forms, a model parameter randomization test and a data randomization test. Adebayo and colleagues proposed them in 2018 and ran them on an Inception v3 model trained on ImageNet. Gradients and GradCAM passed. Guided BackProp and Guided GradCAM did not. Those two are invariant to higher-layer parameters, and the maps they produce are visually comparable to a plain edge detector, which uses neither the model nor the training data. The abstract says it flatly: “Through extensive experiments we show that some existing saliency methods are independent both of the model and of the data generating process.” A method can fail that badly and still return a picture the reviewer finds convincing. That is why step four is a test and not an impression.
1. Define the user question
Local decision, global behavior, debugging, recourse, compliance, or communication.
2. Choose the explanation target
Model, data, process, policy, or causal mechanism.
3. Select and constrain the method
Match scope, fidelity, stability, privacy, and actionability.
4. Validate empirically
Use sanity checks, perturbation, known cases, user studies, and alternatives.
5. Connect to action
Specify what the user may conclude, do, challenge, or escalate.
Analogy
A mechanic, driver, and investigator asking different questions
A warning light on a dashboard serves three people badly at once. The driver needs to know whether to pull over, the mechanic needs evidence about a component, and an investigator needs a trace of what happened and what was serviced when.
The light is wired to a sensor that observes the fault. A feature attribution is a second model reporting on the first, which is why two attribution methods can disagree about the same prediction and both look reasonable.
How often that happens, and what practitioners do about it, has been measured. A 2022 paper on the disagreement problem in explainable machine learning ran 30-minute interviews with 25 data scientists, put six state-of-the-art post-hoc explanation methods over four real-world datasets, then ran an online user study with 25 more. 84% of the interview participants reported encountering the disagreement problem in their day-to-day workflow. The resolution was rarely a test: “Furthermore, 86% of our online user study responses indicated that ML practitioners either employed arbitrary heuristics (e.g., choosing a favorite method) or just simply did not know how to resolve the disagreement problem.”
Explanation quality depends on the question, method, fidelity, and action it supports.
Comparison
Feature attribution, Counterfactual explanation, or Process explanation?
Attribution, counterfactuals, and process explanation serve different audiences. The one most useful to an affected person often contains nothing computed by the model at all.
The counterfactual register has a founding example, and it is two sentences long: “You were denied a loan because your annual income was £30,000. If your income had been £45,000, you would have been offered a loan.” Those lines open a section of Wachter and colleagues’ 2018 paper in the Harvard Journal of Law & Technology. Nothing in the two sentences reports the internal logic of the system. A counterfactual describes a dependency on the external facts that led to a decision. The “closest possible world” the authors set out is the smallest change to the world that obtains a desirable outcome.
The process register has a binding instrument. Article 86 of the EU AI Act, Regulation (EU) 2024/1689, is titled "Right to explanation of individual decision-making". Article 86(1) reads: “Any affected person subject to a decision which is taken by the deployer on the basis of the output from a high-risk AI system listed in Annex III, with the exception of systems listed under point 2 thereof, and which produces legal effects or similarly significantly affects that person in a way that they consider to have an adverse impact on their health, safety or fundamental rights shall have the right to obtain from the deployer clear and meaningful explanations of the role of the AI system in the decision-making procedure and the main elements of the decision taken.” The role of the system in the procedure, and the main elements of the decision. No attribution, no saliency map, no coefficient.
Feature attribution
Highlights input contributions under a chosen method.
- Useful for local investigation
- Not automatically causal
- Can be unstable or method-dependent
- Requires baseline and sanity checks
Counterfactual explanation
Shows changes associated with a different outcome.
- Can support recourse and debugging
- May propose infeasible or unfair changes
- Depends on model and causal assumptions
- Needs actionability constraints
Process explanation
Explains system purpose, evidence, rules, review, and remedy.
- Often more useful to affected people
- Does not reveal every model computation
- Supports accountability and contestability
- Can coexist with technical explanations
Key idea
Understandable, and still unfaithful to the model
An explanation can be understandable and still be unfaithful to the model. It can also be faithful to the model while describing correlations that should not guide a decision.
And it can be both and still leave its reader worse off. That is a measured result, not a worry. A sequence of pre-registered experiments put N = 3,800 participants in front of functionally identical models. The models varied only in the number of features and the transparency of the internals. The work was published at CHI in 2021. Participants shown a clear model with few features could better simulate its predictions. They did not follow those predictions more closely than a black-box model's. Worse: “Furthermore, showing participants a clear model meant that they were less able to detect and correct for the model's sizable mistakes, seemingly due to information overload.”
No explanation method answers every audience at once, and none of them establishes why the world produced the outcome in the first place. A reviewer should pair the explanation with a test that it holds, a plain statement of how uncertain it is, and the power to challenge the data and the policy underneath it. The clinician received a chart that was accurate about the model’s average behaviour and silent about the patient in front of them.
Without the power to challenge the data and the policy beneath it, a reviewer only describes the model.
Example
Match the question to the method, then break the match
Take five real stakeholder questions and watch how quickly the method choice stops being a technical one.
- Question-method table: Match five stakeholder questions to an explanation type and a limitation — including the one Article 86(1) actually asks for: the role of the AI system in the decision-making procedure, and the main elements of the decision taken.
- Counterfactual filter: Remove changes that are immutable, unsafe, inaccessible, or institutionally controlled. The £30,000-to-£45,000 sentence is the template, and a candidate survives only if the affected person can move the figure at all.
- Method comparison: Generate two explanation methods for the same case and investigate the disagreement, instead of joining the 86% who employed an arbitrary heuristic or did not know how to resolve it.
- User-action test: Watch whether the explanation supports the intended decision without creating overconfidence. The N = 3,800 experiments are the standing warning: the clearer model left participants catching fewer of its mistakes.
Record the question, the limit, the permitted conclusion
Explanation methods are chosen against a question. So the question asked, what the method cannot do, and what the reader is allowed to conclude from it all belong together in the record.
There is a named standard to write that record against, rather than a house convention. NIST set out four principles for explainable AI in a 2021 report, NISTIR 8312: “We have termed these four principles as explanation, meaningful, explanation accuracy, and knowledge limits, respectively.” A system delivers accompanying evidence or reasons. Explanations are understandable to the intended consumer. Explanations correctly reflect the system’s process for generating the output. And the system operates only under the conditions for which it was designed, and only when it reaches sufficient confidence in its output. Meaningful and Explanation Accuracy are kept apart on purpose, and Knowledge Limits is a principle in its own right. That is the vendor chart’s failure written as a standard. It is the 0.63 area under the curve written as one too.
Set the fidelity, stability, or user-study result that would force the reviewer to redesign, restrict, remedy, or retire the system.
Key takeaways
- Intrinsic, local, global, counterfactual, example-based, and procedural explanations answer different questions, and Article 86(1) of the EU AI Act asks only for the last of them.
- A global summary does not automatically explain an individual output. The Epic Sepsis Model's external validation reports an area under the curve of 0.63 and 1,709 of 2,552 sepsis patients missed, and says nothing about any one alert.
- Feature attribution is not a causal explanation by default. Guided BackProp and Guided GradCAM failed the randomization sanity checks while still returning maps that look like explanations.
- Counterfactuals require feasibility, safety, access, and causal consistency. The closest possible world of Wachter and colleagues is the smallest change to the world that obtains a desirable outcome.
- Explanation methods should be validated for fidelity, stability, and user effect. 84% of interviewed practitioners met the disagreement problem, and 86% of user-study responses resolved it by arbitrary heuristic or not at all.
- Useful explanation includes what the audience may conclude and what action is available. NISTIR 8312 makes Knowledge Limits a principle of its own, separate from being Meaningful.