The Blue Book of UX Directives
7. Trust, Safety & Responsibility

2. Transparency

Why systems behave as they do.

First, ask yourself

“Can users of your system understand and influence behavior when needed?”

Mission statement

Ensure users understand system behavior by making processes and outcomes visible.

Key heuristics Transparency

  1. Transparency must enable trust and user intervention.
  2. Explanations must provide sufficient detail for informed decisions without excess.
  3. Inputs, triggers, and outcomes must be traceable.
  4. Confidence indicators must reflect actual reliability.
  5. Higher-consequence outcomes must receive deeper explanation.
  6. Explanations must be accompanied by meaningful correction mechanisms.
  7. Explanations must simplify without misrepresenting behavior.
  8. Explanations must appear before or during consequential impact.
  9. Explanations must exclude unnecessary technical detail.

Executive brief

The system must ensure its behavior is understandable and controllable.

Core questions Transparency

“Is the system understandable enough to be trusted and correctable?”

“Can users see what is happening and fix it when it is wrong?”

Focus areas

Understanding-first

“Can users explain what the system is doing? Do they know why?”

“Is cause-and-effect visible, not just inferred?”

Action-first

“What can users do when they disagree with the system?”

“Can corrections be made without escalation or special expertise?”

Risk-aware

“Is opacity minimized and proportional to risk?”

“Are critical decisions more transparent than trivial ones?”

AI-aware

“Does the system reveal uncertainty and limits?”

“Are explanations faithful to actual behavior?”

UX directives Transparency

Directive72/01

Design transparency to support trust and intervention.

Ensure explanations empower user correction, not passive observation.

Directive72/02

Provide decision-relevant clarity.

Deliver explanations sufficient for informed action without overwhelming detail.

Directive72/03

Expose causal relationships.

Make inputs, triggers, and outcomes traceable.

Directive72/04

Communicate uncertainty proportionally.

Align confidence indicators with actual reliability.

Directive72/05

Increase explanatory depth for high-risk outcomes.

Provide greater insight where stakes are higher.

Directive72/06

Enable correction mechanisms alongside explanation.

Pair visibility with meaningful user action.

Directive72/07

Ensure explanatory accuracy with simplicity.

Simplify without misrepresenting system behavior.

Directive72/08

Deliver explanations at the point of impact.

Provide visibility before or while a consequence unfolds, not after.

Directive72/09

Curate explanations for relevance.

Do not overwhelm users with unnecessary technical detail.

Executive summary

  • Transparency is actionable clarity, not passive disclosure.
  • It reveals causal relationships so users can understand inputs, triggers, and outcomes.
  • The system must provide decision-relevant explanations aligned with actual reliability and uncertainty.
  • Explanatory depth must scale with risk and appear at the point of impact.
  • Visibility must be paired with meaningful correction or intervention mechanisms.
  • Transparency succeeds when users can interpret system behavior accurately and act on it confidently.

Success indicators

  • Users can see how system actions lead to outcomes.
  • Important inputs, triggers, and results are visible.
  • The system communicates uncertainty clearly.
  • Explanations appear when they are relevant to user decisions.
  • Users can act to correct or adjust outcomes.

One-line summary

Before users can rely on a system, they must be able to understand what it is doing and why.