The One-Page Memo Template That Makes You Look Senior

The first time I sent my manager a five-page doc and got back “lgtm,” I thought he hadn’t read it. He had. He’d read enough to know I hadn’t told him what to do.

That’s what “looks good to me” usually means. Not “I read this carefully and agree.” It means “I don’t see anything I have to push back on, and I’m not going to do your job for you and find the question buried on page three.”

If you’ve gotten “lgtm” with no comments, no follow-ups, no decision, your memo didn’t fail to convince anyone. It just took up space.

The misunderstanding behind every long memo

First-year professionals treat the memo as a record of their thinking. The doc proves they did the work. Every consideration, every option, every footnote, in the body, in order, so the reader can see the path.

Seniors treat the memo as a forcing function for the reader. The doc isn’t proof of effort. It’s a request for a specific decision, written so the reader can say yes or no in 90 seconds.

Same Google Doc. Completely different job.

You can tell which version someone wrote in the first line. “Here’s an update on the Q2 forecast project, including methodology, key assumptions, and proposed next steps” is a record. “Recommend: ship the Q2 forecast on the updated assumptions; risk is one missed scenario, mitigation below” is a decision request.

The first one earns “lgtm.” The second one earns either a yes or a sharp question. Either is better than silence.

A scar from earlier in my career

Early in my career I sat through a performance review at a Fortune 1 retailer where I was, on paper, having a great year. I’d run stakeholder interviews. I’d synthesized exec input into a strategy framing. I’d built decks. I’d built docs.

The review came back average.

I asked why. The answer was something like: “You did a lot of thinking. Nothing shipped. No metric moved. No user touched the thing.”

It stung because it was right. The artifacts I was proudest of were the artifacts that documented effort, not the ones that drove a decision. The deck looked like work. It wasn’t the work.

I think about that review every time I’m tempted to add another section to a memo. A four-page doc lets you hide inside your own thinking. A one-pager forces you to convert effort into a question. Questions are what get answered.

The template

This is the version I use now. Steal it. Adjust the headers to match your company’s voice if needed, but keep the order.

TITLE: [Decision needed in 8 words or less]

To:        [Decider's name]
CC:        [Anyone whose objection could block this]
From:      [You]
Date:      [Today]
Decision needed by: [Specific date — not "ASAP"]

RECOMMENDATION
[One sentence. What you want them to say yes to.]

WHY
- [Reason 1 — the strongest one]
- [Reason 2]
- [Reason 3 — stop here]

ALTERNATIVES CONSIDERED
- [Option B]: [why not, one line]
- [Option C]: [why not, one line]

KEY RISK + MITIGATION
[The biggest thing that could go wrong, and what you'll do about it.]

WHAT I NEED FROM YOU
[Specific action: approve, reject, ask one question, forward to X.
 Not "let me know your thoughts."]

APPENDIX
[Everything else. Methodology, raw numbers, alternate scenarios,
 the spreadsheet, the Figma link, the Slack screenshots, the
 background reading. The body of the doc points here. The reader
 only opens it if they want to.]

That’s the whole thing. Two-thirds of a page if you’re verbose. Half a page if you’re disciplined.

What’s missing on purpose: a “Background” section. An “Objectives” section. A “Next Steps” section that restates the recommendation. None of those help the decider decide. They help the writer feel thorough.

The pre-read script

The template only works if the reader sees it before the meeting. A memo handed across the table at the start of a meeting is a deck in disguise. You’ll end up walking them through it instead of letting them read it.

Send this 24 hours before, or at minimum the night before:

Subject: Pre-read for tomorrow — [decision needed in 8 words]

Hi [Name],

For our 2pm tomorrow, here's the one-pager on
[topic]: [link].

The ask is on line 1. If you can read it before we meet,
we can spend the meeting on the risk section instead of
the background. If something on the page is a non-starter
for you, a quick reply is fine and I'll regroup.

Thanks,
[You]

That message does three things. It tells the reader where the ask lives. It signals you respect the way they actually work — skim on a phone, mark up in comments. And it gives them an explicit out. They can kill it in writing without a meeting, which is the kindest outcome for everyone when the answer is no.

Yes, sending a pre-read 24 hours early feels like LinkedIn-influencer behavior the first time you do it. Send it anyway. The first time a director replies “looks fine, we can skip the meeting” you’ll never go back.

Why one page is a thinking constraint, not a writing constraint

People hear “one page” and think it’s a stylistic preference, like double-spacing or sentence case. It isn’t. The page limit is the discipline.

If your memo runs to two pages, it’s not because the topic is too big. It’s because you haven’t decided which of your three recommendations is actually the recommendation. You’re hedging by including all of them. The reader can tell.

The senior move is the subtractive pass. Write the four-page version first if you need to. Then cut. Cut the “Background” section. Cut the recommendations that aren’t the recommendation. Cut the section where you list the things the reader already knows.

If after cutting you still can’t fit on a page, you don’t understand the problem yet. That’s useful information. Stop writing and go think for an hour.

What goes in the appendix

Anything you’d defend in a meeting goes in the appendix. The methodology. The raw spreadsheet. The full list of alternatives you considered before narrowing to two. The screenshots, the customer quotes, the legal review.

The page-one line that points to it (“see appendix for methodology”) is the line that signals seniority. It says: I did the work. I’m not going to make you read all of it. Ask if you want to dig in.

The fix isn’t to pre-empt every question on the front page. The fix is to know the appendix cold so you can flip to it in real time.

When this doesn’t fit

The template is built for a reversible-but-expensive decision with two or more stakeholders. That’s most of what you’ll write memos for in the first five years.

Two exceptions. In a Slack-first startup of under thirty people, a one-pager reads as overkill for routine asks — use it when the decision is hard to reverse or when more than two people have to agree. In regulated industries (healthcare, finance, legal), the memo lives on top of whatever compliance document policy already requires. It’s a cover sheet, not a replacement.

---

The manager who graded me average wasn’t being harsh. He was being literal. The doc looked like work. It wasn’t asking him for anything. The one-pager fixes the same bug — it converts effort into a question. Questions are what get answered.

---