Advisory-to-Mandate Escalation

Problem

The institution's process quietly converts the advice into a command. A protocol says to act on the alert, a workflow makes following it the default and overriding it an exception that must be justified, and overriding it comes to be treated as defiance rather than expertise. The advisory label still exists on paper, but the running social process treats the output as mandatory, so the expert is pressured to comply even when their own evidence says otherwise. Automation bias — the documented tendency to over-rely on automated suggestions, especially under time pressure — pushes the same way. The human is nominally in control while being punished for exercising it.

Solution

Treat the gap between the advisory label and the running process as the thing to fix. Design the workflow so that following the recommendation and overriding it are equally legitimate, low-friction paths, and so a documented, evidence-based override is recorded as professional judgement rather than as a deviation to be justified or disciplined. Counter automation bias actively — surface the recommendation's uncertainty and the basis for it, and require the human to engage rather than rubber-stamp. Audit override rates and outcomes to confirm the human's judgement is genuinely governing, and make sure accountability rests with the human decision, not with compliance to the tool. The output stays advice in practice, not only in name.

When to use

• Recognising this failure when an advisory recommendation is, in practice, mandatory and overriding it is treated as non-compliance.
• Reviewing a decision-support deployment whose protocol defaults to following the output and makes overriding costly.
• Diagnosing why experts stop deviating from a system's advice even when their own evidence disagrees.