The one-pager that gets a decision

Analysis is not a decision

A great deal of good work dies in a document that describes what was found and never says what to do. The reader (busy, three levels up, holding a budget) reaches the end without knowing what is being asked of them, and files it.

The skill that converts technical work into influence is the ability to write a page that produces a decision. It is learnable, it is rarer than it should be, and it is the most reliable route from doing good work to being trusted with more of it.

Put the ask first

Technical writing is trained backwards: method, results, then conclusion. Decision writing inverts it, because the reader may stop at any point and you want them to have the answer before they do.

Compare the same work in two openings.

“We analysed churn across the last four quarterly cohorts using a survival model, controlling for plan type and acquisition channel. The results indicate…”

Nobody above your manager reads past that.

“Recommendation: move the annual renewal reminder from 7 days before expiry to 30 days. Expected effect: 1.5 to 3 percentage points of annual churn, worth ₹40 to ₹80 lakh a year. Cost: about two engineering weeks. Decision needed by 20 October to make the January cohort.”

Everything after that is evidence for a reader who wants it. Both documents contain the same work; only one of them will be acted on.

The structure

1. Recommendation. One or two sentences.
2. What it costs and what it is worth, with numbers.
3. The decision needed, from whom, by when.
4. The evidence, briefly, with the strongest thing first.
5. What would change my mind, or what we are uncertain about.
6. Alternatives considered and why they were rejected: this is what separates a recommendation from an opinion.
7. Appendix for the method, the queries, the caveats.

One page above the appendix. If it will not fit, the recommendation is not clear enough yet.

Number discipline

Every number in a decision document carries four things: what it measures, when, on what sample, and how uncertain it is.

Churn is 12%.

versus

Churn was 12.1% for the January cohort (n=400, ±3 points at 95%), where churn means no renewal within 30 days of contract end.

The second is longer and it is the one people trust, because a reader can tell what would break it. Stating uncertainty raises your credibility rather than lowering it: you have shown you know the difference between what you measured and what you know, which is exactly what a decision-maker is trying to establish about you.

Anticipate three questions

Every senior reader asks the same three, so answer them before they do:

• How do we know? One line on the data and its limits.
• What does it cost? Money, time and opportunity.
• What happens if we do nothing? The most commonly omitted section and often the most persuasive one.

The meeting

A pre-read circulated 24 hours in advance beats a presentation, because people can think. Some organisations go further and read the document silently at the start of the meeting (a practice Amazon is known for) precisely because slides let a weak argument sound strong.

If you must present: the first slide is the recommendation, the last slide is the recommendation, and the middle is evidence you may skip if the room has already agreed. Never build to a conclusion. There is no suspense in a budget meeting.

Email, briefly

Same rules, smaller. The subject line contains the ask: “Decision needed by Friday: renewal reminder timing”. The first line repeats it. The detail follows. If there is a deadline, it appears twice.

The limitation

Good writing does not defeat organisational politics. A perfectly argued memo proposing something a director does not want will sit unanswered, and you will not be told why.

Two things partly compensate. Know whose decision it actually is before writing: a document addressed to nobody in particular is decided by nobody in particular. And find out what that person is measured on, because a recommendation framed against their target is a different document from one framed against yours, even when the analysis is identical.