Independent public-interest project · Scientific framework under active development · Live public pilot
UXR Documentation
UXR Research Notebook
Document status: Living development notebook
First published: August 4, 2026
Authority level: Development record, not constitutional authority
Purpose
The UXR Research Notebook records significant discoveries, questions, rejected assumptions, and methodological changes while the framework develops.
Notebook entries do not become official UXR doctrine merely because they appear here. A notebook entry may describe a hypothesis, working term, communication discovery, unresolved conflict, or proposal that later changes or is rejected. Formal authority remains with the current constitutional and methodological documents.
August 4, 2026: Burden can remain real without conscious friction
Different people recognize system burden differently. One person may spend hours challenging an outcome. Another may accept the first result because prior experience makes correction appear exhausting, uncertain, or pointless.
Discovery: complaint volume and self-reported frustration do not directly measure burden. A system may appear frictionless because people have learned not to ask it for outcomes they expect will be difficult to obtain.
Working concepts: Anticipated Burden, Burden Avoidance, Adaptive Acceptance, and Unexpressed Objective Loss.
August 4, 2026: Onboarding must include lost outcomes, not only visible fights
People who actively resist a system recognize themselves in stories about long phone calls, repeated escalation, and administrative struggle. Other people recognize delayed care, an unrepaired device, a missed appointment, or an accepted answer that should never have been final.
Decision: UXR onboarding should include active resistance, passive constraint, hidden failure, and proxy burden.
August 4, 2026: Population averages must show distribution
“One minute per person per day” can be misunderstood as one minute taken from every person every day.
Decision: describe population-level estimates as averages across people and time. Publish the distribution, concentration, population, period, baseline, assumptions, and uncertainty whenever possible.
August 4, 2026: Not every failure creates institutional savings
A broken workflow can consume customer time and paid institutional labor simultaneously through repeat contacts, transfers, rework, queue pressure, and unresolved outcomes.
Discovery: Shared Inefficiency is a necessary companion to Shared Efficiency and Extractive Burden Transfer.
Working measures: Contact Time, Total Resolution Time, Repeat-Contact Burden, and Resolution Yield.
August 4, 2026: Small burdens can produce large cascades
Traffic signal timing demonstrated that one delay can produce additional fuel use, emissions, braking, acceleration, vehicle wear, road wear, attention demands, maintenance costs, and reliability effects.
Working concept: Burden Cascade.
Decision: UXR should examine repetition scale and cascading scale separately.
August 4, 2026: Time is a flagship metric, not the whole project
Time is intuitive, finite, measurable, and aggregatable. It cannot replace health, safety, dignity, access, opportunity, environmental effects, recovery, or practical agency.
Decision: pair Human Time with Human Outcome in public onboarding.
August 4, 2026: Audience architecture and public on-ramps
Perspective reviews and public-documentation work showed that different audiences recognize UXR through different values and professional habits. Researchers look for truth and testability. Journalists look for provable public evidence. Auditors look for repeatable failure detection. Operations specialists see transferred work. Clinicians see delayed care and administrative harm. Public-interest readers see practical freedom and dignity.
Discovery: UXR should remain one framework while offering multiple accurate entrance ramps. Communication may adapt to the audience without changing the underlying standard.
August 4, 2026: Universal scope clarification
Multiple independent reviews initially described UXR as a framework for software, technology, applications, or machine interfaces, even when their later analysis covered healthcare, government, courts, organizations, and physical systems.
Decision: revise the opening documentation to state immediately that UXR examines all human-made systems.
August 4, 2026: Responsibility scales with capability
A recurring principle emerged across very different perspectives: institutions are stronger than individuals in the dimensions that matter for administration. They possess records, continuity, staff, automation, legal resources, authority, and redesign capacity.
Decision: formalize the principle that responsibility should scale with capability.
August 4, 2026: Interpretive Stress Testing
Character and perspective reviews became useful only when UXR stopped treating them as endorsements or authoritative readings. A perspective may identify a real defect, reveal a communication problem, or simply impose its existing worldview.
Decision: distinguish correctly recovered principles, communication discoveries, reasonable misunderstandings, documentation ambiguities, framework proposals, lens-imposed conclusions, and character-specific rhetoric.
August 5, 2026: One incident may require multiple cases
Live cardiology-referral analysis demonstrated that one contributor narrative can contain multiple failure mechanisms with different responsible functions, harms, corrective paths, and resolution timelines.
Decision: case boundaries should preserve independent accountability. Related cases may remain grouped under one incident without forcing every failure to stay open until every other failure resolves.
August 5–6, 2026: Case infrastructure moved from planned to operational
UXR created structured operational records for intake, boundary decisions, work orders, cases, evidence, assessment, activity, resolution, public publication, taxonomy, routing, and related functions.
Decision: describe this capability as a bounded operational case pilot. Do not continue describing case architecture and publication as merely planned, but do not confuse a working pilot with broad public intake or validated large-scale operations.
August 6, 2026: Public cases expose maturity drift in the documentation
Interpretive stress tests continued to criticize UXR for lacking live cases even after public cases existed. The criticism was no longer primarily about missing capability; it revealed that project-status documents had fallen behind the actual implementation.
Decision: current-status, roadmap, maturity, and reviewer-facing materials should draw from live operational data where practical. A project that changes quickly needs status surfaces designed to change with it.
August 6, 2026: Time is evidence, not the whole objective
Repeated interpretive reviews naturally centered the Human Time Dividend because time is intuitive and measurable. That created a risk that readers would misread UXR as a time-and-motion or efficiency framework.
Discovery: time can function as observable evidence of a deeper loss without becoming the purpose of reform. Agency, dignity, safety, understanding, opportunity, and human capacity remain core outcomes.
Working framing: time is one visible footprint of what a system consumed; the framework must preserve the distinction between measurable cost and human outcome.
Copyright © 2026 Sean Arenas. User Experience Reform (UXR). All rights reserved. Notebook entries may be cited with attribution but should not be represented as final UXR standards unless incorporated into an authoritative document.