One-Pager Writing
Parent: Writing and Documentation · Published reference · snapshot 2026-09-08 · skill executive-comms/references/one-pager-writing.md
↓ Facts as markdownall context files
One-pagers are the highest-impact document format in business: a single page that earns a meeting, secures a budget, aligns a partner, or briefs an exec in under three minutes.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Overview
- One-pagers are the highest-impact document format in business: a single page that earns a meeting, secures a budget, aligns a partner, or briefs an exec in under three minutes. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#overview]
1. The no-second-page discipline
- A one-pager fits on one page. The moment you flow to page 2, the document is now a half-finished two-pager. Everything else in this skill exists to enforce this rule. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#1-the-no-second-page-discipline]
- Cut by 30-50% from your first draft. Always. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#1-the-no-second-page-discipline]
- Drop full sentences for fragments where fragments work. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#1-the-no-second-page-discipline]
- Move evidence to an appendix link, not a footer. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#1-the-no-second-page-discipline]
- If three things won't fit, you have three things - not one. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#1-the-no-second-page-discipline]
2. Above-the-fold visual hierarchy
- The reader scans before they read. What lives above the fold: [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#2-above-the-fold-visual-hierarchy]
- Headline - the one-line value prop, written in the reader's language. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#2-above-the-fold-visual-hierarchy]
- Subhead or value-prop sentence - what changes for the reader if they say yes. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#2-above-the-fold-visual-hierarchy]
- The "if you only read one line" sentence - bolded, set off visually. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#2-above-the-fold-visual-hierarchy]
- A visual anchor - chart, screenshot, diagram, photo, or large pull-quote. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#2-above-the-fold-visual-hierarchy]
3. The "if you only read one line" pattern
- Every one-pager has one sentence the reader must take away. Find it. Bold it. Place it above the fold. Repeat it in different words at the end. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#3-the-if-you-only-read-one-line-pattern]
5. The Amazon 1-pager and the PR/FAQ lineage
- The Amazon 1-pager / PR-style opener: [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#5-the-amazon-1-pager-and-the-prfaq-lineage]
- Heading: the product or initiative name. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#5-the-amazon-1-pager-and-the-prfaq-lineage]
- Subheading: who it's for, in their language. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#5-the-amazon-1-pager-and-the-prfaq-lineage]
- Summary paragraph (3-4 sentences): what it does, who benefits, why now. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#5-the-amazon-1-pager-and-the-prfaq-lineage]
- Problem paragraph: the customer's status quo. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#5-the-amazon-1-pager-and-the-prfaq-lineage]
- Solution paragraph: how this changes the status quo. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#5-the-amazon-1-pager-and-the-prfaq-lineage]
- Quote (optional): an executive or customer making the value claim concrete. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#5-the-amazon-1-pager-and-the-prfaq-lineage]
- Call to action: what the reader does next. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#5-the-amazon-1-pager-and-the-prfaq-lineage]
- Two non-negotiables: written as full sentences; written as if the product already launched. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#5-the-amazon-1-pager-and-the-prfaq-lineage]
6. Bullets vs paragraphs
- Use paragraphs when: The reader needs to see how ideas connect; describing a customer's strategic status quo; Amazon 1-pager opener. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#6-bullets-vs-paragraphs]
- Use bullets when: Listing 3-7 parallel items; scannable facts; the reader is an exec who triages. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#6-bullets-vs-paragraphs]
- Heuristic: paragraphs for the upper half (the narrative), bullets for the lower half (the facts and the ask). [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#6-bullets-vs-paragraphs]
7. Section budget for a single page
- A single page gives you roughly 550-650 words of usable real estate: [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#7-section-budget-for-a-single-page]
- Headline + value prop: 20-30 words [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#7-section-budget-for-a-single-page]
- Above-the-fold callout: 15-25 words [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#7-section-budget-for-a-single-page]
- Body - problem / context: 80-120 words [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#7-section-budget-for-a-single-page]
- Body - solution / approach: 100-150 words [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#7-section-budget-for-a-single-page]
- Body - outcomes / proof: 80-120 words [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#7-section-budget-for-a-single-page]
- The ask: 30-50 words [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#7-section-budget-for-a-single-page]
9. The five canonical species
- Account brief - for an internal audience to brief before a customer meeting. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#9-the-five-canonical-species]
- Project pitch - to get funding or headcount. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#9-the-five-canonical-species]
- Product one-pager - for stakeholders evaluating a product. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#9-the-five-canonical-species]
- Sales-enablement one-pager - for sellers to use in front of buyers. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#9-the-five-canonical-species]
- Amazon 1-pager / PR-FAQ opener - for internal alignment on a new product. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#9-the-five-canonical-species]
10. The ask, the owner, the next step
- Every one-pager ends with: [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#10-the-ask-the-owner-the-next-step]
- The ask - what specific thing do you need from the reader. A verb with an object. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#10-the-ask-the-owner-the-next-step]
- The owner - who runs this, with name, role, contact. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#10-the-ask-the-owner-the-next-step]
- The next step - when, where, what format. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#10-the-ask-the-owner-the-next-step]
- These three sentences are the entire reason the one-pager exists. Never cut these. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#10-the-ask-the-owner-the-next-step]
Anti-Patterns
- The 1.5-pager - runs onto a second page by half a paragraph. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#anti-patterns]
- The mystery headline - "Project Phoenix: A New Approach." No value visible. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#anti-patterns]
- The ask buried at line 47 - the ask should be visible above the fold. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#anti-patterns]
- The "alignment" ask - "We're seeking alignment on..." No verb, no object. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#anti-patterns]
- The missing owner line - the page is anonymous. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#anti-patterns]
- The four-CTA ending - list more than two CTAs and readers pick zero. [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#anti-patterns]
References
- Working Backwards - Amazon's Six-Page Memo culture [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#references]
- How to Write a Product One-Pager - ProductPlan [archived source: https://llms-explorer.com/sources/mdb-context-hub/one-pager-writing/#references]
Where this helps
- Requesting budget or headcount from an exec who has three minutes and needs the ask, owner, and next step visible above the fold rather than buried in narrative. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Briefing an internal team before a customer meeting, where a scannable account brief beats a long email thread nobody actually reads in full. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Aligning a cross-functional team on a not-yet-built product using the Amazon PR/FAQ-style opener, written as if the product already shipped, to surface disagreement before real work starts. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Handing sellers a single artifact they can use in front of a buyer, where bullets for scannable facts and paragraphs for the strategic narrative need to coexist on one page. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
How to apply this
- Draft the one-pager long first, then apply the no-second-page discipline by cutting 30-50% and moving evidence to an appendix link rather than trying to shrink the font. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Identify the single "if you only read one line" sentence before writing anything else, bold it, and check it appears both above the fold and again at the end. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Budget the page by section (roughly 550-650 usable words) before drafting, so the ask isn't the section that gets cut when the page runs long. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Pick the right one of the five canonical species before drafting, since each implies a different structure and audience. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Common mistakes
- Writing "We're seeking alignment on..." as the ask — it has no verb and no object, so the reader can't act on it. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Burying the ask around line 47 instead of making it visible above the fold, where a triaging exec reader will actually see it. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Shipping a "1.5-pager" that runs onto a second page by half a paragraph — the moment it flows to page two, it's a half-finished two-pager. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Ending with four calls to action instead of one or two — readers presented with more than two CTAs tend to pick none. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Limitations
- The roughly 550-650-word budget assumes standard margins and body-text size — dense visuals like a large chart or the Amazon opener's optional quote eat into that budget and force sharper cuts elsewhere. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- The Amazon PR/FAQ opener is written as if the product already launched, which only works when the audience already understands it's a forward-looking exercise — used on an unfamiliar audience, it can read as a factual claim about something that doesn't exist yet. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- A one-pager compresses by design, which means it structurally cannot carry the caveats and supporting data a skeptical technical reviewer might need — that evidence has to live in a linked appendix, not on the page itself. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- The bullets-for-facts, paragraphs-for-narrative heuristic assumes a reader who scans top to bottom — a reader who jumps straight to the ask may miss context the ask depends on. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Children
- No-Second-Page Discipline (frontier)
- Above-the-Fold Visual Hierarchy (frontier)
- Headline + Value-Prop Pattern (frontier)
- If You Only Read One Line (frontier)
- Amazon 1-Pager and PR-FAQ (frontier)
- Working Backwards Lineage (frontier)
- Bullets vs Paragraphs (frontier)
- Section Budget for One Page (frontier)
- Design vs Writing Collaboration (frontier)
- Account Brief Species (frontier)
- Project Pitch Species (frontier)
- Sales-Enablement One-Pager Species (frontier)
Frontier under this node: Above-the-Fold Visual Hierarchy, Account Brief Species, Amazon 1-Pager and PR-FAQ, Bullets vs Paragraphs, Design vs Writing Collaboration, Headline + Value-Prop Pattern, If You Only Read One Line, No-Second-Page Discipline, Project Pitch Species, Sales-Enablement One-Pager Species, Section Budget for One Page, Working Backwards Lineage