Responsibility, Capability, and Institutional Asymmetry

Status: Development Notes — Published for Review

Responsibility should scale with capability and consequential power.

Institutions commonly possess capabilities that individuals do not: persistent records, operational continuity, staffing, automation, specialized expertise, legal resources, money, formal authority, and the power to redesign or govern systems that affect human lives.

That asymmetry does not make an institution malicious. It does create responsibilities that an individual may be unable to carry safely, efficiently, or at all.

Condition, Intent, Culpability, and Responsibility Are Different Questions

UXR should first establish what the evidence supports about the condition. A harmful or burdensome condition does not automatically prove malice, negligence, exploitation, indifference, or any other motive or mental state.

Intent matters to culpability. It does not determine whether a supported condition exists, whether corrective responsibility exists, or whether reform should be investigated.

An affected person should not have to diagnose the moral or psychological state of an institution before the condition can be taken seriously. UXR can recognize the condition, investigate necessity and cause, identify relevant responsibilities, and pursue correction while keeping motive unresolved when the evidence does not establish it.

The Proportionality Principle

The side better equipped to perform coordination, recordkeeping, explanation, correction, risk management, continuity, or responsibility routing should carry proportionally more of that burden.

An institution should not require a person to reconstruct records the institution already holds, coordinate departments the institution controls, repeatedly prove facts the institution already verified, or reverse-engineer a multi-party system merely to find the entity capable of acting.

Consequential Institutional Power

Some institutions exercise substantial consequential power over human lives through access, authorization, infrastructure, payment, employment, housing, care, mobility, enforcement, communication, or remedy. The greater that capability, the stronger the stewardship responsibility to understand the human consequences of the system and maintain credible ways for affected people and evidence to reach corrective authority.

“Nobody told us” may explain a lack of awareness. It does not by itself answer whether the institution maintained effective mechanisms through which people could tell it.

Responsibility Is Often Layered

“Who is responsible?” can be too simple for a multi-party system. UXR may need to distinguish several responsibilities:

• Experienced-system responsibility: who the person reasonably understood themselves to be interacting with.
• Mechanism responsibility: which component or process produced the condition.
• Control responsibility: who has authority or technical capacity to change that mechanism.
• Policy responsibility: who chose or governs the rule under which the mechanism operates.
• Coordination responsibility: who is best equipped to move the issue across organizational or departmental boundaries.
• Disclosure responsibility: who knew or reasonably should have known about the limitation and could have explained it before the failure.
• Remedy responsibility: who can provide correction, restoration, accommodation, authorization, reimbursement, or another appropriate result.
• Governance responsibility: what regulator, legislature, standards body, contract structure, network authority, or other governing layer can address a failure that persists even when local actors follow their own rules.

These responsibilities may belong to different parties. Correct attribution of one responsibility does not absolve every other participant from every role.

“Not Us” Is an Attribution Claim

When an organization named in a case says that the relevant failure is controlled elsewhere, UXR should not automatically accept or reject the statement. It should treat the statement as a testable attribution claim.

A useful denial of responsibility should identify, to the extent reasonably known, what the organization controls, what it does not control, who it believes controls the disputed mechanism, why it believes that, what evidence supports the attribution, and what usable path reaches that party.

If the evidence supports reattribution, UXR should correct the case. Accurate reattribution can remove unsupported blame from the initially named organization while preserving any separate responsibility it had for disclosure, coordination, handoff quality, or remedy.

If two institutions point to each other, the conflict is not a reason to abandon the case. It becomes conflicting causal evidence to investigate. If responsibility remains unresolved after reasonable inquiry, UXR should say so rather than manufacture certainty.

Navigation Burden Can Be Its Own Failure

A person may encounter one underlying failure and then a second failure: no reliable way to determine who owns correction. The resulting calls, transfers, repeated explanations, record reconstruction, jurisdiction discovery, and responsibility mapping are human burdens even when every participant accurately describes its own limited authority.

Institutions may transfer internal responsibility without transferring the navigation burden. Where practical and lawful, a humane handoff should preserve context, explain the dependency, identify the next responsible party, and move the issue toward the place capable of resolving it rather than forcing the person to restart.

Fragmentation and Asymmetry

Fragmented responsibility can create an asymmetric institutional advantage because the affected individual bears the cost of determining ownership while each participating institution can limit its involvement to a local boundary. That structural effect can exist regardless of whether any participant intended to create or exploit it.

At scale, UXR can reduce that asymmetry by allowing substantially matching experiences to contribute to one bounded evidentiary record while UXR investigates the responsibility chain. Many affected people should not each have to become amateur investigators of the same institutional architecture.

Constraint Provenance

When a burden is defended with “we cannot,” UXR should ask what produces the constraint. Possible sources include physical reality, safety, the rights of others, law, current technology, architecture, contracts, policy, risk tolerance, cost or resource allocation, organizational priority, or inherited practice. These sources do not carry the same reform path.

A constraint imposed by one layer may be genuine for a front-line actor while remaining corrigible at a governing layer. UXR should trace the constraint to the level at which human decision can meaningfully affect it.

Forms of Institutional Asymmetry

• Information asymmetry: one side knows the rules, evidence, or status while the other does not.
• Record asymmetry: one side controls the authoritative history of the interaction.
• Continuity asymmetry: the institution persists while the person must remember, save, and reconstruct.
• Expertise asymmetry: the institution understands its own systems, terminology, procedures, and boundaries.
• Time asymmetry: the institution can often wait longer than the person facing a deadline, illness, lost income, or urgent need.
• Power asymmetry: the institution may control access, authorization, enforcement, payment, employment, housing, or remedy.
• Responsibility asymmetry: the institution can understand or navigate a responsibility map that the affected person cannot reasonably be expected to reconstruct.

Capability Does Not Rank Human Worth

A surgeon's hour may be harder to replace operationally than another worker's hour. That does not make the surgeon a more valuable human being. UXR may account for scarce expertise, opportunity cost, and system risk without ranking inherent human worth.

Question for Review

How should UXR distinguish mechanism, control, policy, coordination, disclosure, remedy, and governance responsibilities without making the responsibility map itself another burden for the affected person?