One Pager

One Pager

The person this is written for was not in the room, did not ask for it, and is reading it because someone they trust forwarded it. They will give it forty seconds.

Everything follows from that. It is not a summary of what happened. It is the shortest thing that lets a stranger make a decision or hold an accurate view.

The failure this exists to prevent: the document the sponsor rewrites before sending. The moment they have to edit it, two things are true: it did not sound like them, and you have lost control of what their leadership actually reads.

What this needs

Shared context. If an account-context document exists, read it first for the value metric, which is the unit any number in here has to be expressed in. Where it is absent, carry on and name the assumption.

Minimum: what happened and who it is for. Enough to produce the structure and the opening.

Better with the customer's own goals in their words, and any prior document their leadership has already seen, because matching that format matters more than improving on it.

Best with their numbers rather than yours, and a sense of what the forwarder will be asked when they send it.

Step 0: Establish which of three documents this is

They look similar and they are not. Getting this wrong is why most one-pagers do nothing.

• A decision brief. The reader has to choose. It leads with the recommendation, gives the options actually considered, and names what happens if they do nothing
• An information brief. The reader has to hold an accurate view, usually because they will be asked. It leads with the state of things and anticipates the question they will get
• An advocacy brief. The forwarder is arguing for something internally. The reader is the person they have to convince. This one is closest to expansion-case, and if it is specifically about budget for additional scope, use that skill instead

Say which one it is before writing a word. A decision brief with no decision in it is the most common failure in this category.

Step 1: Write for the forwarder, not for yourself

The sponsor is the real client here. They are putting their name on this by sending it.

• Never include a claim they do not already believe. If they have to defend something you asserted, they will delete it, and they will trust the next document less
• Use their vocabulary. Their name for the project, their metric names, their team names. Not your product names, not your tier names, not your internal terms for stages
• No logo, no branding, no template. The moment it looks like a vendor document it is read as a vendor document, which means it is read as arguing rather than informing
• Give them the line to write above it. One or two sentences they would actually type when forwarding. That line does more work than the document, and almost nobody writes it for them

Step 2: Put the conclusion in the first three lines

No background, no context-setting, no "as you may know". The reader has forty seconds and the first three lines are what they spend them on.

• Line one: the conclusion. What is true, or what is being recommended
• Line two: why it matters to them, in cost, risk, revenue or time
• Line three: what is being asked, or explicitly that nothing is

Everything below those three lines exists to support someone who wants to check. Most readers will not go further, and that is a successful document, not a failed one.

Step 3: One page means one page

Not "about a page". If it does not fit, the problem is scope rather than formatting, and shrinking the font is a way of avoiding the decision about what to cut.

• Three or four sections, each with a heading that carries meaning on its own
• Short paragraphs, and a table only where it genuinely beats prose
• No appendix. If something needs an appendix it is a different document, and it can be offered rather than attached

Cut anything that is only there to show effort. Length reads as effort to the person who wrote it and as an obstacle to the person who did not.

Step 4: Make every number theirs and checkable

• Their unit, their reporting period, their definition
• Sourced. Where it came from and when, in the line itself or a short note
• Estimates marked as estimates, with the basis. A range with a stated assumption survives a finance team; a precise figure with no basis does not
• Nothing that only exists in your dashboard, unless you explain what it is, in which case ask whether it belongs at all

The test: could the reader disagree with this number and go and check. A number nobody can check is decoration.

Step 5: Anticipate the one question the forwarder will be asked

Whoever sends this gets a reply, and it is usually a single predictable question: what does it cost, what happens if we stop, is this working, who else does this.

Work out which one it will be and answer it inside the document, briefly. A sponsor who cannot answer the first question they get is a sponsor who stops forwarding things.

Step 6: Deliver it in a form that travels

• Body text or an editable document. A PDF is harder to forward with an edit and impossible to paste into a message, and the sponsor will paste it
• No tracking that shows in the document. A link that visibly reports back changes how it is read and how freely it is passed on
• Where a file is genuinely needed, keep the filename plain and dated, with no vendor name and no version number in it

Then ask the sponsor to read it before it goes anywhere. That single step catches the vocabulary problem, which is the one you cannot catch yourself.

Output

1. Which of the three it is: decision, information or advocacy
2. The three opening lines, written out
3. The page itself, three or four sections, one page
4. Every number in their unit, sourced, estimates marked
5. The anticipated question, answered inside the document
6. The line the forwarder writes above it
7. The delivery format, and who reads it before it goes
8. What you could not check

assets/one-pager-template.md is the skeleton, written to be filled in and handed over.

Failure modes

• The document the sponsor rewrites. It did not sound like them, and now their leadership reads a version you never saw
• No decision in a decision brief. The most common failure here
• Background first. Three lines of context and the point in paragraph two, read by nobody
• Your vocabulary. Product names, tiers, internal stage names. Each one costs a line to explain and marks the document as external
• A logo on it. It stops being information and becomes a pitch
• Two pages. The scope was never decided, and the font got smaller
• Numbers only checkable in your dashboard, which cannot be argued with and therefore cannot be believed
• A claim the sponsor does not hold. They delete it, and they trust the next one less
• Sending a PDF. It gets pasted anyway, badly
• Not writing the covering line, leaving the highest-leverage sentence to somebody in a hurry

What good looks like

• The sponsor forwarded it without changing a word
• Someone reading only the first three lines has the point
• It is one page
• Every number is theirs, sourced, and checkable by someone who wants to disagree
• The obvious follow-up question is already answered in it
• There is no logo on it and no product tier named in it
• The covering line was written for them

Related skills

• expansion-case when the document is specifically a budget case for additional scope
• business-review when this is the leave-behind from a review rather than a standalone
• customer-update when the audience is a list rather than one sponsor's boss
• exec-conversation when the senior person can be reached directly instead
• email-critic on the covering message that carries it

Supporting files

• assets/one-pager-template.md - the skeleton, usable without an assistant