Barrier Removal Workflow¶
Process improvement workflow — instantiates Equity Adjustment
Identifies recurring barriers and redesigns processes, environments, forms, interfaces, schedules, or requirements so fewer individual exceptions are needed.
A Barrier Removal Workflow treats a pattern of individual adjustments as evidence that the default design is wrong, and closes it by redesigning the process itself so the barrier stops recurring. Its defining idea is the shift from case to system: where a case-review workflow answers one request well, this workflow asks why the same request keeps arriving and changes the rule, form, requirement, or schedule that generates it — once, for everyone. It is triggered by accumulation, not by any single hardship, and its output is a redesigned default plus a trigger to revisit whether the redesign held. That accumulation-driven, redesign-the-process character is exactly what separates it from a one-off environmental fix.
Example¶
A university financial-aid office notices that every fall it grants dozens of near-identical extensions on income-verification paperwork. Digging in, the workflow maps the recurring barrier: the verification form demands a prior-year tax transcript, but a large share of applicants are recently independent students, displaced workers, or families whose income changed — people for whom last year's transcript is unavailable or misleading. This is textbook administrative burden:[n1] the cost is not in the standard but in the proof it demands. Instead of processing another wave of extensions, the office redesigns the requirement: it accepts alternative documentation for the changed-circumstance cases and adds a self-attestation path with later verification. Fewer individual exceptions are needed the next cycle, and the workflow sets a reassessment point one year out to confirm the redesign did not open a fraud gap or a new exclusion. The single-case accommodations do not vanish, but they stop being the norm.
How it works¶
The distinctive method is aggregation, then structural change, then a trigger to re-check:
- Aggregate the exceptions. Pull the stream of individual adjustments and cluster them: which barrier, which step, which requirement keeps generating requests.
- Map the barrier to its cause in the design. Locate the specific form field, deadline, proof rule, channel, or schedule that turns a relevant difference into disadvantage — the thing to change, not the people to help one at a time.
- Redesign the default rule. Change the requirement, procedure, or format so the barrier is gone for everyone, bounded by the standard it must still protect.
- Set a reassessment trigger. Schedule a look-back to confirm the redesign reduced the exception load without eroding the standard or creating a new gap; if it did not, reopen the design.
Tuning parameters¶
- Aggregation window — how many cases, over how long, count as a "pattern" worth a redesign. A short window reacts fast but chases noise; a long one is confident but leaves people stuck under the old default meanwhile.
- Redesign scope — patch one field vs. re-architect the whole process. Narrow scope ships quickly and leaves adjacent barriers; broad scope fixes more and risks over-reach and delay.
- Standard-preservation stringency — how tightly the redesign is bound to protect the original purpose. Loose, and redesign drifts into erosion; tight, and it may not move enough to matter.
- Reassessment interval — how soon the trigger fires. Sooner catches a bad redesign early; later gives the change time to show its true effect.
When it helps, and when it misleads¶
Its strength is leverage: one redesign can retire a standing queue of accommodations and remove the barrier for people who never asked. It is the mechanism that converts the archetype's learning invariant into practice — repeated cases feeding back into system design instead of into an ever-growing backlog.
Its failure mode is standard erosion by convenience. Under pressure to cut the exception load, a redesign can quietly strip an essential requirement rather than an incidental barrier — the fastest way to shrink the queue is to lower the bar, which is a different (and often wrong) move. A classic misuse is redesigning around the loudest complaints while the quietest, most-excluded cases never entered the data at all. The guarding discipline is to separate the core standard from the incidental pathway before changing anything, and to bind the redesign to the standard's purpose with a reassessment trigger that can reverse it.
How it implements the components¶
Barrier Removal Workflow fills the diagnose-and-redesign slice of the archetype — the systemic lever, not the individual case:
barrier_map— it locates the recurring barrier in the specific process step, form field, proof rule, or schedule that keeps generating exceptions.rule_adjustment— it changes the governing requirement, format, or procedure once for everyone, rather than granting a per-person exception.sunset_or_reassessment_trigger— it attaches a scheduled look-back that confirms the redesign reduced burden without eroding the standard, and reopens the design if it did not.
It does not deliver an individual environmental fix or protect a person's disclosure (support_adjustment, privacy_and_dignity_safeguard) — that is its nearest twin, Accessibility Change, which modifies the interface directly rather than diagnosing a recurring pattern. It also does not run the standing request channel or per-case review (participation_channel, fairness_outcome_monitor — Accommodation Process).
Related¶
- Instantiates: Equity Adjustment — the systemic lever that turns recurring exceptions into a redesigned default.
- Consumes: Accommodation Process supplies the stream of individual cases whose accumulation triggers a redesign.
- Sibling mechanisms: Accessibility Change · Accommodation Process · Differentiated Support Pathway · Hardship Exception Review · Needs Assessment Rubric · Targeted Resource Allocation
Editorial Notes¶
Form Classification¶
Form family: Intervention, Treatment & Transformation
Rationale: Identifies recurring barriers and redesigns processes, environments, forms, interfaces, schedules, or requirements so fewer individual exceptions are needed, making its operative form a direct operation whose success is a changed target state or capacity.
Independent corroboration: The frozen evidence defines Barrier Removal Workflow as 'Identifies recurring barriers and redesigns processes, environments, forms, interfaces, schedules, or requirements so fewer individual exceptions are needed', so its operative form is Intervention, Treatment & Transformation.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Equity-oriented policy design removes recurring structural access barriers rather than relying on individual exceptions.
Related originating lineages:
- Human-Computer Interaction — Inclusive design removes interface and process barriers at the system level.
- Law & Governance — Disability and equality law establish reasonable access and nondiscrimination duties.
- Organizational & Management Science — Process improvement removes recurring workflow friction.
Review resolution: Public administration is the agreed primary through administrative-burden and systemic-equity redesign. Inclusive interaction design, equality law, and process improvement materially shape the workflow; converting recurring exceptions into a reassessed default is the Encyclopedia's synthesized procedure.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
This workflow is where the archetype's individual-versus-systemic tradeoff is resolved in the system's favor. The right reading of a long exception queue is rarely "process the cases faster"; it is "the default is wrong for a predictable group." The reassessment trigger is what keeps that correction from becoming its own unreviewed default.
[n1] "Administrative burden" (Pamela Herd and Donald Moynihan) names the learning, compliance, and psychological costs that processes impose on the people who must navigate them; recurring accommodation requests are frequently a symptom that such burden, not the standard itself, is doing the excluding. ↩