In product and UX, the framework’s claim becomes: a system fails legitimacy when “available” paths are unusable under ordinary fatigue, confusion, and time pressure.
Common misdescription in this field
Feature exists = problem solved
Teams equate surface availability with usability.
- Path is technically present but discoverability is low.
- Recovery requires detective work.
- Exit rates are treated as user preference.
User error = user failure
Users are left to decode jargon and unclear rules.
- Ambiguous copy creates avoidable mistakes.
- Users must infer policy from edge-case behavior.
- Support scripts keep the policy opaque.
What to measure instead
Measure whether people can complete the path and get repair under stress.
Recourse clarity: can users identify the next recoverable step quickly?
Instrument resolution pathways, not just funnel starts.
Burden count: how many steps to restore baseline function?
Count repeats, redirects, and handoffs needed for correction.
Interpretive load: how much translation is required?
Test with ordinary users under realistic stress and partial attention.
Typical failure pathway (how people fall out)
Friction accumulates
User hits ambiguous state, cannot confirm risk, and retries.
Recourse opacity
Help channels route to scripts that cannot resolve the specific case.
Silent exit
Drop-off is logged as churn while design burden stays unmeasured.
Design/legal/operational fixes
Fixes must be structural and testable.
Design fix: make reversal first-class
Prioritize undo, rollback, and human escalation from every risky action.
Operational fix: resolution SLAs
Track time-to-repair and unresolved loops as core quality metrics.
Legal fix: usable rights language
Expose appeal rights and deadlines in plain language at decision points.