Every board deck has a number and a narrative. The number is what you spent. The narrative is what it means. Most organizations get the number late and write the narrative quickly. That sequence is backwards.
Why the number comes late
The number comes late because it has to be assembled. Finance closes the quarter, the IT analyst pulls the data, reconciles it against the budget, maps it to the board-level categories, and hands it to the CIO's office two days before the deck is due. The analyst does good work, but the work takes time, and the time compresses the window for thinking.
What should be a question — "what does this number mean for our strategic position?" — becomes a constraint: "how do we explain this number in the time we have?"
Why the narrative suffers
Board narratives suffer from two failure modes. The first is defensiveness — the narrative explains the variance rather than addressing the strategy. The second is imprecision — the narrative uses words like "significant" and "substantial" without anchoring them to numbers, because the underlying numbers weren't ready in time to be integrated into the argument.
A good board narrative has the opposite properties. It is forward-looking rather than explanatory. It uses specific numbers to support strategic claims. It anticipates the questions a board member will ask and answers them before they are asked.
What a faster close makes possible
When the IT spend number is produced by a deterministic system rather than a manual reconciliation, the close accelerates. The number is available as soon as the source data is loaded, not after the analyst has finished reconciling the spreadsheet. The time recovered from reconciliation is available for thinking.
That shift changes the nature of the CIO's preparation. Instead of spending the week before the board meeting confirming that the number is right, the CIO can spend it thinking about what the number means and how to frame the implications for the board's priorities.
The quality of board reporting is not primarily a communication problem. It is a data availability problem. Fix the data availability and the communication problem is easier to solve.