One question tests most of what this site argues. Would this institution still look successful if the people around it stopped saving it from itself?
A hospital keeps delivering care, an office keeps processing claims, a team keeps meeting its targets, and the outcome is read as the institution’s competence. Often part of it is the work of people who catch errors, chase referrals, re-enter data, absorb delays and remember what the system forgot. The institution records the outcome and the work behind it goes unrecorded. The site’s terms for this are compensated performance and the falsified denominator. This essay asks what to do once the work is seen: treat the burden as a placement that can be changed.
From adaptation to allocation
Critique usually stops at the observation that people are carrying too much. The more useful question is why a burden sits with these people and not somewhere else in the system. Asked that way, the burden stops looking inevitable. The sequence runs from suffering, to a burden, to compensating work, to a function the system relies on, to the design choice that put the function there, and then to a target for redesign.
No system can remove all difficulty. Each one decides where difficulty lives.
- A health system can put complexity in its own coordination or in the patient’s life.
- A software company can put it in product design or in users’ workarounds.
- An agency can verify eligibility from records it already holds or make people prove themselves again.
- An employer can keep spare capacity or make workers absorb every fluctuation.
- A safety system can be built to tolerate error or can depend on permanent human vigilance.
Someone has to remember, coordinate, absorb uncertainty, detect errors, recover when a forecast fails and carry spare capacity. The question stops being how resilient people should become. It becomes which layer of the system should absorb this disturbance: the institution, its technology, or the person.
Misplaced computation
Much of what people do to get through an institution is computation done by hand. They integrate fragmented information, keep track of state across interactions, spot anomalies, reconcile rules that conflict, anticipate failures, handle exceptions, route problems to the right desk, settle ambiguous cases and remember what the institution forgets.
The work goes by other names: navigation, advocacy, professionalism, resilience, life admin. Functionally it is processing, misplaced computation being done inside human lives instead of by the institution whose structure generates it. The problem is not only that people are tired. The architecture may be assigning tasks to the wrong subsystem.
What looks natural, and what is designed
| What looks natural | What may be designed | What it could be redesigned as |
|---|---|---|
| Some people are better at navigating systems | Complexity, fragmentation, documentation demands, opaque procedures | Fewer handoffs, automatic coordination, default enrollment |
| Good workers go above and beyond | Understaffing, missing redundancy, poor escalation | Slack, backup capacity, explicit exception handling |
| Patients need to advocate for themselves | Fragmented care and records | Shared records, accountable coordination, proactive follow-up |
| Customers need to read the fine print | Strategic complexity, asymmetric information | Standard terms, meaningful disclosure, safer defaults |
| Applicants need persistence | Administrative burden working as rationing | Automatic eligibility, presumptive access, the burden of proof on the institution |
| People need resilience | Repeated exposure to preventable instability | Predictable schedules, staffing reserves, protected recovery |
| Users need better digital literacy | Products that hand interpretation and error correction to the user | Reversibility, constrained failure modes, clearer interaction design |
| Workers need to catch mistakes | Safety that depends on vigilance | Error-proofing, forcing functions, redundancy |
| People should leave bad systems | Lock-in, switching costs, irreversible consequences | Portability, interoperability, exit rights, transition support |
| Feedback exists | Feedback without authority or closure | Escalation that closes, with a named owner for the correction |
| The system is efficient | Costs shifted past the accounting boundary | Full-cost accounting and burden-adjusted measures |
| Failure is rare | Failures absorbed before they reach the metric | Counting near misses, compensating work and recovery labor |
Several things usually treated as properties of people are partly properties of systems. Resilience depends on how much disturbance reaches a person. Demands on executive function depend on how many things a person must remember, sequence and check. Stress depends on unpredictability, reversibility and time pressure. The persistence a process requires depends on how many gates stand between a person and an outcome. Powerlessness depends on the distance between the person who meets a problem and the authority that could fix it. Even apparent competence is shaped this way: one person looks unusually capable because the environment demands heroic compensation, another looks incapable because it demands skills unrelated to the task.
Productive and compensatory difficulty
Removing all friction is not the goal. Some friction protects people, some redundancy is necessary, and some judgment cannot be automated away.
Productive difficulty belongs to the activity itself: learning mathematics, raising a child, making a hard clinical judgment, making something new. Learning research has a name for one form of it, desirable difficulty, in which effort is part of how the skill is built.
Compensatory difficulty exists because the surrounding arrangement is badly built: entering the same data five times, spending hours finding out who has authority, correcting predictable errors, waiting at arbitrary gates, supplying coordination nobody else provides.
The first is worth keeping. The second is a workaround the institution has made routine, and it is the target.
The responsibility line
Every arrangement draws a line somewhere between what the institution handles and what is left to the person.
institutional responsibility | personal responsibilityMove the line toward the institution’s side and the person compensates more. Move it the other way and the institution absorbs more of the complexity it creates. Much of politics can be read as a dispute over where this line sits, and the responsibility line is a design decision like any other. The point at which an institution’s failure becomes somebody’s personal problem was chosen. It can be stated, reviewed and moved.
Where the control loop breaks
Five questions locate the break. Who observes the failure? Who lives with its consequence? Who has the information to diagnose it? Who has the authority to intervene? Who pays for the correction? When those are different people, the institution has a feedback problem, the condition insulation describes.
The usual response to a bad outcome is to compensate the person harmed. The redesign response traces the mechanism that generated the outcome, reconnects the consequence to the authority that can change it, rebuilds the feedback, and prevents the next instance. It is more constructive and more demanding, because it names something to change.
Substitution, not abolition
The aim is not to abolish the functions people are performing. The patient coordinating five specialists is doing necessary work. Coordination stays. What changes is who does it and how. The nurse who catches errors is doing quality control. Quality control stays, built into the process instead of resting on permanent vigilance. The applicant proving eligibility is doing verification. Verification stays, and the question becomes whether the institution already holds the information and can carry the burden itself.
So redesign has a sequence. Identify an avoidable burden. Name the function it performs. Design a mechanism that performs the function better. Move the function upstream to the layer with the capacity and the authority to perform it. Then retire the human compensation, and check that it does not reappear somewhere else.
Theory, drawn
The same functions on either side of the line
Someone has to coordinate, verify, catch errors, remember, absorb fluctuation and route problems. The responsibility line decides whether a person does it by hand or the institution and its technology do it. Moving the line moves the functions. It abolishes none of them.
A specification
“People should not have to work this hard” can sound sentimental, and it is easy to dispute. The same point stated as a requirement is harder to wave away: a system should not rely on costly human compensation for failure modes that are predictable, recurring and could be engineered out.
Stated as a design objective, the aim is to minimize compulsory adaptation, coordination burden, vigilance burden, irreversible error, unnecessary switching cost and recovery labor, and to maximize reversibility, observability, corrective authority, institutional memory, usable exit, and slack held for genuine uncertainty. The constraints are that agency, useful human judgment and the capacity to respond to the unexpected are preserved at an acceptable cost.
Questions that change
| The usual question | The question once the burden is a design choice |
|---|---|
| Why can’t people cope better? | Why was coping chosen as the control mechanism? |
| Why aren’t users better informed? | Why does safe participation require extraordinary information processing? |
| Why did this worker burn out? | Why was depletion part of the operating model? |
| Why did this family fail to navigate the system? | Why was the family doing the institution’s coordination? |
| This is what dealing with healthcare is like. | Which design decisions make healthcare require this much navigation? |
| Some jobs are stressful. | Which uncertainties has this organization passed straight to its workers? |
| People need executive-function skills. | Why does ordinary participation demand this much executive function? |
Treating a burden as part of life protects the arrangement that produces it, because there is nothing to redesign. Treating it as architecture means someone can be asked why the architecture looks the way it does.
Weak, strong and maximal
The argument can be held at three strengths, and it matters which one is in play.
| Form | Claim | Typical intervention |
|---|---|---|
| Weak | Institutions should reduce unnecessary burden on people where they can. | Shorter forms, fewer handoffs, safer defaults, clearer escalation, lower cognitive load |
| Strong | Where adaptation, vigilance, uncertainty and corrective work are allocated is a design problem, technical and political at once. | Redraw the system boundary, move responsibility upstream, count the hidden inputs, change authority and feedback |
| Maximal | An institution’s legitimacy depends partly on whether it turns human adaptability into invisible infrastructure while denying people the authority to change the conditions that consume it. | Standing for the people doing the compensating, and the power to withhold it |
The weak form fits inside human-centered design, accessibility, human factors and administrative-burden reduction, and it asks good questions. It leaves the architecture in place. A weak intervention makes prior authorization easier to navigate. A strong one asks why a patient or clinician is doing coordination work that insurer fragmentation created. A weak intervention improves the appeals portal. A strong one asks why correction comes after the fact, at the claimant’s cost and initiative, instead of being built into the original decision.
The strong form also changes evaluation. Two institutions can produce the same outcome, one from its own formal capacity and the other from formal capacity plus unpaid coordination, vigilance, family labor and overextended staff. The weak form says the second should reduce some of those burdens. The strong form says the two should not be credited with the same performance. Efficiency claims should count hidden compensation, resilience claims should say whose reserve is being spent, automation claims should include the downstream correction they create, access claims should include the work of converting formal access into a result, and choice claims should include the cost of exit.
The maximal form brings in power, and it is where this site’s argument about dependence without standing lives. A person who carries the burden, lacks the authority to remove its cause, and whose coping hides the failure is in a relation of domination, in the sense republican political theory gives the word. In its strongest form: an institution is badly designed when its apparent competence depends on consuming human adaptability it neither measures, replenishes, nor lets people withhold.
Burden-adjusted value
The strong form implies a change in how value is counted, which this essay sketches without claiming a finished theory.
Conventional accounting asks what was produced, at what monetary cost, and for whom. The further questions are what human capacity the arrangement consumed, who supplied it, whether they did so voluntarily, whether it can be replenished, and whether the same outcome could have come with less compulsory adaptation. Vigilance, patience, executive function, emotional regulation, persistence, coordination, tolerance of uncertainty, schedule flexibility and recovery are capacities people have. Institutions can also use them up, and when they do, they are inputs to production whether anyone pays for them or not.
Three consequences follow.
- Value has a counterfactual. An arrangement is judged partly by the gap between the human burden it actually imposes and the least burden reasonably needed for the same result. That gap is avoidable adaptation, institutional waste measured in people’s time and stamina.
- Productivity claims need the full denominator. A tool that removes twenty minutes of formal work and creates thirty minutes of checking, correction and exception handling downstream has not raised productivity. It has reclassified an input. The units of these inputs differ and some should never be priced, so the useful demand is that a claim state which inputs it counted.
- Some activity creates burdens and sells their relief. Measured revenue cannot tell a firm that solves a problem from one that creates a problem people must then pay to manage. Counting the burden alongside the product can.
The positive form is the one the essay on the consumption of adaptive capacity ends on. An arrangement creates value by producing goods and capabilities, and also by reducing how much human life must be spent, involuntarily, compensating for deficiencies that could have been prevented. Freedom enters the account too. Of two arrangements that deliver the same outcome, the one that leaves people able to refuse, contest, revise and leave is worth more. The capability approach and republican freedom both point this way. What this framework adds is attention to how dependence and compensatory demand are engineered.
What the laws take from this
- Law III: evidence and authority must stay coupled. A control loop in which the person who sees the failure cannot act on it has decoupled them.
- Law IV: every consequential delegation creates a correction obligation. Moving a function upstream is how an institution meets that obligation instead of passing it to the people it serves.
- Law VII: error-bearing parties need standing proportional to exposure. The people performing compensating work are the first to know where the responsibility line sits, and the last to be asked.
- Law XII: no system may erase the conditions of its own contestability. A system that runs on unrecorded compensation erases the evidence a challenge would need.
Many institutions have solved their own complexity problem by exporting it into people’s lives. Redesign means pulling that complexity back inside the parts of the system with the capacity and the authority to manage it, and keeping human adaptability for the uncertainty no design can remove.