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
- It was a laboratory experiment, not an operations floor.
- Accountability is not a slogan. Reviewing the research, Jennifer Lerner and Philip Tetlock found that its effects depend on the kind of accountability, the task, the person and the timing.
- The screen is my proposal. Nobody has tested it on a warehouse override.
Sources
- Tetlock, P. E., L. Skitka, and R. Boettger. 1989. “Social and cognitive strategies for coping with accountability: Conformity, complexity, and bolstering.” Journal of Personality and Social Psychology 57(4): 632-640. doi.org/10.1037/0022-3514.57.4.632
- Lerner, J. S., and P. E. Tetlock. 1999. “Accounting for the effects of accountability.” Psychological Bulletin 125(2): 255-275. doi.org/10.1037/0033-2909.125.2.255
From the field notes Nobody Pays for Being Wrong · PDF, 27 pages