In many organizations, the executive pack is rebuilt from scratch every month. Analysts export numbers from reports, paste them into slides, check them twice, write a line of commentary under each chart and send a file that is out of date by the next morning. The pack grows whenever someone asks a new question, and pages are rarely removed.
Leaders, meanwhile, read a handful of pages and skip the rest. The alternative is a living briefing: one page that refreshes with the data, explains in plain language what moved and why, and links to the detail for anyone who wants it. Getting there is less a technology project than an editing job, and it frees the analysts who build the pack for work that actually needs them.
What a living briefing is
A living briefing is not a dashboard with dozens of visuals, and it is not a slide deck published online. It is a single page, designed to be read in a few minutes on a laptop or a phone, that contains:
- The few numbers that run the business, each with its trend, its target and a signed variance.
- A short explanation of what moved, drafted by AI from the governed model and refreshed with the data.
- Links to the detail, so that a question about a region or a product opens the report that answers it.
- The data cut-off, stated plainly, so nobody has to wonder whether the numbers are final.
Because it reads from the same certified data as every other report, the briefing never disagrees with the detail behind it. Because it updates itself, nobody has to ask whether they are looking at the latest version. Design it for the question leaders ask first: is the business on track? The page should answer that before anyone scrolls, and every number on it should have someone accountable for it. A number with no owner and no decision attached belongs in the detail.
Start with an inventory of the packs
List every recurring pack: who receives it, how many pages it has, how many hours it takes to produce and who actually reads it. Usage data from the reporting platform shows which pages are opened. For slide decks, ask readers which pages they used last quarter and which they would miss.
The inventory is usually sobering. The same measure appears in several packs with slightly different values, because each was built from a different extract. Whole sections exist because one person asked for them long ago. A small number of pages attract nearly all of the attention.
Share the inventory with the executive team. Seeing the hours spent on pages that nobody opens makes the case for change better than any argument. Include the full cost: the analyst time, the extracts maintained to feed each pack, and the time leaders spend reconciling one pack with another.
Keep the numbers leaders actually use
With the inventory in hand, agree with the executive team on the five or so numbers that genuinely run the business. For each one, settle the definition, the owner, the target and the threshold at which a movement deserves an explanation. Everything else becomes detail behind a link rather than a page in the briefing. Resist adding numbers so that every function is represented; each function keeps its own detailed report, one click away.
Then apply one visual language: the same notation for actual, plan and forecast, the same colours for favourable and unfavourable variances, small multiples instead of a new chart type on every page, and titles that state the finding rather than the topic. Many organizations get there in two steps: first a redesigned pack of a few pages, then a single page once leaders trust the numbers and the notation.
Automate the commentary
The line of commentary under each chart absorbs much of the monthly effort, and it is the part AI now drafts well. Copilot in Power BI and similar assistants can summarize what a page shows; the discipline lies in the rules around them. Explain only movements beyond the agreed threshold. Cite the driver and the number in every sentence. Say when the data is incomplete. Keep the same order every time.
During the month, the briefing updates on its own and labels its commentary as automatic. At month end, when the numbers are final, the owner of each number reviews the explanation before it is marked as approved. Readers soon learn which state they are looking at, and the review takes minutes rather than days. Keep a record of what the AI wrote and what the owner changed; over a few months, it shows where the rules need tightening and where the drafts can be trusted.
Retire the rest, deliberately
Retirement is where simplification efforts tend to stall, because nobody wants to be the person who removed a page someone needed. Announce a date, keep the old packs in an archive for a while, and offer a simple way to ask for anything that is missed. Requests tend to be rare, and each one is a useful signal of a gap in the briefing. Some pages will survive for good reasons, such as a regulatory schedule or a board requirement; move them into the governed reporting platform rather than keeping them alive as slides.
Measure what changes: hours of production removed, how often each role opens the briefing, and the questions it prompts. Retire packs in small steps, and confirm that each one is truly replaced before moving to the next, the same way a sound platform migration moves in thin slices.
What changes for leaders
Meetings start from the same page, and that page is always current, so no time is lost establishing which version of the numbers is right. Discussion moves to the few movements that matter and the decisions they call for. Questions that once waited for next month’s pack are answered from the detail behind the briefing, often during the meeting itself. Analysts, freed from rebuilding slides every month, spend their time on the analysis the briefing points to.
The forty slides do not vanish overnight. But once leaders have read a page that is always current, explains itself and never contradicts the detail, few of them ask for the pack back.