Explainability
Also known as: explainable AI, XAI, interpretability
How well people can understand why an AI system reached a particular result.
Draft - this entry has not been reviewed yet.
Formal
The degree to which the reasons behind a model's output can be shown in terms a person can follow, for example which inputs weighed most, so that the result can be checked, challenged or corrected.
In plain English
Like a doctor who does not just say "take these pills" but tells you what they saw in your tests and why that led to the choice.
In practice
A citizen whose application for housing support is flagged for rejection by a municipality's AI tool asks why; the municipality can show that missing income papers, not age or nationality, drove the result.
Why it matters
Without it, nobody can spot hidden unfairness, answer an auditor or give an affected person a real reason, so trust and accountability break down.
How to put it into practice
The usual steps, in order. Adapt them to your organisation.
- For each AI system that affects people, write down who needs an explanation (the affected person, the caseworker, the developer, the auditor), what they must be able to do with it, and which rules apply, such as GDPR Arts. 13-15 and 22 and AI Act Arts. 13 and 86.
- For decisions on tabular data, first try an interpretable model such as a scorecard, a shallow decision tree or a GAM, and choose a black-box model only if it is clearly better and you can explain it well enough.
- Pick explanation methods to fit the audience, for example global feature importance for developers and auditors, local attributions such as SHAP for caseworkers, and counterfactuals ("had income been above X, the application would have been approved") for affected people.
- Test that the explanations are faithful before you rely on them, with sanity checks such as randomising the model weights, comparing baselines and checking correlated features, and note their limits as NIST IR 8312 recommends.
- Build the explanation into the workflow, so the caseworker sees the main reasons next to the result and the letter to the citizen states the role of the AI and the main elements of the decision in plain language.
- Document the chosen methods, their limits and example explanations in the technical documentation or model card, and train the staff who have to pass explanations on.
- Review explanations with every model update and sample complaints and appeals to see whether people understood them, then adjust the wording or method.
Common pitfalls
- Trusting a saliency map or SHAP chart because it looks plausible, without checking that it actually reflects what the model does.
- Giving affected people a technical feature list or a trade-secret refusal instead of the procedure and principles actually applied, which the CJEU has said they are entitled to understand.
- Presenting an LLM's chain-of-thought as the real reason for its answer, although it is generated text and not a faithful record of the computation.
Good guides
- NIST IR 8312 - Four Principles of Explainable Artificial Intelligence(opens in a new tab) · NIST
- Explaining decisions made with AI(opens in a new tab) · ICO
- AI Act, Article 86 - Right to explanation of individual decision-making(opens in a new tab) · Future of Life Institute
- Offentlige myndigheders brug af kunstig intelligens - Inden I går i gang(opens in a new tab) · Datatilsynet (in Danish)
Technical deep dive
The literature separates interpretability - models whose structure a person can inspect directly, such as sparse linear models, shallow decision trees, rule lists or generalised additive models - from post-hoc explainability, where a separate method approximates why an opaque model produced an output. Explanations are further classified as global (how the model behaves overall) or local (why this one prediction), and as model-specific or model-agnostic. Rudin (2019) argued that for high-stakes tabular decisions an interpretable model often matches black-box accuracy, making post-hoc explanation of a black box the weaker choice.
The main post-hoc families are feature attribution, example-based and counterfactual methods. LIME (Ribeiro et al., 2016) fits a weighted linear surrogate around the instance using perturbed samples. SHAP (Lundberg and Lee, 2017) assigns each feature its Shapley value from cooperative game theory, the unique attribution satisfying efficiency, symmetry, dummy and additivity; KernelSHAP estimates it by sampling and TreeSHAP computes it exactly for tree ensembles. Gradient methods for neural networks include saliency maps, Integrated Gradients (Sundararajan et al., 2017), which integrates gradients along a path from a baseline, and Grad-CAM for convolutional networks. Counterfactual explanations (Wachter et al., 2017) state the smallest change to the input that would flip the outcome - "had declared income been above X, the application would have been approved" - which is often the most useful form for an affected person.
Failure modes are well documented. Attributions depend on the chosen baseline or background distribution; correlated features split credit arbitrarily; saliency maps can look plausible while being insensitive to the model's weights (Adebayo et al., 2018, "Sanity Checks for Saliency Maps"); and LIME and SHAP can be manipulated so that a biased model appears to rely on innocuous features. For LLMs, a chain-of-thought is generated text and is not guaranteed to be a faithful account of the computation; mechanistic interpretability (circuits, probing, sparse autoencoders over activations) aims at faithful explanations but is still a research field. NIST IR 8312 accordingly lists four principles: explanation, meaningful, explanation accuracy and knowledge limits.
Legally, GDPR Arts. 13(2)(f), 14(2)(g) and 15(1)(h) give data subjects a right to meaningful information about the logic involved in automated decisions under Art. 22. The CJEU held in SCHUFA (C-634/21, 2023) that a credit score can itself be such a decision, and in Dun & Bradstreet Austria (C-203/22, 2025) that the explanation must enable the person to understand the procedure and principles actually applied, without being defeated wholesale by trade-secret claims. The EU AI Act adds Art. 13 (instructions enabling deployers to interpret output), Art. 14 (human oversight) and Art. 86, a right for affected persons to obtain clear and meaningful explanations of certain decisions based on Annex III high-risk systems.
What to learn first
Everything this builds on, foundations first.
- Training data
- →Machine learning
- →Explainability
Relationships
- Part of
- AI governance
- Requires
- Machine learning
- Mitigates
- AI bias
- Mandated by
- EU AI Act
- Used with
- Model cardDecision treeAudit
Sources & further reading
Standards & official texts
Where this data comes from
This entry was drafted by an AI from the sources above and has not yet been checked by a person. Treat it as a starting point, and check anything important against the sources.
See the review queueSuggest a correction on GitHubThis term as JSON
Check yourself
Loading…