Tip 03 · 17 November 2026
Report in a pyramid structure
You build your analysis from the bottom up. You tell your story from the top down.
The project team had worked hard for six weeks, gathered a mountain of data and translated it into plans and timelines. When I read the draft final report, I could not believe my eyes. The titles were questions, or conclusions that the facts on the page did not support. The story disappeared behind the details. I intervened. The team spent the rest of the day on titles that matched the supporting evidence, following the lessons of Barbara Minto.
The mistake is understandable. Working from the details for six weeks is something else than formulating a clear story for the board. The reader does not need to retrace your search. They want to know the conclusion first, and then understand what it rests on.
There is something important on top of that. Boards that regularly read reports from McKinsey and similar consultancies get used to that structure: first the main conclusion, then the supporting evidence. Those reports, as it were, train the way they read. This creates an expectation that also applies when an internally written report lands on the boardroom table. Even before the discussion about content starts, the reader notices whether the structure matches what they are used to.
That is why the pyramid structure introduced by Barbara Minto is also relevant for internal reports. Start with the main conclusion and work out the supporting evidence. Give every content page a clearly worded conclusion as its title. The facts on that page must carry the conclusion. Then read only the titles: do they form a logical story together? And does the report title state the main conclusion of that story?
A question as a title leaves the reader still searching for the answer. As the author, you should show which conclusion you draw from the facts. That gives the board something concrete to assess and discuss.