Protocol
Treat a repeated workaround as a process-design signal
A workaround solves today's task and can hide tomorrow's defect.
When it fits
- People repeatedly bypass, duplicate or manually repair the official workflow to finish ordinary work.
When to avoid it
- Some workarounds are unsafe and must stop immediately. Immediate containment and later process redesign are separate decisions.
Why it matters
Do not start with 'people must follow the process.' First map what the workaround is achieving: speed, missing information, unavailable authority, bad interface, conflicting goals or recovery from a known defect. Compare the official path with the real path, assess the risk created by both, then remove the cause, redesign the workflow or deliberately formalize the safer path. Repeated bypass is operational data.
Steps
- Observe the real workflow without assuming the workaround is irrational.
- Name the constraint or failure the workaround compensates for.
- Compare risk and cost in the official and real paths.
- Change the system or formally justify the exception.
- Verify that the workaround is no longer needed or that the approved exception is controlled.
An example
Users copy data into a spreadsheet because the official report cannot filter the needed cases. Repeating the policy will not repair the missing capability.
Check your result
The response changes or deliberately accepts the workflow condition that generated the workaround, rather than only reminding users.
Keep this limit in mind
- Some workarounds are unsafe and must stop immediately. Immediate containment and later process redesign are separate decisions.
Connected ideas
Useful withTrack a precursor you can act on before the failure
Evidence and sources
AHRQ safety-engineering guidance recommends combining prospective and retrospective analysis with ongoing surveillance, and notes that workarounds can signal that a process is not functioning well.
The guidance is written for healthcare systems; transfer to knowledge work is at the general system-design level.
Engineering Safe Practices Affinity Group · Strategy 1 rationale and opportunities
AHRQ PSNet guidance says recurring workarounds should trigger assessment of workflow and competing demands rather than a reflexive reminder to follow the official process.
Not every workaround is unsafe or evidence of bad design; local constraints and risk still need to be examined.
Workaround · Definition and management response
AHRQ distinguishes first-order problem solving, which fixes the immediate case, from second-order problem solving, which changes the process to reduce recurrence.
Immediate recovery can still be necessary; the distinction is about whether future risk is also addressed.
Learn From Defects in Care of Mechanically Ventilated Patients: Facilitator Guide · Problem-Solving Hierarchy