First published , revised
The Art of the Decision Memo
How to write for executives who do not have time to read: the context, the complication, the recommendation and the tradeoff.
Ten minutes
You spent three weeks building a sixty-slide deck. You have the data, the charts, the sensitivity analysis and the appendix. You walk into the board meeting and the chair says she has ten minutes, and would you please just tell her what needs to be decided.
If you cannot state the tradeoff in the first paragraph, you have not finished thinking yet. That is the whole discipline of the decision memo, and it is a discipline most organizations never learn because slide software lets them avoid it.
Why prose wins
Jeff Bezos famously banned PowerPoint at Amazon in favour of six-page narrative memos, and his reason was simple: bullet points allow for lazy thinking. "We need to optimize the customer funnel" is a bullet point that everyone nods at and nobody understands. "We need to remove the email verification step because it causes a twenty percent drop-off, even though it will raise spam complaints by an estimated fifteen percent" is a sentence that forces a decision. The first is a status update. The second is a recommendation with consequences attached.
The structure we teach
We train teams to write decision memos rather than update reports, and a decision memo has a fixed shape built for speed.
It opens with the context, which answers why we are talking about this now. Something changed: the vendor contract expires in forty-five days, or the provincial funding guidelines were revised last week and the organization no longer qualifies under the old model. Then comes the complication, which explains why the status quo is no longer viable and what breaks if nothing is done. This is where urgency is earned. If there is no real complication, the situation does not need a decision memo. It needs a project plan.
The recommendation follows, in one clear and unambiguous sentence: we should pursue option B and defer option C to the third quarter. Do not hedge, and do not present three options and ask the executive to choose. Your job is to synthesize the analysis and make a call. Their job is to approve it, reject it or challenge its logic.
Last, and most often skipped, comes the tradeoff. Every strategic choice carries a cost, whether financial, operational, reputational or a matter of time, and pretending otherwise costs you credibility. Say it plainly: option B delivers faster, but it deepens our dependence on a single vendor and raises operational risk by roughly fifteen percent, which a six-month contract review clause can mitigate. Naming the tradeoff does not weaken the recommendation. It shows the reader that the thinking has been done.
Writing is thinking
A memo forces you to connect the logic in a way slides never do. Slides let you gesture at an idea. Prose makes you defend it. If you cannot write a coherent two-page argument for your recommendation, you are probably not ready to make it, and the gaps in the reasoning become obvious the moment you try to write in full sentences.
Respect their time and they will respect your call
The executives I work with in Canada, chief executives of mid-sized firms, municipal chief administrative officers, executive directors of non-profits, do not have time to hunt for the point. They are managing competing priorities, tight timelines and board scrutiny. Do the hard work of synthesis before you press send. Strip out the vanity metrics, the hedging and the "for your consideration" phrasing. If you respect their time, they will respect your recommendation. If you waste it, they will stop reading your memos altogether.