Please rotate your phone.

This experience is designed for portrait mode.

AI Product Tools  /  MIF Explorer  /  Library  /  Design System

Truth Layer

Truth Layer

The Truth Layer is the badge system that tells you how trustworthy, directional, or risky a measure is.

Why it matters: It helps teams separate meaningful signals from vanity, misuse, or AI distortion before they optimize the wrong thing.

Example: A metric can be Meaningful, Leading, or Vanity Risk.

Governance Metric Design System DirectionalLeadingMisused

Governance Exception Rate

The percentage of work that requires an exception to the current system, standards, or operating model.

Category: Trust
Measurement class: Governance Metric

Measurement Class

A measurement class tells you what kind of measure something is, not just what topic it covers.

Why it matters: It stops teams from building a stack full of only KPIs while ignoring value, governance, or AI signals.

Example: Governance Metric and AI Signal are two different measurement classes.

Frequency: Monthly
Back to library

Evaluation method

exception_requests / reviewed_work_items × 100

Signal type

leading

What it is best for

Evaluating design system governance fit

What it tells you +

Whether governance standards match real delivery needs or teams are constantly forced around them.

What it does not tell you +

Tell you whether every exception was bad. Some exceptions are healthy signals that the system needs to evolve.

When to use it +
  • Evaluating design system governance fit
  • Finding areas where standards no longer match delivery reality
  • Prioritizing system updates driven by repeated exceptions
When not to use it +
  • As a blunt “compliance” metric without learning from the reasons behind exceptions
How leaders misuse it +
  • Treating every exception as failure instead of a signal that the system may need to adapt
Anti-patterns +
  • Pushing teams to stop requesting exceptions instead of improving the standards themselves
Companion entries +
Instrumentation or evaluation guidance +

Track exception type, requesting team, and whether the exception triggered a system update.

Sample events

exception_requested, exception_granted, system_guideline_updated
Examples +

A system with a 28% exception rate discovered that teams were repeatedly asking for responsive table patterns the governance model did not yet support.

Suggested decisions +
  • If exceptions cluster in one area, update the system rather than repeatedly granting manual approvals
  • Track which exceptions create permanent improvements versus one-off bypasses