dcd
DCD: Directional Cognitive Discomfort for error feedback
Comfort belongs on the happy path. At the moment of error, a well-formed aversive signal teaches faster and more durably than a neutral message — if it is immediate, local, directional, proportional, formally identical every time, and aligned with the user's own goal. This skill turns that into a build procedure.
Source: Abdurakhimov, Directional Cognitive Discomfort (2026). Biological grounding: cultured neurons learn when errors are signaled by unpredictable stimulation, and only when the feedback channel is delivered with strict temporal and structural consistency (Kagan et al. 2022; Hogan et al. 2026, CL API).
The one-sentence rule
The fastest way for the user to make the signal stop must be to do the correct thing.
If the escape route is "read the message", "dismiss the banner", or "give up", it is not DCD. If the escape route is "do what the operator wants", it is a dark pattern.
Workflow
Follow these steps in order. Skip none; step 3 is the one people skip and it is the one that makes everything else work.
1. Inventory error points
List every interaction where a user can take an incorrect action that costs them something. For each, record: action, what "correct" is, cost to the user if wrong (data loss / time / money / safety), and observed frequency. Rank by cost × frequency. Work the top of the list first.