---
name: memos-one-pagers
description: "Write one-page memos and one-pagers for decisions, proposals, status updates, ideas, incidents and projects: the bottom line in two sentences, brief context, options with benefits, costs and risks, a recommendation, a specific ask with a date and templates that fit on one page. Use whenever someone needs a memo, one-pager, decision document, project one-pager, incident summary or a short pre-read for leaders, or wants to cut a long document down to one page."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/productivity/workplace-writing/memos-one-pagers/
  category: productivity
  subcategory: workplace-writing
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-13"
---

# Memos and One-Pagers

Busy readers decide in the first paragraph whether a document matters to them. A one-page memo forces the writer to know exactly what they are asking and why, and gives decision makers everything they need in a few minutes. Long slide decks and rambling documents often hide weak thinking; a good one-pager exposes it, which is why many organisations use short written memos before important discussions.

This skill writes one-page memos and one-pagers for decisions, proposals, updates and ideas: a clear title, the bottom line first, context in a few sentences, the options or plan, risks and costs, the ask and next steps, in plain language that fits on one page.

## Operating principles
1. **One page means one page.** If it does not fit, the thinking or the scope needs work.
2. **Bottom line first.** The ask or conclusion goes in the first two sentences.
3. **Only what the reader needs to act.** Background in one paragraph, detail in links.
4. **Show the trade-offs.** Options, costs and risks make the memo trustworthy.
5. **End with the ask.** Who needs to do what by when.

## Memo types
| Type | Purpose | Lead with |
|---|---|---|
| Decision memo | Get a decision | The decision needed and recommendation |
| Proposal one-pager | Get support for an idea | The problem and the proposed solution |
| Status memo | Update stakeholders | What changed and what is needed from them |
| Idea one-pager | Test interest in an idea | The opportunity and the smallest next step |
| Incident summary | Explain what happened | Impact, cause and fix |
| Project one-pager | Align a team | Goal, scope, owner, dates, success measures |

## When to use, and when not to
Use it for decisions, pitching an idea internally, updating leaders, explaining an incident, starting a project or preparing for a meeting where people need a pre-read.

Don't use it for full reports with detailed analysis (`reports`) or formal proposals to clients (`proposals`).

## Inputs
- The purpose and the reader.
- The ask or main point.
- Facts, data and options.
- Constraints: cost, time, risk, approvals.
- Any required template.

## Workflow

### Step 1. Write the bottom line
Two sentences: what you want and why. Test it on its own.

### Step 2. Choose the type and structure
From the table above.

### Step 3. Draft each section briefly
Context (3 to 4 sentences), options or plan, costs and risks, the ask and next steps.

### Step 4. Cut to one page
Remove history, repetition, hedging and anything that does not change the decision. Move detail to linked appendices.

### Step 5. Format for scanning
Short headings, bullets for lists, a small table for options, bold only for the ask.

### Step 6. Test
Ask a fresh reader for the ask in one sentence and the main risk; fix anything they miss.

## Decision memo template
```
Title: <decision in a few words>
To: <decider> | From: <author> | Date: <date>

Bottom line: <what we recommend and why, in two sentences>

Context: <3 to 4 sentences: the problem, why now>

Options
| Option | Benefit | Cost | Risk |
| A | ... | ... | ... |
| B | ... | ... | ... |
| Do nothing | ... | ... | ... |

Recommendation: <option> because <reason>

Risks and mitigations: <2 to 3 bullets>

Ask: <decision needed by date> | Next steps if approved: <owner, date>
```

## Project one-pager template
```
Project: <name> | Owner: <name> | Dates: <start to end>
Goal: <one sentence>
Why now: <2 sentences>
Scope: in <...> | out <...>
Success measures: <2 to 3 metrics with targets>
Milestones: <3 to 5 with dates>
Team and roles: <names>
Risks: <top 3>
Needs: <budget, people, decisions>
```

## Output format
```
1. Bottom line (two sentences)
2. One-page memo using the right template
3. Appendix links or notes on what was moved out
4. Fresh-reader check: the ask and main risk as a reader understood them
```

## Incident summary template
```
Incident: <short name> | Date: <date> | Severity: <level>
Impact: <who was affected, how, for how long>
Cause: <what happened, in plain words>
Fix: <what was done to restore service>
Prevention: <changes, owners, dates>
What we need: <decisions or resources>
```
Keep blame out; describe systems and decisions, not individuals.

## Writing the bottom line
| Weak | Strong |
|---|---|
| This memo discusses support staffing. | Approve one extra support agent from January to bring response times under four hours. |
| We've been looking at vendors. | Choose Vendor B for payroll: 20% cheaper and live in six weeks. |
| Update on the launch. | Launch moves to 4 November because of payment testing; no action needed from you. |
A strong bottom line names the action, the reason and, where relevant, the cost or date.

## Fitting on one page
- Use short sentences and bullets rather than paragraphs where possible.
- Replace background with one sentence and a link.
- Show options in a table instead of prose.
- Remove qualifiers such as "it could be argued that".
- If it still does not fit, the scope is too wide: split it.

## Pre-reads for meetings
Send the memo at least 24 hours before the meeting, or give attendees the first ten minutes to read it silently. Ask for comments in the document beforehand so the meeting can focus on real disagreements and the decision itself.

## Using an AI agent
The agent can draft the bottom line from the user's notes, build the options table from data, cut a long draft to one page, run a fresh-reader check and produce a three-line summary for very senior readers. The user checks figures and approves the recommendation.

## Tone
Keep the tone factual and confident without overselling. State uncertainty plainly, such as "estimates may vary by 10%", rather than hiding it. Decision makers trust memos that show the downside as clearly as the upside, and they approve faster when nothing seems to be missing.

Read the final memo aloud once before sending.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Too much content for one page | Split into a one-pager plus appendix; or narrow the scope |
| No clear recommendation yet | Write an options memo asking for direction |
| Sensitive topic | Facts only; limited distribution; review before sending |
| Senior reader with little time | Three-line summary at the top |
| Required company template | Fill it; keep the bottom line first |
| Data uncertain | State the uncertainty and what would resolve it |

## Handoffs to related skills
- Staged writing: `writing-process`
- Longer analysis: `reports`
- Client-facing proposals: `proposals`
- Summaries of long documents: `executive-summaries`
- Running the decision meeting: the Meetings and Calendar `decision-meetings` skill

## Worked example
A team lead wanted budget for a second support agent. Her first draft was four pages of ticket history. The one-pager opened with "Approve one additional support agent from January (£32,000 a year) to bring response times back under four hours; current staffing misses the target on 40% of days." Context took three sentences, an options table compared hiring, outsourcing evening cover and doing nothing, risks covered training time, and the ask set a decision date. The director approved it after a ten-minute read.

## Common mistakes
- Background before the ask.
- More than one page.
- Only one option presented.
- Vague asks ("thoughts welcome").
- Jargon the reader does not share.

## Self-check before you answer
- Is the bottom line in the first two sentences?
- Does it fit on one page?
- Are options, costs and risks shown?
- Is the ask specific, with a date?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/productivity/workplace-writing/memos-one-pagers/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.