# Prefer a system-strengthening action over another reminder

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

---

## Prefer a system-strengthening action over another reminder

ID: MHC-D-RESEARCH-0733 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/prefer-a-system-strengthening-action-over-another-reminder

If the same slip can recur unchanged, the action probably did not reach the system.

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

### Use when

- The proposed fix is training, a policy reminder, a warning email or 'be more careful' after a repeatable failure.

### Avoid when

- Not every problem can be engineered away. Accountability, skill and judgment still matter; the point is not to misclassify a system defect as a memory problem.

### Explanation

Compare the proposed action with stronger options: remove the hazardous step, constrain invalid input, change the default, automate a check, improve visibility, reduce ambiguity or add recovery. Training can still be useful, especially for knowledge gaps, but do not use it as the automatic answer to a design defect.

### Example

Instead of reminding analysts to check a file version, reject uploads whose schema version does not match the target.

### Check

The selected action changes the conditions under which the error occurs, or explicitly explains why that is not feasible.

### Limits

- Not every problem can be engineered away. Accountability, skill and judgment still matter; the point is not to misclassify a system defect as a memory problem.

### Evidence and sources

- supports: Modern RCA guidance emphasizes system-level contributing factors and sustainable corrective actions rather than stopping at individual blame or documentation. — RS-C63447C9710D56FD. AHRQ discusses healthcare safety. The corpus transfers the system-design logic cautiously to ordinary work. (Introduction; RCA2; action hierarchy discussion)
- RS-C63447C9710D56FD: The Evolution of Root Cause Analysis — https://psnet.ahrq.gov/perspective/evolution-root-cause-analysis

No review details supplied.
