What is Memo?
A memo is a concise internal document used to communicate a decision, recommendation, policy, analysis, operational update, or request for action to a defined workplace audience. A decision memo is a memo variant that makes the decision, alternatives, evidence, tradeoffs, and requested authority especially explicit.
What good memo looks like
A good memo lets a busy reader understand the purpose and bottom line early, then provides the minimum background, evidence, implications, alternatives, and next steps needed to act. For a decision memo, the requested decision and the reasoning that supports it should be recoverable without reading a chronological history first.
- Use a clear subject or title that names the issue.
- Lead with the decision, recommendation, or purpose.
- Separate background from analysis and action.
- Use headings for longer memos.
- Name owners, deadlines, and required responses explicitly.
A practical structure to follow
Use these elements as a decision checklist, not as a rigid formula. The exact wording should still fit the reader, context, and purpose.
- Use a clear subject or title that names the issue.
- Lead with the decision, recommendation, or purpose.
- Separate background from analysis and action.
- Use headings for longer memos.
- Name owners, deadlines, and required responses explicitly.
Trace the visible problem back to the writing decision
Do not fix only the sentence that looks weak. Use the symptom, underlying issue, test, and correction columns to identify why the draft is failing and what change actually addresses the cause.
| Failure mode | Likely underlying issue | What to test | Correction |
|---|---|---|---|
| Burying the recommendation after several paragraphs of context. | Use a clear subject or title that names the issue. | Test the draft against this question: Identify the reader and the decision or knowledge gap. | Identify the reader and the decision or knowledge gap. |
| Writing a chronological narrative when the reader needs a decision. | Lead with the decision, recommendation, or purpose. | Test the draft against this question: Write the bottom line in one or two sentences. | Write the bottom line in one or two sentences. |
| Using vague next steps such as “we should consider.” | Separate background from analysis and action. | Test the draft against this question: Add only the background needed to understand it. | Add only the background needed to understand it. |
Choose between this technique and its nearest alternatives
Nearby writing concepts often overlap in vocabulary while solving different jobs. Compare the success criteria directly so you choose the technique because it fits the task—not because the label sounds familiar.
| Nearby technique | Use this guide when… | Prefer the alternative when… | Key distinction |
|---|---|---|---|
| Professional Email | Use Memo when its core job is: A good memo lets a busy reader understand the purpose and bottom line early, then provides the minimum background, evidence, implications, and next steps needed to act. | Prefer Professional Email when its core job is: The best professional email can be scanned quickly: the recipient knows why they are receiving it, what information matters, what action is needed, who owns that action, and any relevant deadline. | Choose by the writing job, not keyword similarity; keep the definition and success criteria of each technique separate. |
| Meeting Agenda | Use Memo when its core job is: A good memo lets a busy reader understand the purpose and bottom line early, then provides the minimum background, evidence, implications, and next steps needed to act. | Prefer Meeting Agenda when its core job is: A strong agenda helps people prepare before the meeting and makes the desired outputs visible. It distinguishes decision items from updates that could be handled asynchronously. | Choose by the writing job, not keyword similarity; keep the definition and success criteria of each technique separate. |
| Executive Summary | Use Memo when its core job is: A good memo lets a busy reader understand the purpose and bottom line early, then provides the minimum background, evidence, implications, and next steps needed to act. | Prefer Executive Summary when its core job is: A strong executive summary stands on its own, leads with the main conclusion rather than background, preserves the source document’s important qualifications, and makes recommended actions or decisions easy to locate. | Choose by the writing job, not keyword similarity; keep the definition and success criteria of each technique separate. |
Separate choices that look similar but solve different writing jobs
Many weak revisions come from choosing a nearby technique because its label sounds right. These worked contrasts compare success conditions directly and link to the alternative when that other tool truly fits better.
| Looks similar to… | Why they are easy to confuse | Use this guide when… | Use the alternative when… |
|---|---|---|---|
| Professional Email → | Both can appear relevant because they address nearby decisions in professional-writing. | Use Memo when the real success condition is: A good memo lets a busy reader understand the purpose and bottom line early, then provides the minimum background, evidence, implications, and next steps needed to act. | Use Professional Email when its distinct success condition is the real job: The best professional email can be scanned quickly: the recipient knows why they are receiving it, what information matters, what action is needed, who owns that action, and any relevant deadline. |
| Meeting Agenda → | Both can appear relevant because they address nearby decisions in professional-writing. | Use Memo when the real success condition is: A good memo lets a busy reader understand the purpose and bottom line early, then provides the minimum background, evidence, implications, and next steps needed to act. | Use Meeting Agenda when its distinct success condition is the real job: A strong agenda helps people prepare before the meeting and makes the desired outputs visible. It distinguishes decision items from updates that could be handled asynchronously. |
| Executive Summary → | Both can appear relevant because they address nearby decisions in professional-writing. | Use Memo when the real success condition is: A good memo lets a busy reader understand the purpose and bottom line early, then provides the minimum background, evidence, implications, and next steps needed to act. | Use Executive Summary when its distinct success condition is the real job: A strong executive summary stands on its own, leads with the main conclusion rather than background, preserves the source document’s important qualifications, and makes recommended actions or decisions easy to locate. |
See what each writing choice causes downstream
Two choices can both look competent at sentence level while sending the draft in different directions. Compare the immediate benefit, hidden trade-off, and downstream consequence before committing to a structure, claim, scene move, tone, or workflow.
| Writing choice | What it helps | Trade-off / failure risk | Downstream consequence |
|---|---|---|---|
| Use a clear subject or title that names the issue. | Identify the reader and the decision or knowledge gap. | Burying the recommendation after several paragraphs of context. | If this choice is wrong, later revisions will compensate for the wrong problem instead of improving Memo. Recheck the reader, evidence, genre, authority, or purpose before adding more detail. |
| Lead with the decision, recommendation, or purpose. | Write the bottom line in one or two sentences. | Writing a chronological narrative when the reader needs a decision. | If this choice is wrong, later revisions will compensate for the wrong problem instead of improving Memo. Recheck the reader, evidence, genre, authority, or purpose before adding more detail. |
| Separate background from analysis and action. | Add only the background needed to understand it. | Using vague next steps such as “we should consider.” | If this choice is wrong, later revisions will compensate for the wrong problem instead of improving Memo. Recheck the reader, evidence, genre, authority, or purpose before adding more detail. |
Verify the parts that cannot be solved by prose quality alone
Fluent writing cannot make an unsupported claim, broken canon fact, stale submission rule, incorrect quotation, unauthorized commitment, or model-generated detail true. Use this table to identify what needs an external check and what evidence is strong enough.
| What to verify | Acceptable standard | Red flag | Final verification move |
|---|---|---|---|
| Operational fact | For Memo: Dates, amounts, owners, status, decisions, policy text, and commitments are confirmed. | Turning a draft assumption or meeting impression into an official fact. | Separate confirmed fact, proposal, forecast, and open question before sending. |
| Authority and approval | For Memo: The writer has authority to make the promise, decision, policy statement, or external claim. | Confident wording creating an unintended commitment or admission. | Confirm decision owner, approval state, legal/HR sensitivity, and audience before publication. |
| External evidence | For Memo: Performance, customer, market, legal, and factual claims have traceable support. | Using persuasive language as a substitute for substantiation. | Attach source, date, scope, and uncertainty to claims that could be challenged. |
When two plausible versions are both reasonable, choose the one that serves the real job
Correctness is only the first filter. These pairs use examples from this topic to show why audience, evidence, genre, stakes, or intended reader action can make one version a better fit even when both are grammatically or structurally defensible.
| Real purpose | Plausible option A | Plausible option B | Purpose-fit test |
|---|---|---|---|
| Inform or document | Recommendation: Move the support handoff to 4 p.m. so the receiving team has one hour of overlap with the outgoing shift. | Decision: Beginning October 1, all customer-facing policy changes require a plain-language review before publication. | Both choices can be defensible Memo examples. For “Inform or document”, choose the version whose structure, evidence/story support, tone, and level of certainty most directly serve that purpose; do not choose by polish or length alone. |
| Get a specific decision or action | Issue: The current intake form collects three fields that are never used downstream, adding time without affecting eligibility. | Finding: Most delayed approvals occur when requests arrive without an owner, not when reviewers lack capacity. | Both choices can be defensible Memo examples. For “Get a specific decision or action”, choose the version whose structure, evidence/story support, tone, and level of certainty most directly serve that purpose; do not choose by polish or length alone. |
| Persuade under accountability or reputational risk | Risk: Launching before the vendor migration is complete would create two sources of customer status data. | Next step: Operations will publish the revised checklist by September 15; team leads will confirm adoption by September 22. | Both choices can be defensible Memo examples. For “Persuade under accountability or reputational risk”, choose the version whose structure, evidence/story support, tone, and level of certainty most directly serve that purpose; do not choose by polish or length alone. |
What to learn next
These links follow the writing decision rather than alphabetical similarity. Use them as a short path from the current concept to the next structural, evidence, revision, or publishing decision.
How to write memo step by step
- 1Identify the reader and the decision or knowledge gap.
- 2Write the bottom line in one or two sentences.
- 3Add only the background needed to understand it.
- 4Present evidence or options in a scannable structure.
- 5State implications, risks, and next steps.
- 6Edit for unnecessary history and repeated conclusions.
200 Memo examples
Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.
Recommendation: Move the support handoff to 4 p.m. so the receiving team has one hour of overlap with the outgoing shift.
Decision: Beginning October 1, all customer-facing policy changes require a plain-language review before publication.
Issue: The current intake form collects three fields that are never used downstream, adding time without affecting eligibility.
Finding: Most delayed approvals occur when requests arrive without an owner, not when reviewers lack capacity.
Risk: Launching before the vendor migration is complete would create two sources of customer status data.
Next step: Operations will publish the revised checklist by September 15; team leads will confirm adoption by September 22.
Memo templates
Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.
To: [audience] From: [author] Date: [date] Subject: [specific issue] Bottom line: [decision/recommendation] Background: [necessary context] Analysis: [evidence/options] Next steps: [owner + date].
Decision memo: Decision | Why now | Evidence | Alternatives considered | Risks | Owner | Review date.
Recommendation memo: Recommendation | Problem | Evidence | Options | Tradeoffs | Proposed next step.
Common mistakes to avoid
- Burying the recommendation after several paragraphs of context.
- Writing a chronological narrative when the reader needs a decision.
- Using vague next steps such as “we should consider.”
- Attaching evidence without explaining what conclusion it supports.
Final revision checklist
- Does the opening make the purpose clear quickly?
- Is every important claim, detail, or example doing a distinct job?
- Could a reader misunderstand any pronoun, transition, time reference, or instruction?
- Is the tone appropriate for the relationship and situation?
- Can you remove repetition without removing necessary context?
- If the writing contains factual claims, names, dates, quotations, or citations, have you verified them independently?
Questions about Memo
What is Memo?
A memo is a concise internal document used to communicate a decision, recommendation, policy, analysis, operational update, or request for action to a defined workplace audience. A decision memo is a memo variant that makes the decision, alternatives, evidence, tradeoffs, and requested authority especially explicit.
What makes Memo effective?
A good memo lets a busy reader understand the purpose and bottom line early, then provides the minimum background, evidence, implications, alternatives, and next steps needed to act. For a decision memo, the requested decision and the reasoning that supports it should be recoverable without reading a chronological history first.
How do I write Memo?
Start with the purpose and reader, then work through the structure in order. Draft for meaning first, check the examples for pattern, and do a final revision for clarity, accuracy, tone, and unnecessary repetition.
What should I avoid when writing Memo?
Burying the recommendation after several paragraphs of context. Writing a chronological narrative when the reader needs a decision. Using vague next steps such as “we should consider.”
How do I know which version of Memo fits my situation?
Start with the job the writing must perform, then compare audience, length, evidence, genre, and stakes. The worked-scenario section shows how the same broad technique changes under different constraints, and the guided path links the next concept to check when the problem actually belongs to a neighboring writing decision.
What should I practice first if I am learning Memo?
Start with the beginner example and make the core writing job unmistakable. Move to the intermediate example only after you can explain which additional constraint it introduces. The advanced example then shows how the same principle changes when evidence, audience, genre, stakes, or publication context becomes harder. Use the skill ladder for the next neighboring concept instead of trying to master every related topic at once.
What should I do when the usual Memo advice does not fit my situation?
Identify the constraint that changed first: audience knowledge, evidence quality, length, genre, stakes, workflow, or publication context. Keep the core job of Memo intact, then adapt the surface pattern. The constraint-comparison examples on this page show what can change without losing the underlying writing decision.
What misconception should I avoid when using Memo?
A common shortcut is: Burying the recommendation after several paragraphs of context. A better correction is: Identify the reader and the decision or knowledge gap. The principle to preserve is: Use a clear subject or title that names the issue. Use the misconception table on this page to separate a surface rule from the actual writing decision.