Should the reason for an override be recorded before or after the change?

Before, and for a reviewer whose view the operator does not know. Explaining a decision before committing to it makes people think. Explaining it after makes them defend it. Knowing what the reviewer wants makes them agree with the reviewer.

How it works

A reason written after the fact is a defence. A reason written to please the reviewer is an echo. Timing is the part a screen controls: the reason field appears before the change is saved, it starts blank, and nothing on the screen hints at the answer the reviewer prefers.

Evidence

In an experiment by Philip Tetlock, Linda Skitka and Richard Boettger, people answerable before committing, to an audience whose views they did not know, thought more self-critically. People answerable for a position already taken spent their effort defending it. People who knew what the audience wanted simply moved toward it.

What this does not prove

Sources

From the field notes Nobody Pays for Being Wrong · PDF, 27 pages