# Treat a repeated workaround as a process-design signal

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Treat a repeated workaround as a process-design signal

ID: MHC-D-RESEARCH-1270 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/treat-a-repeated-workaround-as-a-process-design-signal

A workaround solves today's task and can hide tomorrow's defect.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- People repeatedly bypass, duplicate or manually repair the official workflow to finish ordinary work.

### Avoid when

- Some workarounds are unsafe and must stop immediately. Immediate containment and later process redesign are separate decisions.

### Explanation

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

1. Observe the real workflow without assuming the workaround is irrational.
2. Name the constraint or failure the workaround compensates for.
3. Compare risk and cost in the official and real paths.
4. Change the system or formally justify the exception.
5. Verify that the workaround is no longer needed or that the approved exception is controlled.

### 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

The response changes or deliberately accepts the workflow condition that generated the workaround, rather than only reminding users.

### Limits

- Some workarounds are unsafe and must stop immediately. Immediate containment and later process redesign are separate decisions.

### Evidence and sources

- supports: 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. — RS-00E7F25184BF4AAC. The guidance is written for healthcare systems; transfer to knowledge work is at the general system-design level. (Strategy 1 rationale and opportunities)
- supports: AHRQ PSNet guidance says recurring workarounds should trigger assessment of workflow and competing demands rather than a reflexive reminder to follow the official process. — RS-BD4546713D38A818. Not every workaround is unsafe or evidence of bad design; local constraints and risk still need to be examined. (Definition and management response)
- supports: AHRQ distinguishes first-order problem solving, which fixes the immediate case, from second-order problem solving, which changes the process to reduce recurrence. — RS-209873EE786D9765. Immediate recovery can still be necessary; the distinction is about whether future risk is also addressed. (Problem-Solving Hierarchy)
- RS-00E7F25184BF4AAC: Engineering Safe Practices Affinity Group — https://www.ahrq.gov/action-alliance/engineering-safety-practice/index.html
- RS-BD4546713D38A818: Workaround — https://psnet.ahrq.gov/glossary/workaround
- RS-209873EE786D9765: Learn From Defects in Care of Mechanically Ventilated Patients: Facilitator Guide — https://www.ahrq.gov/hai/tools/mvp/modules/cusp/learn-from-defects-fac-guide.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/track-a-precursor-you-can-act-on-before-the-failure
