Writing a Business Memo That People Actually Read

Most business memos are garbage. They're long, vague, and structured like the writer is trying to prove they deserve a salary. I've seen people send twelve-paragraph documents about a new lunch schedule. Nobody reads past the first line. The trick is treating a memo like a tool, not a novel.

For A Business Memo, Lead With the Decision

When I was managing a logistics team, we had a situation where three departments kept ordering supplies through different channels. The procurement memo I wrote was four paragraphs. The first line was "We are consolidating all supply orders through the new portal by Monday." That was it. The rest was a table showing what changed, a link to the portal, and one sentence about exceptions. It took about ten minutes to write and five seconds for someone to understand what was needed. The opposite also happened. I once received a memo about a policy update that started with six paragraphs of background history before mentioning that the deadline had moved up by two weeks. The subject line just said "Update." By the time the actual news appeared, the reader had already decided to skip it. The structure that actually works is inverted. Start with what needs to happen, then explain why, then list any details. If you can't state the core action in one sentence on the first line, you don't understand the memo yourself yet. Subject lines matter more than most people admit. A subject like "Quarterly Budget Review" tells someone nothing. "Action Required: Submit Q3 Budget by Friday" tells them everything. People scan inboxes the way they scan everything else. Make the scan profitable. I learned this the hard way during a reorganization. I drafted a memo about reporting structure changes and spent twenty minutes on the opening paragraph about how the company was evolving. My manager read the first sentence, looked at me, and asked if there was a point. There wasn't, not really. We rewrote it together in three minutes. The new version started with "Effective next month, the marketing team reports to operations instead of sales." That was the memo. Everything else was secondary.

The Common Mistakes

The biggest problem I see is people writing memos to cover their own ass. They include too much context because they're afraid someone will ask why a decision was made. But the person reading the memo already knows why. They just need to know what changes for them. Every extra sentence is a chance for the message to get lost. Another mistake is the passive voice trap. "It has been decided that..." means nothing. "Management has decided..." or better yet, just name the person or department making the call. Accountability is part of clarity. If you're the one who made the decision, put your name on it. I also see people use memos for things that should be conversations. If a memo requires back-and-forth discussion, it's the wrong format. A memo announces or directs. If you need input, send an email or set up a meeting. Memos are one-way by design. Trying to make them collaborative just creates confusion about whether you're asking for feedback or stating a decision.

Advanced: When Memos Fail

There are scenarios where a memo simply doesn't work. If you're communicating something that requires emotional intelligence or relationship management, a written document will feel cold or aggressive. Layoffs, performance issues, and team conflicts should never be handled primarily through memos. The format strips away tone and nuance in ways that hurt more than help. Another limitation is audience size. If you're sending a memo to more than fifty people, engagement drops significantly. That's not a flaw in memo writing, it's a flaw in communication theory. Large groups need different formats. Use a memo for targeted distribution, not company-wide announcements. For those, a brief email or a live meeting works better. I ran into this when we tried rolling out a new compliance requirement across a global organization. The memo was thorough, technically accurate, and completely ignored by half the offices. What actually moved the needle was a series of short video walkthroughs and a live Q&A session. The memo still existed as a reference document, but it was never the primary communication tool. That's a lesson I remember now. Keep it short enough that someone could read it while walking to their desk. If it takes more than two minutes, you've included something you didn't need to. The format itself is also outdated in some contexts. Younger employees, particularly those who joined during or after the remote work shift, often expect information through Slack channels or shared documents rather than formal memos. That doesn't mean the memo is dead, but it does mean the delivery method matters. Posting a memo as a PDF attachment in an email has lower readership rates than putting the same content in a shared workspace where people already check for updates. What remains constant is the principle. Whatever the medium, the memo should answer three questions immediately: what is changing, what do I need to do about it, and when does it happen. Everything else is support material. Write for those three questions first. Add the rest only if someone genuinely needs it.