A decision memo is useful when a conversation has reached the point where someone must choose, but the choice is still moving around in notes, chats, and meeting comments. It is not a project brief, a status update, or a transcript. It is a short argument that makes one decision clear enough to debate and act on.
To write one, put the exact decision first, name the owner, show the real options, separate evidence from assumptions, state the trade-offs, make a recommendation, and close with the next action plus a revisit trigger. Everything else earns its place by helping the reader make the call.
Start with the decision, not the background
The first paragraph should tell the reader what choice is being requested. Background can follow. If the reader has to reach page two to discover the question, the memo has already made the work harder.
Use a sentence that includes the action, scope, timing, and reason:
Decision: Choose [action] for [scope] by [date] because [the condition that makes the choice necessary].
Compare a vague prompt such as "Should we improve the onboarding experience?" with a decision that can actually be answered: "Should we release the revised onboarding flow to the next customer cohort on September 1, or hold the release until the support handoff is complete?"
The second version gives the reader a boundary. It identifies the object of the decision, the timing, and the constraint. It also makes it possible to say what evidence would change the answer.
The seven sections of a useful decision memo
1. Name the call and the decision owner
State the choice in one or two sentences, then name the person who has authority to make it. A recommender can gather evidence and write the memo. The decision owner is the person who accepts the consequences. Those roles may be the same, but they should not be left implied.
Also name the people who will implement the decision or need to be consulted. Clear decision rights keep the memo from becoming a group exercise with no finish line.
2. Explain why the decision is needed now
Give the minimum context that changes the call. That could be a deadline, a dependency, a customer signal, a capacity limit, a new risk, or a choice that has been deferred long enough to create cost.
Do not write the history of the entire project. Write the pressure that makes a decision necessary today. If a paragraph would remain true but would not affect the choice, it belongs in an appendix or nowhere.
3. Put real options on the table
List two to four options that could genuinely be chosen. Include the option to defer or do nothing when that is a real path. Do not present one preferred answer beside two weak alternatives designed to lose. A memo earns trust by showing the choice set fairly.
For each option, give the practical description, the condition it serves, and the main cost. A short list is more useful than a catalog of every imaginable variation.
4. Separate evidence from assumptions
Facts and beliefs do different jobs. A fact might be a confirmed deadline, a measured constraint, or a customer request. An assumption is a belief about what will happen if the team chooses a path. Label both.
Then ask which evidence would actually change the decision. This keeps the memo from becoming a research dump. Include the signals that help the owner judge the options, not every tab opened while preparing the document.
5. Make the trade-offs visible
Every choice spends something. It may spend time, focus, money, capacity, speed, flexibility, or an opportunity to do something else. Name that cost plainly.
Risks belong here too, but do not turn the section into a fear inventory. Describe the risk, its likely consequence, and the indicator that would show the plan is drifting. A decision memo should make the price of each path easier to see.
6. Make a recommendation
The recommendation is not a summary of the options. It is a call. State which option you support and why it best fits the decision criteria, current constraints, and timing.
Include the strongest argument against your recommendation. A real objection is more useful than a ceremonial one. If you cannot explain why a reasonable person might choose another path, you may still be describing the debate instead of resolving it.
7. Close with implications and a revisit trigger
Tell the reader what happens if the recommendation is accepted. Name the first action, the owner, the timing, the communication required, and any commitment that changes.
Then state what would cause the team to revisit the call. A trigger might be a missed milestone, a new constraint, a customer signal, or an assumption that proves false. The trigger turns the memo into a living control point instead of a document that goes stale after the meeting.
Know which document you are writing
Many project documents overlap in language, but they answer different questions. A project brief defines the work: purpose, scope, audience, constraints, and intended result. A status update describes the current condition: what moved, what changed, what is blocked, and what needs attention.
A decision memo asks for a choice. A decision log records the choice after it is made so the reasoning, owner, and accepted trade-offs do not disappear into memory. You may use all four in one project, but combining them into one sprawling document usually makes each job less clear.
Use a one-page test before you send it
A short decision memo is not automatically a good one. Use this final check:
- Can a reader state the decision after reading the first paragraph?
- Is the decision owner named?
- Are the available options real, including defer when relevant?
- Are facts separated from assumptions?
- Does each trade-off connect to a consequence?
- Is there a clear recommendation?
- Does the memo say what happens next and what would reopen the call?
If the answer to any of these is no, edit the structure before polishing the language. Clear headings, short paragraphs, and direct sentences help the reader inspect the reasoning without turning the memo into a performance.
Make the decision usable after the meeting
The memo is not finished when someone says yes. Update it with the final call, the date, the owner, the reason, and the trade-offs the team accepted. Record the first action and the revisit trigger in the place where the project will actually be managed.
That small act protects the work from quiet revision. People can disagree before the decision, execute after it, and learn from it later without reconstructing the entire conversation.
A practical uniform can support that kind of focused work without becoming the point of it. The Standard Issue Crewneck is a no-hood layer in heavy-blend fleece with ribbed trim and an embroidered white mark at the left chest. If your writing block calls for a quiet, structured layer, that is its use case.
For more frameworks on making the work clearer, visit The Self Made Journal. The goal is simple: make the choice visible, make the next move owned, and leave less ambiguity for the people who have to carry it forward.
0 comments