Essential-Function and Method-Separation Review¶
Method — instantiates Human-Capacity Accommodation Design
Tests which outcomes and safety controls are essential and which methods are inherited or convenient.
Most exclusion hides inside a requirement that sounds necessary but is really just the way things have always been done. Essential-Function and Method-Separation Review pulls those apart. For each requirement in a task or role it asks a single hard question — is this the outcome that must be achieved, or merely the inherited method for achieving it? — and forces every "must" to justify itself against evidence rather than tradition. Where a genuine hazard is claimed, it isolates the actual safety control being relied on and asks whether that control (not the method that historically carried it) is what is essential. Its one defining idea is separation: it rewrites the goal in method-neutral terms and demotes everything that turns out to be convention, so that later steps design around the real outcome instead of optimizing a barrier. It does not itself invent alternatives, profile people, or test any substitute — it decides what may not be compromised, and thereby what is fair game to change.
Example¶
A city clerk's office lists, among the "essential functions" of its permit-intake role: handwrite each application into the ledger, answer the counter phone within three rings, and personally carry files to the records room twice a day. A capable applicant who cannot sustain fine handwriting is about to be screened out. The review takes each clause in turn. The essential outcome is that a permit record is accurate, timely, and retrievable — not that a specific hand produced it; handwriting is an inherited method from a pre-database era. The three-ring phone rule is defended as "responsiveness," but the real control is that callers reach help promptly, which a shared queue satisfies equally. The twice-daily file walk is traced to a safety claim — chain-of-custody for legal documents — and here the review does not wave it away: it names the genuine control (tamper-evident custody) and records that any alternative must preserve it. The output is a rewritten frame: one essential outcome, one genuine safety control with its bar stated, and two inherited methods marked open for redesign.
How it works¶
The method is a disciplined interrogation of requirements, one at a time:
- Restate the goal method-neutrally. Convert "do X this way" into "achieve this result," stripping the verb that smuggled in a method.
- Classify each requirement as essential outcome, genuine safety control, or inherited/convenient method — and demand the evidence for any "essential" label.
- Trace safety claims to the actual hazard and control. Name the risk, the control that reduces it, and whether that control is method-bound or method-independent.
- Record the consequence of relaxation. For each demotion, log what could go wrong if it were changed and what compensating control would hold.
- Assign authority. Note who has standing to challenge or defend each requirement, so demotions are decisions, not opinions.
The product is not a solution but a cleared field: a frame that states the outcome and the safety bar, and lists what is now legitimately changeable.
Tuning parameters¶
- Essentiality threshold — how much evidence a "must" must produce to survive; a high bar frees more design room but risks demoting something quietly load-bearing.
- Safety-control resolution — how finely a hazard is decomposed into its actual control; finer resolution reveals method-independent controls but takes expert time.
- Authority breadth — who may contest a requirement (owner only, or affected people too); wider standing catches more false "musts" but slows sign-off.
- Documentation depth — a note versus a full reason-and-consequence record per requirement; depth aids later appeal but adds effort.
When it helps, and when it misleads¶
Its strength is that it turns "we've always required this" into a testable claim, and it does so before anyone designs an accommodation, so the whole downstream effort aims at the real outcome instead of a fossilized method.
Its failure mode runs in both directions. Demote too eagerly and you can strip out a requirement whose purpose you never understood — the review must respect Chesterton's fence: do not remove the fence until you can say why it was put there.[n1] Demote too timidly, or let an incumbent defend the status quo, and "essential function" becomes a rubber stamp for exclusion — the classic misuse, where every inherited method is declared safety-critical to avoid change. The guarding discipline is symmetric evidence: an "essential" label and a "merely inherited" label each require a stated reason, a named consequence of relaxation, and an accountable owner, so neither convenience nor timidity wins by default.
How it implements the components¶
This mechanism fills the framing pole of the archetype — what must be preserved — and the safety bar that any later option must clear:
essential_outcome_user_and_context_frame— its primary output: the method-neutral outcome, the user and context, decision authority, and the inherited methods now marked changeable.safety_dignity_privacy_and_burden_gate— it establishes the safety pole of the gate up front: which controls are genuinely essential and the risk bar an accommodation must not fall below.
It does not build capacity or demand profiles (representative_human_capacity_and_variability_profile, task_environment_and_interface_demand_map) or the mismatch ledger (mismatch_barrier_workaround_and_risk_ledger) — those belong to Person–Task–Environment Mismatch Analysis. Its nearest twin is the Participatory Accommodation-Option Workshop: that method generates the accommodation_option_and_equivalent_path_set once the essentials are fixed; this review fixes what is essential and never proposes a single option.
Related¶
- Instantiates: Human-Capacity Accommodation Design — supplies the essential-outcome frame and safety bar the lifecycle designs against.
- Sibling mechanisms: Person–Task–Environment Mismatch Analysis · Participatory Accommodation-Option Workshop · Multimodal Equivalence and Assistive-Compatibility Test · Accommodation Failure and Recovery Rehearsal · Longitudinal Fit, Equity, and Burden Audit
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Essential-Function and Method-Separation Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it tests which outcomes and safety controls are essential and which methods are inherited or convenient.
Independent corroboration: The frozen evidence defines Essential-Function and Method-Separation Review as 'Tests which outcomes and safety controls are essential and which methods are inherited or convenient', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Disability and employment law cohered the distinction between an essential job function and a customary method that may be changed as accommodation.
Related originating lineages:
- Medicine & Healthcare — Rehabilitation and occupational practice supplies functional-capacity and safety assessment.
- Organizational & Management Science — Job analysis supplies evidence about actual outcomes, task design, and inherited work methods.
Review resolution: The current reviewers agree that law_governance is primary. For the reported differences (alternate_origin_disagreement, domain_reach_disagreement, encyclopedia_synthesis_disagreement), the evidence supports cross_disciplinary_synthesis, multi_domain, and medicine_healthcare, organizational_management; these choices preserve materially formative origins without conflating later domain reach.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Chesterton's fence is the principle that you should not remove a rule or barrier until you understand why it was put there; only once its purpose is known can you judge whether it is safe to take down. It is the discipline that keeps method-demotion from silently deleting a genuine safety control. ↩