User Burden Ratio — Operational test: Teams can point to a concrete example that demonstrates user burden ratio in practice.
Operational test "Teams can point to a concrete example that demonstrates user burden ratio in practice." for User Burden Ratio in the Measures & indicators glossary category.
Operational test
Teams can point to a concrete example that demonstrates user burden ratio in practice.
Use this test to validate operational readiness.
Pair this test with the minimum evidence criteria to capture both qualitative and quantitative signals.
- Evidence artifact: Artifact documenting how User Burden Ratio is expected, enforced, or governed.
- Behavior signal: Observed behavior showing User Burden Ratio in practice during real use or drills.
- Metric signal: Metric tracked to monitor User Burden Ratio performance over time.
How much work a user must perform to correct or navigate system errors. This metric feeds directly into fair burden distribution . Interpretation: UBR must be evaluated against the Evidence Burden Ceiling (documentation) plus time/steps caps (process). Targets & breach behavior. Measurement window: weekly median; monthly p95. Target / floor / ceiling: target ≤ 10 minutes, ≤ 5 steps, ≤ 2 documents; floor ≤ 15 minutes, ≤ 8 steps; ceiling 20 minutes / 10 steps. Owner: Traceable Ownership (must have). Breach action: switch to burden inversion , offer staffed alternatives, or trigger safe pause . Public surface: receipt + time transparency + decision artifact showing burden caps.
G. Measures & indicators. Metrics that track moral performance across systems.
Ethotechnics uses User Burden Ratio to extend the g. measures & indicators vocabulary and connect governance, design, and policy teams.