Why Every Board I Know Receives Too Much Information and Too Little of What It Needs
The first board meeting I ever chaired as a chair who built a board from scratch lasted four hours. We had 340 pages of materials. By the end, I could tell you almost nothing about the actual state of the business — not because the information wasn't there, but because it was buried under data prepared for management, not for governance. The reporting pack had been assembled for the wrong audience. That was the moment I started thinking seriously about what boards actually need to see, in what form, and when.
What I have come to call the Board Information Architecture Model — or BIA — is not a reporting template. It is a structural question: whose job is it to make sure that the people responsible for oversight have the right information, in the right format, at the right time? In my experience from the operator's side of the table, the answer is almost never clear. Which is why the problem persists.
What the BIA Framework Addresses
The failure mode I see most often is not dishonest reporting. It is misaligned reporting — management teams producing information that is accurate but structured to answer the questions management asks of itself, not the questions a board needs answered to do its job. These are different questions. Management asks: did we execute? A board needs to ask: are we still governing toward the right outcome, and what would tell us if we weren't?
The BIA framework emerged from my effort to systematise the difference. It rests on four premises:
- Information has a primary recipient. The same financial report that serves a CFO's planning function serves a board's oversight function badly — unless it is specifically reframed for the governance question.
- Boards govern through exceptions, trends, and questions — not through operational completeness. A 300-page pack represents a failure of editorial judgment, not diligence.
- Information architecture is a governance responsibility, not an administrative one. If the board is not actively specifying what it needs, management will fill the gap with what is convenient to produce.
- Timing matters as much as content. Information that arrives 48 hours before a meeting on a topic that requires six weeks of follow-up is structurally useless for governance, regardless of its quality.
The BIA Structure: Three Layers
The model identifies three distinct information layers, each with a different purpose, cadence, and owner:
| Layer | Purpose | Cadence | Typical Owner |
|---|---|---|---|
| Layer 1 — Governance Dashboard | One-page summary of KPIs against board-set thresholds. Red/amber/green is acceptable here — because the board has defined what red means. | Monthly, 5 days before board | Company Secretary or CFO |
| Layer 2 — Deep-Dive Packages | Structured analysis of one or two topics per meeting. Each package must contain: the question the board is being asked to answer, the relevant data, management's recommendation, and the risks if the board disagrees. | Per meeting, rotated by committee | Committee Chair + relevant executive |
| Layer 3 — Horizon Intelligence | Forward-looking signals: regulatory changes, sector stress indicators, competitor governance events, early-warning data the board has identified as strategically important. This layer is almost always missing. | Quarterly minimum; quarterly pre-reads | Board Chair or designated non-executive |
The key discipline is that Layer 1 never expands — it must fit on one page, always. Once it starts growing, it has stopped being a governance dashboard and become a management report again. That compression is the governance signal: when something cannot be summarized cleanly, that is itself important information.
How I Applied It When Building the Board at FireTech
When I established the board at FireTech Engineering BG — having built an EPC business to 450 people and run 200+ industrial projects before turning to governance — one of the first things I did was refuse the standard reporting pack. Not because the information was wrong, but because it had been designed for operational review, not for board oversight of strategy and risk.
We spent three months designing the governance dashboard from scratch. The test for every metric was simple: if this number moved significantly between now and our next meeting, would we need to know before the meeting — or would it wait? Anything that couldn't wait went to the real-time alert protocol. Anything that could wait went into the pack. Anything that neither the board nor management could articulate a decision consequence for was removed entirely.
The result was a two-page Layer 1 dashboard and a rotating deep-dive structure that covered each committee's mandate once per quarter with full analytical depth. The board meetings shortened from four hours to ninety minutes with a better quality of conversation. More importantly, the board started asking the questions that management couldn't answer — which is the correct signal that governance is functioning.
Applying the BIA: A Practical Starting Point
For any board beginning to apply this framework, I suggest starting with a simple audit. Pull the last three meeting packs and ask three questions:
- What percentage of the material was genuinely decision-relevant? Most boards, when they do this honestly, find it is under 30 percent.
- For each item that required a board decision, was the question explicitly framed? Or did the board have to infer what it was being asked?
- What was not in the pack that, in hindsight, would have changed the quality of the conversation? The absence of horizon intelligence is almost always the most striking finding.
The audit is not a critique of management. It is a specification exercise. The board's job is to articulate what it needs — clearly, specifically, with enough lead time for management to produce it. If the board has not articulated this, it has no basis for complaining about what it receives.
According to research by Spencer Stuart on board effectiveness (2024 Board Index), directors consistently rank "quality of information received" as one of the top three constraints on board effectiveness — alongside time and composition. The BIA framework addresses the first of those directly and creates conditions for the other two to improve as well.
Where the BIA Framework Does Not Work
Every framework has failure modes. The BIA has three that I have encountered directly.
The first is board passivity. The framework assumes a board willing to specify what it needs and push back when it doesn't receive it. Boards that have developed a culture of deference — where reading the pack and not asking sharp questions is considered polite — will not make the BIA work because they will not maintain the discipline of Layer 1.
The second is management resistance. Restructuring the reporting architecture requires more editorial work from management, not less. A management team that measures effort by volume of output — and equates bulk with diligence — will find ways to expand every layer back toward the comprehensive pack. This requires active board chair enforcement, ideally written into the governance charter.
The third is over-formalization. In smaller or younger companies, the BIA can become a compliance exercise rather than a governance tool. The model should be treated as a thinking structure, not a bureaucratic template. The three-layer logic matters; the exact format of each layer should adapt to the company's size, complexity, and governance maturity.
The Deeper Point
The reason information architecture matters is that what boards see shapes what boards govern. A board that only receives operational data will govern operationally — and miss the strategic and reputational risks that are often invisible in monthly financials. A board that receives horizon intelligence will ask different questions. A board that has defined its own governance dashboard will notice when the numbers stop telling a coherent story.
This is not a reporting problem. It is an architecture problem — and architecture is always a choice, even when it looks like habit.
The boards that govern best are not the ones with the most information. They are the ones who have been most deliberate about which information they actually need.