Principle
Do not discipline away a system defect
Accountability and redesign are different questions; answering one does not remove the other.
When it fits
- An incident review focuses on who clicked the wrong thing while the same interface can mislead the next person.
When to avoid it
- This is not legal or HR advice; serious misconduct and regulated incidents require the relevant formal process.
Why it matters
Separate behavioral accountability from system learning. Determine whether the action was inadvertent error, an at-risk shortcut, or reckless conduct under the organization's policy. Independently ask what design allowed one action to produce the harm and what would protect the next user. Even when accountability is appropriate, fix the repeatable system trap.
An example
A user may violate a known rule and still reveal that the destructive button lacks any environment distinction or validation.
Check your result
The incident review can name both any justified accountability response and the system improvement needed for recurrence prevention.
Keep this limit in mind
- This is not legal or HR advice; serious misconduct and regulated incidents require the relevant formal process.
Evidence and sources
AHRQ just-culture guidance separates inadvertent human error from at-risk or reckless behavioral choices and recommends system design rather than blame as the default response to ordinary error.
Serious misconduct, policy violations and legal obligations require their own accountability process.
Staff Empowerment: System design, behavioral choices, learning systems and accountability · System design, behavioral choices and accountability