memo-stress-tester

name	memo-stress-tester
type	domain
family	rhetorician
rigor	standard
description	Use when evaluating business documents for structural integrity and persuasive logic.
keywords	business-writing, memos, stress-testing, clarity, structure, briefing
compatibility	Claude Code and compatible agent products
requires	[]
enhances	["non-fiction-precision","prd-writing","executive-briefing"]
sources_pdf	["The Pyramid Principle (Minto)","The Effective Executive (Drucker)","Working Backwards (Bryar)"]
sources_web	["Amazon 6-pager methodology","Completed Staff Work doctrine"]

Overview

Memo stress-testing is the rigorous evaluation of a business document's "readiness" for executive decision-making. It identifies logical gaps, unproven assertions, and "half-baked" ideas. By applying the Amazon narrative standard, Minto's pyramid logic, and the doctrine of Completed Staff Work, it ensures that a document is a self-contained tool for strategic action rather than a draft for the boss to finish.

Guiding Principles

Principle 1: Completed Staff Work (Source: Web, Completed Staff Work Doctrine)

Study, write, restudy, and rewrite until you have evolved a single proposed action. The "Chief" should only need to approve or disapprove. If the superior has to do more research or thinking, the staff work is incomplete.

Principle 2: The Self-Contained Narrative (Source: Bryar, Working Backwards)

A memo must stand on its own without a supporting presentation. It should be a narrative that forces better thinking and allows for deep, silent reading. If the document relies on "hallway context" or a presenter's explanation, it fails the stress test.

Principle 3: MECE Validation (Source: Minto, The Pyramid Principle)

Every group of supporting points must be Mutually Exclusive (no overlaps) and Collectively Exhaustive (no gaps). If points in a list overlap, the logic is "fuzzy." If a key driver is missing, the document is fragile.

Principle 4: Contribution over Effort (Source: Drucker, The Effective Executive)

The memo must focus on the results and contribution to the organization, not the effort centers (costs/internal processes). An effective memo identifies what needs to be done to move the needle on the outside environment.

Principle 5: The "Answer First" Order (Source: Minto, The Pyramid Principle)

Never build a "logical crescendo" where the recommendation is at the end. State the conclusion first, then support it. Executives are paid to make decisions; don't make them wait for page 6 to see what they are deciding.

When to Use This Skill

• Before submitting a proposal to senior leadership.
• Reviewing a peer's PRD or strategic brief.
• Auditing a document after a meeting resulted in "no decision" or "more research needed."
• Compressing a long report into a "one-pager."

When NOT to Use This Skill

• Brainstorming/Ideation phases where logic is still fluid.
• Informal updates or status reports that don't require a decision.

Core Process

Step 1: The "Completed Staff Work" Audit (Source: Web)

Ask: "If I presented this to the CEO today, could they say 'Yes' or 'No' and be done with it?"