apply-narrative-memo-discipline

name	apply-narrative-memo-discipline
description	Use when a significant decision is being made based on a slide presentation — require a structured, written narrative document (full sentences and paragraphs, not bullet points) instead, and have the room read it silently before any discussion, because slide formats systematically let weak analysis and unsupported claims pass unchallenged in a way that full-sentence prose does not.
source	Edward Tufte, "The Cognitive Style of PowerPoint: Pitching Out Corrupts Within" (2003) — including its analysis of the Columbia Accident Investigation Board's finding that a PowerPoint slide obscured critical risk data before the 2003 Space Shuttle Columbia disaster; Jeff Bezos, Amazon 2017 Shareholder Letter — describes Amazon's six-page narrative memo and "study hall" silent-reading practice; Brad Stone, "The Everything Store: Jeff Bezos and the Age of Amazon" (2013)
tags	["decision-making","meetings","governance","communication","organizational-culture"]
related	["apply-merit-selection","write-prfaq","apply-halo-effect-mitigation"]

Apply Narrative Memo Discipline

Require a structured, full-sentence written narrative for any significant decision instead of a slide presentation, and have the room read it silently before discussion begins — because bullet-point slide formats systematically let weak analysis, unsupported claims, and missing logical connections pass unchallenged in a way that full-sentence prose does not.

Why This Is Best Practice

Why best: A bullet-point slide format does not require the author to state the actual logical relationship between claims — bullets can be juxtaposed on a slide without ever specifying whether one causes another, contradicts another, or is merely adjacent to it, and a fluent presenter can paper over that missing logic with delivery. A full-sentence narrative document cannot hide this gap: a claim has to be stated as a complete sentence with an explicit logical connector to the next one, which forces the author to either supply the actual reasoning or expose its absence on the page, where a reader can catch it before a decision is made rather than after.

Tufte, "The Cognitive Style of PowerPoint" (2003): Tufte's analysis specifically examined a PowerPoint slide used in NASA communications during the 2003 Space Shuttle Columbia mission, which presented data about a foam-strike risk to the shuttle's wing in a nested hierarchy of terse bullet points. The Columbia Accident Investigation Board's own subsequent report concluded that the slide's format compressed and obscured the severity of the underlying engineering data to the point that key decision-makers did not grasp the actual risk being described — a documented, high-stakes, real-world case in which the compression inherent to bullet-point slide format contributed to a fatal misjudgment, not merely a stylistic complaint about slides being unaesthetic.

Jeff Bezos, Amazon 2017 Shareholder Letter: Bezos describes Amazon's standard practice for important decision-making meetings: instead of a slide presentation, the meeting's presenter writes a structured, full-sentence narrative memo (Amazon's convention caps it at six pages), and the meeting begins with everyone silently reading the memo in the room ("study hall") before any discussion starts. Bezos explains the rationale directly: a good memo forces better thought and better understanding of what's actually important versus what's not, in a way that a slide presentation's structure inherently does not — because the act of writing complete sentences and paragraphs requires the author to actually work out the argument, not merely gesture at it.

Adopted by: Amazon's narrative-memo and silent-reading practice, documented in Bezos's shareholder letters and in Brad Stone's "The Everything Store," has been in standing use as Amazon's default format for significant internal decision meetings since the mid-2000s and has been subsequently adopted or emulated by numerous other technology companies and venture-backed startups as an explicit alternative to slide-based decision meetings. Impact: The Columbia Accident Investigation Board's finding that a specific PowerPoint slide's bullet-point compression obscured critical risk data is documented, publicly available evidence of the format's failure mode in a genuinely high-stakes context; Amazon's sustained, long-running use of narrative memos as its standard decision-meeting format, described directly by Bezos as producing better collective understanding than slide presentations, constitutes a large-scale, long-duration natural experiment in the alternative this skill recommends.

Steps

1. Require a full-sentence, structured written narrative for any decision meeting of real consequence, rather than a slide deck. The document should state the problem, the relevant data, the options considered, and the recommendation in complete sentences and paragraphs — not phrases or bullet fragments.

2. Set an explicit length constraint on the memo. A fixed page limit (Amazon's convention is six pages) forces the author to prioritize and compress their actual argument rather than padding it, while still requiring the argument to be stated as connected prose rather than as isolated bullet fragments.

3. Have the room read the memo silently at the start of the meeting, before any discussion. This ensures everyone has actually engaged with the full argument on their own terms, rather than the loudest or most senior voice's initial reaction to a slide anchoring the group's discussion before others have processed the material themselves (see apply-anchoring-defense and apply-primacy-effect-mitigation for the related biases this also helps counter).

4. During discussion, hold the author accountable to the specific logical connections stated in the memo, not to their live verbal delivery. If a claim in the memo lacks a stated justification or a stated logical connector to the prior claim, treat that gap as a finding to be addressed, rather than allowing the author to verbally supply a justification in the moment that isn't actually written down and vetted.

5. Do not allow a slide deck to substitute for the memo, even as a supplementary visual aid, for the core argument itself. Charts and diagrams that support specific data points can accompany a narrative memo, but the core claims, tradeoffs, and recommendation must be carried by the prose itself, not by a slide's visual layout.

6. Apply this selectively to decisions of real consequence, not to every routine update or status check. The discipline has a real cost in preparation time; reserve it for decisions where the cost of an undetected logical gap is high enough to justify that cost.

Rules

• Require the core argument, tradeoffs, and recommendation to be carried by full-sentence prose, not by a slide's bullet points or visual layout — supporting charts may accompany the memo but cannot substitute for it.
• Set an explicit page limit on the memo to force prioritization without permitting the argument to remain unstated or merely implied.
• Read the memo silently as a group at the start of the meeting before any discussion begins, rather than allowing a live presentation to shape the room's first reaction to the material.
• Hold the written document, not the presenter's live delivery, accountable for the actual logical connections in the argument.

Examples

Product decision: A team preparing to recommend a significant product direction change writes a six-page narrative memo stating the problem, the customer data behind it, the alternatives considered and why they were rejected, and the specific recommendation — rather than a twenty-slide deck. The team reads it silently for fifteen minutes at the start of the meeting; several participants flag that the memo's argument for rejecting one alternative isn't actually supported by the stated data, a gap that a slide-based presentation of the same material would likely have let pass unchallenged behind confident verbal delivery.

Post-incident review: An organization examining a past decision that led to a costly outcome finds, on reviewing the original decision materials, that the case had been made via a slide deck whose bullet points implied a causal relationship between two factors that was never actually established. Adopting a narrative-memo requirement for future decisions of similar consequence is implemented specifically to prevent that same category of unstated logical gap from recurring.

Startup adoption: A venture-backed startup, following Amazon's documented practice, requires narrative memos rather than slide decks for its quarterly strategy reviews, with the founding team citing the same rationale Bezos describes — the act of writing full sentences forces the presenting team to actually work out and defend their reasoning in a way a slide outline does not.

Common Mistakes

• Allowing a slide deck alongside the memo to functionally replace it as the actual argument being discussed. If the room's attention shifts to slides during discussion, the narrative memo's discipline is defeated even if it was nominally written.
• Skipping the silent, at-the-start reading and instead distributing the memo in advance "for review." In practice, pre-distributed memos are frequently skimmed rather than read in full; the in-room silent-reading practice specifically ensures genuine engagement immediately before the discussion it informs.
• Applying the discipline to every routine meeting regardless of stakes, producing memo fatigue that degrades the quality of the memos themselves. Reserve the practice for decisions of real consequence, where the preparation cost is clearly justified.
• Treating the page-limit constraint as license to omit necessary logical steps rather than to compress prose efficiently. The limit should force prioritization and clarity, not the omission of the actual justification for a claim.

When NOT to Use

• For routine status updates, low-stakes informational meetings, or decisions where the cost of an undetected logical gap is trivial — the preparation overhead of a full narrative memo isn't justified at that scale.
• When the material is genuinely and primarily visual or quantitative in nature (e.g., a data visualization whose core value is the visual pattern itself) — narrative prose is not a substitute for a chart when the chart is the actual point being made; the discipline targets the surrounding argument and recommendation, not necessarily supporting data visualizations themselves.
• In fast-moving, time-constrained situations where a full written narrative genuinely cannot be produced before a decision must be made — a lighter-weight format is a reasonable tradeoff in those circumstances, with the narrative-memo discipline reserved for decisions where adequate preparation time exists.