Who the Form Is For

Field notes for the COO

A record the dock fills for the auditor teaches the dock to fill it, not to use it. The same fields, built to help the person at the door, start telling you what happened.

Two organization researchers, Paul Adler and Bryan Borys, argued in 1996 that written procedures differ not only in how much they control but in what they are built for: some are built to catch the people who follow them, others to help them handle what goes wrong. One of their examples is an organization proud of its recent ISO 9000 registration, where engineers wrote the procedures and employees had to sign them like a contract, for an audit trail. Covert workarounds, they report, abounded. My reading: a record built for that answers who is accountable and says less about the work, which goes on in the workarounds.

The field notes end with four questions for a record your auditor reads, one for each feature the authors use to tell the two designs apart, and one to start with: ask the person who fills the record what it is for.

Read the field notes (PDF, 9 pages)