Trading in Trust: How Documentation Protects People, Not Just Projects
summary
Documentation functions as trust infrastructure: a missing policy lets power and loudness decide, while a written contract changes interactions. Example: tutorial-event misuse produces an 89% vs 19% day-one retention mistake until telemetry gets formalized; analysts gain protection after a Slack bot request form plus schema docs that name event purpose, trigger timing, and limitations. The result is a repeatable filing workflow and enforceable rules that deflect ad hoc pressure and let teams argue about docs, not people.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:30Documentation as trust infrastructure
- 2:33First failure story absence of documentation
- 9:38Solving the docs vacuum
- 10:00Second failure: docs as power
- 13:29Documentation externalizes authority
- 14:31Four-pillar framework for trustworthy docs
- 15:35Writing for enforcers
- 17:23Anchor to mission
- 18:51Document why and what
- 21:00Make limitations visible
- 22:45Docs as leveler and shield
- 23:49Q&A
related talks
19mBuilding Trust Across Teams Through Documentation
27mThe hidden power of information assets The role of documentation in product success
43m"How To Write Tech Documentation That Will Save Your Career"
24mWho Writes the Docs?
40mDocumentation as User Experience
26mWe're Agile, We Don't Do Documentation
29mHumanizing Your Documentation
36mTo document, or not document that is the question