design-honest-record-keeping

Design Honest Record Keeping

Establish institutional norms for recording events, decisions, and failures accurately and without euphemism — because organizations that record reality honestly develop better learning loops, earlier warning signals, and stronger accountability than those that soften unflattering facts.

Why This Is Best Practice

谷梁传 (Guliang Chi, ~5th–4th century BC) — Book of Commentary on the Spring and Autumn Annals:

Why best: The 谷梁传 is built around a single interpretive principle: the 春秋's value as a historical and moral record comes entirely from its accuracy. Each entry — how an event is named, what details are included, what is omitted — constitutes a permanent moral judgment. The text repeatedly analyzes cases where the 春秋 used a particular word or form to convey a moral assessment: calling a ruler's death "killed" rather than "died peacefully," recording a defeat accurately rather than calling it a "withdrawal." The 谷梁传's teaching: institutional records that use euphemism or omit unflattering facts corrupt not just the record but the institution's capacity for moral and operational judgment.

Google Site Reliability Engineering — Blameless Post-Mortems (Beyer et al., 2016): Google's SRE handbook establishes the blameless post-mortem as a foundational engineering practice. The key design requirement: "A postmortem that blames individuals is not a useful postmortem." The actual requirement is: record exactly what happened — what systems failed, what decisions were made, what the timeline was — without assigning individual blame, without softening technical failures, and without omitting decisions that contributed to the incident. Google's rationale: accurate records produce actionable learning; blame-focused or euphemized records produce self-protection. This practice is adopted at Netflix, Etsy, Atlassian, PagerDuty, and throughout the SRE community globally. The "blameless post-mortem" is now standard vocabulary in software reliability engineering.