How To Write A Memo

Why most memos get ignored

I spent seven years writing internal documents for logistics companies and consulting firms. The problem was never structure. It was readability. People skim these things at 200 words per minute while checking their phones. If your memo doesn't land its main point in the first three lines, it's dead on arrival regardless of how thorough your supporting analysis is. A memo is simply a short document used within organizations to communicate information, decisions, or requests. Standard memo format includes a header with date, to, from, and subject lines, followed by a body organized into sections. That's the textbook definition. The actual practice of writing one that people finish reading is something entirely different.

How To Write A Memo That Gets Read

Start with the bottom line. Put your conclusion or primary recommendation in the first paragraph, not the last. I learned this after spending three weeks on a 12-page memo about warehouse staffing ratios that my VP forwarded back with a single note: "Just tell me what you want." That memo could have been four pages if I'd led with the recommendation instead of building up to it through methodology and data. The header is straightforward. Date at the top, then TO with the full names and titles of recipients, FROM with your name and title, and SUBJECT that actually describes the content rather than being vague. I've seen subjects like "Update" and "Follow-up" so often it's almost comical. A subject line should be specific enough that someone scanning an inbox knows exactly what they're opening. "Proposed Q3 Warehouse Staffing Adjustment – Two Positions Realigned to Distribution Bay 4" tells you everything you need to know before reading another word. After the header comes the opening paragraph. This is where most people go wrong. They write a sentence or two of filler about the background before getting to the point. Don't do that. Open with the purpose of the memo in one or two sentences max. "This memo recommends eliminating two administrative positions in Building C and reallocating those funds toward overtime coverage at Distribution Bay 4. The change would take effect November 1 if approved by October 15."

Then provide supporting context. This is the section where you lay out the facts, the data, the reasoning. Keep it organized with clear subheadings if there are multiple topics. Numbered lists work well for sequential items. Bulleted lists work better for related points that don't have a particular order. Here's something counter-intuitive that I've found through years of this work: the length of a memo has almost nothing to do with its effectiveness. I've read five-page memos that could have been one page and I've read one-page memos that contained more useful information than entire reports. Brevity isn't just a virtue in memo writing. It's the whole point. People don't read long internal documents. They glance at them, absorb what they can, and move on. If your memo is longer than two pages, you should be questioning whether it needs to exist at all or whether you're burying your actual point under irrelevant detail. The closing paragraph should restate the action you want taken and by when. If there are deadlines, state them clearly. If you need a response, specify what kind of response and on what timeline. "Please review and provide feedback by end of day Friday, September 20. Approval from department heads will be sufficient to proceed."

A specific problem I ran into

Once I wrote a memo recommending a software migration for our inventory management system. I included extensive technical specifications, vendor comparisons, cost projections, and implementation timelines. I got it down to five pages which I considered concise. My director's response was "I still don't understand what you're asking me to approve." I had made the mistake of presenting all the analysis without a clear decision point. The memo wasn't actually asking for approval of anything specific. It was just sharing information, which is almost never effective in an organizational setting. My workaround was to rewrite it with a single explicit approval request at the top: "I am requesting approval to proceed with the NetSuite migration as outlined in this document, with a budget ceiling of $47,000 for the first phase." Everything else became supporting documentation. The director approved it the same afternoon. Sometimes the entire structure of a memo needs to be built around the decision you want the reader to make rather than the information you want them to have.

Common mistakes I see repeatedly

The biggest mistake is treating a memo like an academic paper where you build an argument and reveal the conclusion at the end. Memos are not arguments. They are requests for attention and action in environments where both are scarce resources. Lead with what you need. Another common error is including information the reader doesn't need. If someone doesn't need to know the historical context of why the previous vendor was chosen in 2019, don't include it. Get to the current situation and what should happen next. The less noise, the higher the signal. Tone is also worth paying attention to. Memos can easily read as passive-aggressive depending on phrasing. "It has come to my attention that the policy has not been followed" reads very differently from "We've had three instances of the policy not being followed this month. I'd like to address this." The second version states the problem and signals intent to solve it without assigning blame in a way that makes people defensive.

When memos don't work

They don't work well for highly complex technical topics that require interactive discussion. If your message requires back-and-forth clarification, a memo is the wrong format. Use a meeting invitation or a shared document with comment threads instead. Memos also fail when the audience has widely varying levels of context. If some readers need foundational background while others need granular detail, you're either writing two documents or neither group gets what they need. The format also struggles with emotionally charged messages. A memo about layoffs, policy violations, or performance issues will almost always land poorly in written form. Those conversations belong in person or at minimum over video call. A memo can communicate the decision afterward, but it shouldn't be the vehicle for delivering difficult news. I usually keep mine under 600 words. Anything beyond that I split into two separate memos rather than one long document. The subject line determines who needs to read it and whether it warrants their time. A clear subject line reduces unnecessary reads across the organization because people can filter what they engage with based on relevance to their actual responsibilities.