Sit in on the assembly of a board pack at any company between fifty and a thousand people and you'll witness one of the strangest rituals in modern management. Forty slides. Two weeks of work across half the leadership team. Three rounds of internal review. A "tone pass" the night before, where particularly alarming numbers get re-coloured, re-worded, or quietly moved to an appendix nobody opens.
By the time the chair of the board opens the pack at 9am, every concerning data point has been rounded down, reframed up, contextualised sideways, or relocated to slide 38. The non-executives read it. They nod. They ask the polite questions the format invites. They go home.
Everyone in the room knows this is theatre. The CEO knows. The CFO knows. The non-executives know — most of them have sat on the other side of this exact ritual at their own companies. The board pack is read as a kind of corporate Kabuki, a performance whose actual function is to demonstrate that things are under control, not to describe what is actually happening. The function is signalling, not informing. And the signalling is so well understood that the most experienced board members ignore the pack and ask the CEO directly what's really going on — at dinner, the night before.
Why the pack drifts from reality
Three structural reasons, none of which are about anybody being dishonest.
The pack is assembled, not generated. Each function owner submits a slide. Each slide is curated by that owner to reflect their function in the most favourable light consistent with not being caught lying. Nothing in the process forces the slides to add up to the underlying state of the company — there's no shared system that the slides are derived from, so the slides become their own reality. Twelve carefully composed individual narratives, stitched together into a forty-page deck, with no integration check.
The pack is monthly or quarterly. The underlying work moved three to four weeks before the data was pulled. Whatever was true on the day of the data pull is no longer true by the time the board reads it. The pack describes a snapshot of a moving system, taken at a moment that's already weeks old, and presented as if it were the current state. That gap is small in calm quarters and catastrophic in turbulent ones — and turbulent ones are exactly when the board most needs accurate data.
The pack has no live link to the work. A green key result on slide 14 is asserted by the slide author, not derived from any system the board can interrogate. Nobody can click through. The number sits there as text on a slide, supported by a story the author has rehearsed, with no chain of evidence behind it. If a non-executive wants to know how that number was produced, the only answer is "the team tracks it." Where? In a spreadsheet. Who updates it? The owner. When? Before the pack is due. The integrity model is honour-based, which means it has no integrity model at all.
What the board should be able to do
The board should be able to ask, in the middle of a meeting, "show me the work that moves this key result." That request should resolve in one click, against live data, with named owners and current state, regardless of whether the data lives in Jira, Linear, HubSpot, or Monday. The slide should be a view into a system, not a hand-painted illustration of one.
When the slide is a view into a live system, three things change about the meeting. The CFO can validate the operational claim behind a financial number in real time, instead of taking it on faith and discovering the truth at the next quarter. The non-executives can drill into a specific bet without a two-week follow-up cycle of "we'll get back to you with that data." And the CEO can stop spending two weeks per quarter on pack preparation, because the pack is now a saved query rather than a curated document.
Critically, the pack stops being a performance because it can no longer be performed. The numbers in it aren't typed in by a slide author — they're rendered from the operating layer. If the underlying work is amber, the slide is amber. If the team hasn't updated the status, the slide says "not updated since." The format itself enforces honesty, because the alternative — making a slide that contradicts the system — is visibly absurd.
Why this hasn't been fixed yet
Because fixing it requires building the underlying system. Most companies have the data — somewhere, scattered across tools — but no integration that joins it into a coherent picture of strategy execution. The board pack persists as a hand-assembled artefact because there is no live alternative. Every other reporting layer in the company has been automated; the strategy reporting layer has not, because the substrate it would draw from doesn't exist as a single object.
The pack also persists because the people most empowered to fix it benefit, in a small uncomfortable way, from the current state. A curated pack lets the CEO control the narrative. A live system lets the board interrogate it. Most CEOs will say they want the second; the assembly process suggests they prefer the first. That tension is the structural reason this problem is unsolved at most companies.
The Vindaris position
The board pack is a symptom. The disease is that goals, work, capacity, and ownership live in separate systems, and the only thing that joins them is a human writing a slide once a quarter. Fix the substrate — put strategy execution on a single live layer — and the pack writes itself, in real time, against actual data.
The board still wants a narrative. That's fine. Narrative is how humans absorb complex situations, and a good CEO will always frame the data for the audience. But the narrative now sits on top of a live system, not in place of one. When the board asks the awkward question, the answer is a query result, not a defensive recomposition. That's what a real status looks like, and it's what every board pack will eventually be, once the substrate exists to make it possible.