Reading notes: The Quiet Ledger
Read by: Ana Ferreira · Date: 2 October 2026
Source
| Title | Author | Link | Date read |
|---|---|---|---|
| The Quiet Ledger: How Small Teams Keep Score | H. Lindqvist | fernhillpress.example/quiet-ledger | 2 October 2026 |
Summary in 3 sentences
- Small teams fail less from bad strategy than from losing track of what they already agreed to.
- The fix is a "quiet ledger": a short, written, shared record of commitments, reviewed weekly and never rewritten after the fact.
- Metrics help only when each one has a named owner and a decision it is meant to inform.
Key ideas
- Commitments decay silently. A promise made in a meeting has a half-life of about two weeks unless it is written somewhere people look again.
- Append, don't edit. Changing a past entry destroys the record of how the team's thinking moved. Add a dated correction instead.
- One metric, one decision. If nobody can name the decision a number changes, stop reporting it.
- The weekly review is the product. The ledger itself is cheap; the fifteen minutes spent reading it together is what changes behavior.
Quotes
"A team that cannot say what it promised last month will promise it again, and believe it is new." (p. 41)
"Dashboards are where numbers go to be admired." (p. 88, on metrics without owners)
Disagreements
- Lindqvist insists the ledger must be on paper or a plain text file. That feels like nostalgia; the real requirement is that it is append-only and visible, which version history gives you just as well.
- The book assumes a stable team. With contractors rotating in every quarter, the onboarding cost of the ledger is higher than the author admits.
How I'll apply it
Related
- Turn the Ship Around (L. David Marquet): intent-based leadership, same emphasis on explicit commitments
- My notes on decision records from the Lumen Labs ADR workshop