Independent public-interest evaluations of how systems respect dignity and support agency.
HXR Documentation
Why Organizations Should Want HXR
How HXR Evaluations make good experiences and areas for improvement visible, connect dignity and agency with organizational performance, and help successful practices spread.
Organizations already compete on price, speed, quality, reliability, convenience, expertise, trust, and innovation.
HXR gives organizations of every size another dimension on which to improve and, where valid comparison exists, compete: respect for human agency, human time, and human dignity.
HXR examines what helps people understand, choose, act and recover across good, difficult and mixed experiences. Its main analytical artifacts are Evaluations, supported by bounded Incident Cases and other evidence. An Evaluation can recognize an effective practice, explain where it works and for whom, identify limits, and track whether the benefit lasts. An organization does not need to have failed first for its good work to merit attention.
HXR Examines the Complete System
Depending on the domain, that may include policies, staffing, incentives, records, queues, forms, handoffs, physical spaces, legal processes, customer support, procurement, software, and automation.
Responsibility Should Scale With Capability
Organizations often possess capabilities no individual customer, patient, worker, student, resident, or supplier can match, including greater information, continuity, staffing, automation, expertise, legal resources, authority, and the ability to redesign the process.
That greater capability creates greater responsibility. Organizations should carry burdens they are better equipped to handle rather than transferring coordination, recordkeeping, explanation, error correction, and responsibility routing downstream.
Correct Attribution Benefits Organizations Too
HXR should not preserve blame merely because an organization was named first. If evidence shows that a different party controls the relevant mechanism, HXR should correct the attribution.
An organization that says “not us” should help make that claim testable by identifying what it controls, who it believes does control the issue, why, and what path reaches that party. A supported reattribution can remove unfair blame while preserving any separate responsibility for disclosure, coordination, handoff quality, or remedy.
Good Experiences Can Benefit Both Sides
When people can understand their options, obtain clear updates and accomplish their objectives with appropriate support, they retain more control over the interaction. The same practices can help an organization avoid unnecessary repeat contacts, reduce staff rework, and give customers clearer reasons to trust and choose it. HXR can make that connection inspectable: what the person experienced, what practice enabled it, and what organizational benefit the evidence supports. Commercial outcomes such as retention or lower costs remain potential benefits until there is evidence to establish them.
Better Experience Can Lower Operating Cost
A workflow designed around successful resolution can reduce repeat contacts, transfers, escalations, staff rework, avoidable exceptions, refunds, complaints, churn, regulatory exposure, employee burnout, and queue pressure.
A short contact that fails may cost more than a longer contact that permanently resolves the objective. Organizations should measure total resolution time, repeat-contact burden, and resolution yield rather than rewarding only short handle time or visible queue reduction.
Benchmarking Can Become Shared Infrastructure
HXR does not need to make “becoming a benchmarking organization” its identity objective. If it accumulates rigorous, comparable evidence about human outcomes and verified reforms, benchmarking becomes a consequence of that knowledge.
Organizations should be able to learn what peers have demonstrated, what analogous systems in other domains have solved, which constraints are genuinely different, and which reforms have been verified. A successful practice should not have to remain trapped inside the organization that discovered it.
Peer comparison requires material comparability. Cross-domain comparison can provide comparative capability evidence and useful questions without pretending that different technical systems are equivalent.
Participation Without Capture
Organizations may comment, provide evidence, challenge errors, explain legitimate constraints, identify responsible parties, propose reforms, share successful practices, and help test standards.
They do not receive a right to approve a supportable public comparison. HXR comparisons should be contestable through evidence and method, not consent-dependent. If an organization's counterevidence shows that HXR is wrong, HXR should correct the finding.
Organizations may not buy a better result or hidden criteria. Improvement must come from changing the evidence, correcting an error, demonstrating a legitimate constraint, or improving the human outcome rather than influencing the ruler.
Good Practice and Verified Improvement Deserve Credit
HXR should recognize both organizations that already handle people well and organizations that improve. Credit belongs to the demonstrated practice, system, team or implementation within the limits of the evidence. An Evaluation can preserve what worked, record what changed, and explain what another organization would need to reproduce the benefit.
Documented good practice can help people make informed choices and give organizations a credible account of the work worth maintaining and sharing. Later evidence may strengthen, narrow or revise that account. Recognition remains independent and open to correction.