The single page that gets you in the room

There's a piece of paper that has changed the trajectory of more careers I've coached than any other artifact. It's a single page. It can describe a project, a strategic recommendation, a budget request, a quarterly view, or a major decision. The format barely changes.

The reason it matters is that this is the artifact senior leaders actually read. Decks get glanced at. Long emails get put off. Meetings get rescheduled. One-pagers get read on the way to another meeting, on a phone, in the back of a car, three minutes before the conversation they're meant to inform.

If you can produce a strong one-pager on demand, you become the person senior leaders quietly route their thinking through. That's the position. That's the unlock.

The structure

Six blocks, in this order. Each one a short paragraph, three to four lines maximum. The whole thing fits on one side of A4, in a readable font, with white space.

Block one: The situation. One paragraph describing what's true right now. No analysis. No recommendation. Just the operational reality. "Q3 revenue is tracking 8 per cent under plan, driven primarily by softness in the SMB segment, which represents 34 per cent of total revenue."

Block two: The decision required. One paragraph naming what specifically needs to be decided, by whom, and by when. "A decision is needed by end of Q3 on whether to invest an additional £600k in SMB acquisition spend, or to accept a £1.2m revenue shortfall and reset the FY plan."

Block three: The recommendation. One paragraph stating what you recommend, in one sentence, then the two or three pieces of reasoning that justify it. "Recommend investing the £600k, focused on the inside-sales channel where customer acquisition cost is 30 per cent below the SMB average. This is expected to recover £900k of the shortfall and protect the FY plan within tolerance."

Block four: The risks. One paragraph stating the two or three most significant risks of the recommendation, with a sentence on how each one is being mitigated. Crucially, name the risks honestly. A one-pager that pretends there are no risks reads as either naive or dishonest, neither of which builds trust.

Block five: The alternative. One paragraph describing the next-best option, the trade-offs against your recommendation, and why you've chosen what you have. "Alternative: accept the shortfall and reset. This is more conservative on cash but creates a public miss that may affect investor confidence and FY momentum."

Block six: The ask. One paragraph stating exactly what you need from the senior person. A decision. A meeting. An introduction. A piece of air cover. Make it specific.

Why the structure works

This sequence matches how senior decision-makers actually want to consume information. They want to know what's going on, what they're being asked to decide, what you think, why they should believe you, what could go wrong, what else they could do, and what you need from them. In that order.

When you give them the information in that order, they can read the page in three minutes and arrive at the meeting already 60 per cent ready to make the call. That's the whole point. You're trying to reduce the cognitive cost of the decision for them, not to demonstrate the breadth of your analysis.

Most one-pagers fail because they don't separate the blocks cleanly. They mix recommendation into situation. They bury the ask. They explain methodology where there should be a decision statement. Once the page is muddled, the senior person scans it once, parks it, and asks for a meeting to talk it through. You've just multiplied your own effort.

The two-page exception

The temptation, when you produce your first few one-pagers, is to make it a two-pager because "there's too much to fit". Resist this.

The discipline of fitting it on one page forces you to find what actually matters. The bit you couldn't fit was, almost without exception, the bit that wasn't load-bearing. Including it in the document would have weakened the page, not strengthened it.

If you genuinely need an appendix (data tables, methodology notes, supporting calculations), that's fine. Put it on page two and label it Appendix. The main page stays single, scannable, and decision-ready.

A worked example

I had a client at a healthcare company who'd been trying for fourteen months to get sign-off on a digital infrastructure project worth £4.8m over three years. Every previous attempt had been a deck. None of them had landed.

We rewrote it as a one-pager. Six blocks. Half a side of A4 once formatted. Inside two weeks, she had the meeting she'd been chasing for over a year. Inside six, the project was approved.

The information was identical. The structure changed everything.

"If you can't put it on one page, you don't understand it yet." A line from a senior partner at McKinsey that I've kept with me ever since.

Practise this week on something small. A project status. A team update. A view on a hiring decision. Force yourself onto one page. The first three attempts will feel like surgery. The fourth one will feel natural. By the tenth, you'll wonder why you ever used decks at all.