memo-stress-tester
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.
More from joellewis/skill-library
problem-framing
Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.
3devils-advocate
Use when a proposal has unanimous support or relies on a single high-impact assumption—constructs the strongest possible counter-argument (Steel Man) and runs a Pre-Mortem.
2prd-writing
Use when translating a product vision into engineering requirements—enforces the Working Backwards PR/FAQ method, requiring a customer-facing press release before any technical spec.
1executive-briefing
Crafts senior leadership communications that deliver judgment rather than activity reports, connecting directly to organizational strategy and driving clear decisions. Use when presenting to board members, C-suite executives, or senior leadership — including status updates, recommendations, and escalations.
1copy-editor
Performs line-level prose editing — pruning adverbs, activating voice, cutting redundancy, and enforcing parallel structure for concision and readability. Use when revising any written content, even if the request is just 'make this better,' 'tighten this up,' or 'clean up the writing.'
1market-context
Use when validating market timing, structural forces, or distribution moats before committing strategic resources—focuses on macro context, not individual competitor teardowns.
1