The Casebook · Entry 06
The Board Packet
A thicker packet looks like transparency. The lens asks what the board can actually act on, and what the volume is hiding.
The conventional reading
The thick packet is diligence made visible. Every statement, every schedule, every appendix, so nothing is withheld and no question finds the room unprepared. Assembling it is a serious monthly production, and its heft signals respect for governance: the board was given everything, and everything is the standard of openness.
Through the Native Constraint lens
Volume is where the read goes to hide. A packet is an abstraction, and the thick one is an abstraction done badly: it exposes machinery the board cannot govern with and buries the position it must. Eighty pages transfer the work of synthesis from the function to the reader with the least context and the least time. Transparency is not the count of pages shown. It is whether the account can be checked, and the thick packet is often neither readable enough to act on nor traceable enough to verify.
What it really costs
Governance latency. Decisions deferred a cycle because the read was not readable, meeting hours spent locating instead of deciding, questions answered by page number rather than by position. And the production cost behind it, days each month assembling a document designed, in practice, to be skimmed.
Where it puts the burden
On the reader least equipped to carry it. The board member reads on the flight in, performing in one evening the synthesis the function should have performed once, upstream, for everyone. Whatever they miss becomes the meeting's blind spot, and the blind spot was chosen by page count.
How to see past it
The packet is an interface, and an interface is designed. The position stated, the movement stated, every figure carrying its source, the machinery held beneath and available to anyone who asks. One read, plainly shown, the same in every room. Depth is not withheld, it is filed where checking happens instead of where deciding does.
A board given the read can govern in the meeting it has. The packet gets thinner, and the governance gets thicker.
The packet is one case. The habit is to read any practice twice: once at its reputation, and once for where the work actually sits, what it costs to keep it there, and whether the system could produce the outcome instead of a person holding the line.