Understanding the Memorandum
A memorandum is just a written message, usually within an organization. That's really all it is. You've probably seen them on office desks or buried in email threads labeled "MEMO" at the top. They're formal enough to be taken seriously but informal enough that they don't require the full legal weight of a contract or policy document. The basic structure is straightforward: a heading with TO, FROM, DATE, and SUBJECT lines, followed by a body that gets to the point quickly. No preamble. No filler. Just the information you need someone to know.
What Is A Memorandum and How Does It Work?
I learned this the hard way early in my career. Someone handed me a memo about a new expense reporting system that ran three pages. Three pages. For a process that could have been explained in eight sentences. That memo got ignored entirely. Most people do ignore long memos. The real trick with memos is knowing when to use them versus when to just send an email. Here's where most people get it wrong: a memo is for information that needs to stick around. If you're announcing something permanent—like a new policy, a procedure change, or a structural update—a memo creates a record. An email disappears into the inbox void. Internal memos don't need the same formality as external correspondence. You don't need "Dear Sir/Madam" or "Yours faithfully." The subject line does the heavy lifting. Keep it specific. "Expense Policy Update Q3 2024" beats "Important Update About Expenses." People scan subjects faster than they read bodies.
One thing nobody tells you about memoranda: they're often used as evidence later. In disputes about whether a policy was communicated, whether someone was notified, or what was agreed upon internally, memos show up. I had to dig through archived memos from 2019 during a compliance audit once. The ones we'd written clearly with dates and specific action items took ten minutes to produce. The vague ones? Those took hours because nobody could agree on what they meant.
Get the Full Details
When to Write a Memo Instead of Something Else
Memos sit in an awkward middle ground. They're more permanent than an email but less formal than a policy document. Use them when you need a trail but don't want to create an official record. Policy documents get filed. Memos get archived and occasionally referenced. There's a common pitfall here. People tend to make memos feel more important than they are by dressing them up with corporate language. "We would like to inform you that..." This makes readers suspicious. If something required that much padding, they assume there's bad news. Skip the padding. "Starting November 1st, the submission deadline moves to Friday noon." Done. Another pitfall: distributing memos to the wrong people. I've seen memos go to entire departments when they only affected one team. When someone's inbox fills up with irrelevant memos, they stop reading all memos. This isn't theoretical—I watched a company where internal communication effectiveness dropped measurably after someone sent a six-page memo about cafeteria hours to four hundred employees. The actual important memos got filtered as noise.
The Components That Actually Matter
Most memo guides list seven or eight components. Half of them are ceremonial. The parts that matter are the subject line and the opening paragraph. Everything after that is support. The subject line should tell someone everything they need to know without opening the document. If your subject line requires reading the memo to understand, rewrite it. This sounds simple. It's surprisingly hard to do consistently, especially when the topic is complex or affects multiple departments. The opening paragraph should state the purpose immediately. One sentence if possible. If you're proposing a change, say what the change is. If you're informing people about a decision, say what the decision was. Don't build up to it. The person reading this already knows they're looking at a memo—they don't need context for why they're reading context.
Body paragraphs come after. Group related information. Use short sections if there are multiple topics. A memo covering both the new software rollout and the updated PTO policy should probably be two separate memos. Mixing unrelated topics is the fastest way to make sure nobody reads either of them thoroughly. Close with action items if there are any. What does the reader need to do? By when? If there's nothing to do—just information to absorb—that's fine too. Say so. "No action required" saves people from wondering whether they missed something.
A Practical Example
Here's what a functional memo looks like in practice: TO: All Marketing Staff
FROM: J. Torres, Department Head
DATE: October 12, 2024
SUBJECT: Q4 Budget Review Schedule Changes The quarterly budget review meeting has moved from the first Tuesday of the quarter to the third Wednesday. The next review is November 20th at 2 PM in Conference Room B. Please submit your department spending reports to finance by November 13th.
Questions about the new timeline can be directed to the finance team at extension 4420. That's it. Nine sentences. A person can read it in fifteen seconds and know exactly what changed and what they need to do about it.
Common Mistakes to Avoid
The biggest mistake is treating memos like essays. Essays build arguments. Memos deliver information. If you find yourself writing a thesis statement, you're doing it wrong. Another mistake is not updating memos when circumstances change. I encountered this with a memo about remote work eligibility that was never revised after the policy expanded. Three years later, new hires were still being told they couldn't work remotely because "the memo says so." The original memo was technically still in circulation. Don't let outdated memos become operational obstacles. Mark them superseded when you issue corrections. Length is also a factor most people underestimate. A memo longer than two pages usually means the writer hasn't finished thinking about the topic. If you can't explain something in two pages, you don't understand it well enough to communicate it yet. Go back to the drawing board. This rule has exceptions—complex technical memos, merger announcements, anything involving significant data—but even those should be digestible.
Where Memoranda Fall Short
Memos aren't universal solutions. They don't work well for sensitive discussions. HR issues, performance problems, conflicts between individuals—those should happen in person, not in writing. A memo about a personal matter reads as cold and impersonal, which makes it worse than useless. They also don't work for situations requiring dialogue. If you need feedback, buy-in, or collaborative problem-solving, a memo is the wrong tool. It's a one-way communication format by design. Send a memo when you need to inform. Use a different channel when you need to discuss. Finally, memos age poorly in digital environments. The physical memo on your desk had presence. A PDF memo in a shared drive is easy to lose, easy to misfile, easy to forget exists. If you're working in a digital-only environment, consider whether a properly tagged document in your knowledge base serves the same purpose better than a traditional memo format.
