A consultant I rate highly sent me a proposal where the recommendation appeared on page 4. Thorough, well-argued, and structured entirely for the writer's comfort. I pulled out a proposal I'd sent the week before. Mine was on page 3. We were both doing the same thing.
The proposal arrived on a Tuesday. Six pages, well laid out, from a consultant whose work I respect a lot.
I read it twice before I trusted it. The first time through, I kept waiting for the point. There was a thorough background section, then a section on methodology, then a market overview, then two pages of analysis. The recommendation arrived at the top of page 4. By that point I'd forgotten the framing well enough that I had to go back and re-read the beginning before I could assess whether I agreed.
I told a colleague about it that afternoon, half-joking. Then I opened a proposal I'd sent the previous week. Executive summary, background, analysis, recommendation. The recommendation was on page 3.
I'd been doing exactly the same thing.
Journalism solved this a hundred years ago
Compelling Communication has a section on the Inverted Pyramid that I keep coming back to. Journalists developed it in the nineteenth century as a response to a practical problem: telegraph wires cut out. If your story got transmitted halfway, the most important information had to have gone first. Background and context went at the bottom, where they could be cut without losing the story.
Business writing went the other direction. Context first, to establish credibility. Analysis next, to demonstrate rigour. Recommendation at the end, once the reader is sufficiently persuaded by the work that preceded it. The structure serves the writer's need to justify the conclusion before stating it.
The problem is that readers scan. They don't start at the top and work methodically to the bottom. They jump to the conclusion first, decide whether they want to invest in reading the reasoning, and then go back. If the conclusion is on page 4, they skip straight to it. The three pages of context you provided to build up to it get ignored entirely.
Your reader doesn't need to follow your thinking to trust your conclusion. They need your conclusion first, then they'll decide whether to read the thinking.
Kipling had a completeness check for this: his Six Honest Serving Men. What, Why, When, How, Where, Who. The Inverted Pyramid doesn't eliminate any of them. It reorders them. What comes first. The rest follows in descending order of importance.
Who the structure is actually serving
I've thought about this a fair amount since that Tuesday. The context-then-conclusion structure is comfortable to write. You build the case. You establish the situation. You walk the reader through your thinking in the order you did the thinking. The recommendation lands at the end, supported by everything that came before it, and it feels earned.
The issue is that this sequence is built for the writer's comfort, not the reader's need.
Readers don't need to follow the reasoning to arrive at the conclusion. They need the conclusion stated plainly, and then they'll decide whether to invest time in the reasoning. If the conclusion sounds wrong on first read, they want to understand why you reached it. If it sounds right, they want confirmation. Either way, they start with the answer.
Structure built around justifying the answer before stating it is built for the writer, not the reader.
There's also something slightly defensive about the traditional structure. Burying the conclusion in analysis is a way of softening the blow if it's unwelcome. The reader has been warmed up by pages of careful argument by the time they reach it. The argument has been pre-loaded. It's a reasonable instinct. It's also a way of making the document harder to read.
What front-loading looks like
The mechanics of the Inverted Pyramid in a proposal are simple enough.
Executive Summary / Background / Analysis / Recommendation / Next Steps
Recommendation / Why / Evidence / Context (if needed)
The recommendation goes first. One clear sentence, no qualifications. Then the primary reason you arrived at it. Then the evidence that supports the reason. Then any context that helps the reader understand the constraints you were working with. Background, methodology, and market overviews go at the bottom, where they're available if someone wants them and invisible if they don't.
The uncomfortable part is stating the conclusion before you've shown your working. It feels presumptuous. It removes the buffer that the traditional structure provides. If the reader disagrees with the recommendation, they'll push back on it immediately rather than sitting with the argument first.
That's actually better. A reader who disagrees with a recommendation on page 4 disagrees with it having spent four pages getting there. The conversation that follows is longer and harder than it needs to be. A reader who disagrees with a recommendation on page 1 tells you immediately, before anyone has invested more time than necessary.
The consultant whose proposal I read that Tuesday is good at their work. The recommendation was sound. The document would have been easier to use if it had arrived on page 1. I know this because I've now restructured two of my own proposals and the conversations they opened were cleaner and faster. The thinking doesn't get shorter. It just goes where it's actually needed, which is after the answer, not before it.
