This essay states the positive framing of the discipline. The companion essay on what Ethotechnics is not draws the boundary by retiring a vocabulary; this one states the same discipline as a design practice, and the essay on what outcomes hide draws out its evaluative consequence. Where the mechanism essays treat a law or a channel, this one treats the designer’s stance toward the people an arrangement touches.
Ethotechnical design treats human adaptive capacity as finite and politically consequential. It asks not only whether an arrangement works, but what kinds of adjustment it demands from people, who bears those demands, and whether the bearers can force the arrangement itself to change.
The allocation of adaptation
The starting assumption is that every design is an imperfect model of reality. A form, a workflow, a building, an algorithm, a rule, an interface, or an institution establishes expectations about the people and situations it will encounter. Inevitably, some reality will not fit.
The ordinary design question is: how do we make people interact successfully with this system? The ethotechnical question inverts it: when the system and the person do not fit, why should the person be the thing that changes?
That makes the discipline fundamentally concerned with the allocation of adaptation:
design → mismatch → adaptation requirement → allocation of that requirement
A badly designed arrangement systematically pushes that final term downward. Users remember passwords. Patients coordinate providers. Workers repair software. Disabled people request exceptions. Citizens reproduce information government already possesses. Caregivers integrate fragmented services. The arrangement remains stable because human beings become flexible around it.
Ethotechnical design reverses that presumption:
Spend institutional capacity before consuming human adaptive capacity.
That does not mean people should never adapt. Learning, cooperation, compromise, care, and collective life all require adaptation. The distinction is between productive or reciprocal adaptation and compensatory adaptation: human effort required primarily because an arrangement has failed to accommodate foreseeable reality.
Four moves
The designer works through four moves.
First, eliminate the demand where possible. Before improving a form, ask whether the form needs to exist. Before making compliance easier, ask whether compliance is necessary. Before designing an accommodation process, ask whether the default could accommodate more variation.
Second, absorb complexity upstream. Where complexity is necessary, place it where there is the greatest capacity to handle it. Institutions can integrate databases, coordinate departments, hire expertise, maintain infrastructure, automate repetitive tasks, and learn across cases. Isolated individuals usually cannot.
Third, design for the remainder. No arrangement will anticipate everyone. Exceptions are not necessarily evidence of bad design; they are inevitable. Ethotechnical design therefore includes low-cost exception handling, human judgment, escalation, reversibility, appeal, and the ability to operate when the model encounters something it did not anticipate.
Fourth, make repeated mismatch capable of redesigning the system. This is what separates accommodation from corrigibility. If thousands of people need the same exception, the system should not become extraordinarily efficient at processing thousands of exceptions. It should become capable of asking whether the rule generating them is wrong.
The fourth move is the one that binds the loop:
mismatch → visible burden → standing → correction → redesign → institutional memory
Unfinished design
The four moves presuppose that design is deliberately unfinished. The designer rejects the fantasy that sufficiently intelligent anticipation can eliminate mismatch. A conventional designer can treat the specification as authoritative and the exception as deviation. The ethotechnical designer treats the specification as a hypothesis and the exception as possible evidence.
That produces a different relationship to failure. When users repeatedly work around something, the workaround is not simply clever user behavior; it is diagnostic evidence. When frontline workers continually exercise unofficial discretion, that may indicate that the formal process is inadequate rather than that the workers are flexible. When disabled people repeatedly request the same accommodation, the question is not merely how efficiently the requests can be processed but what the requests reveal about the default.
The remainder is information about the design.
Following the friction
The discipline is also suspicious of frictionlessness, because friction rarely disappears; it moves. A one-click service may depend on warehouse workers absorbing greater scheduling volatility. An automated bureaucracy may save staff time while making citizens troubleshoot classifications. A seamless healthcare portal may make patients responsible for integrating information previously handled by administrative staff.
Rather than asking whether a design is frictionless, ethotechnical analysis follows the friction: who is doing the work now? The same applies to efficiency. An organization has not necessarily become more efficient when its internal costs fall; it may have externalized them. Evaluation therefore runs across the whole adaptation field, not merely within organizational boundaries — the same move the falsified denominator makes on the accounting side.
This widens accessibility. Accessibility is not a specialized feature added for a subset of users. Human variation — bodily, cognitive, temporal, linguistic, circumstantial — is an ordinary fact systems should expect. The inability of some people to compensate for a design may expose adaptation burdens that more resourced people have been silently absorbing, which is the same asymmetry the workaround presumption names at the level of coping.
What it is not
Because its object is the distribution and correction of adaptation burdens, the discipline cannot be reduced to universal design, human-centered design, participatory design, service design, ergonomics, or accessibility, although it borrows from all of them. Its relationship to participation is correspondingly unusual: it values participation but does not assume more is better. Making people constantly report problems, attend meetings, submit feedback, monitor decisions, and organize for basic corrections creates another adaptation burden.
The objective is therefore high corrective power at low human cost. Ideally people do not have to become experts in the institution governing them merely to make it behave reasonably. The test for any arrangement is two questions. First: what does this design require people to notice, remember, learn, endure, coordinate, translate, correct, prove, monitor, or repeatedly request — and which of those tasks could the arrangement itself absorb? Second, the political question: when those requirements become unreasonable, can the people bearing them make the design change?
Those two questions distinguish the discipline from making something pleasant or convenient. Its ultimate objective is not maximal ease, maximal personalization, or maximum efficiency. It is to convert collective organizational capacity into uncolonized human capacity:
institutional capacity → complexity absorbed upstream → less compensatory adaptation → greater capacity for living
What the laws take from this
The method does not require a reader to accept the framing to adopt its constraints. It takes four, each already bound elsewhere.
From Law IV it takes that every consequential delegation creates a correction obligation, which is the fourth move: repeated mismatch must be able to redesign the generating rule, not merely be absorbed more efficiently. From Law VII it takes that error-bearing parties require standing proportional to exposure, which is the political question — whether the people bearing unreasonable adaptation demands can force the design to change. From Law VIII it takes that observability without state transition is theater, which is what distinguishes a system that registers exceptions from one that is changed by them. And from Law XI it takes that successful automation increases its own governance burden, which is the friction argument: every saved internal step is a demand that has landed somewhere, and the discipline asks where.
An engineer who rejects the essay can adopt all four on narrower grounds: an arrangement that spends its users’ adaptive capacity instead of its own has chosen a cheaper accounting surface, and a system whose repeated exceptions never reach the generating rule is a system whose failure rate its operators do not know. The framing explains why the choice is political. The method only insists that the allocation be visible.