There is a widespread assumption that a strategy document is a record of thinking that has already occurred, a transcription of conclusions reached in meetings and now committed to paper for distribution. This assumption is precisely backward, and recognizing why is among the more consequential shifts a product leader can make. The discipline of writing a strategy down, in a structured form that forces completeness and exposes weakness, is not the documentation of thinking but the act of thinking itself, since the gaps, the unsupported leaps, and the unexamined assumptions that a conversation glides over become visible and unavoidable the moment one is required to render the argument in prose. This module examines the principal frameworks through which product leaders communicate strategy, namely the narrative memo, the strategy document, the press-release-and-FAQ format, and the one-page narrative, and argues that their value lies less in communication than in the quality of thought they compel, with attention to how the AI transition is changing how these documents are produced and what they must now contain.
The Narrative Memo and the Discipline of Prose
The narrative memo, a document of structured prose rather than bulleted slides, was elevated to an organizational practice most famously at Amazon, where Jeff Bezos instituted a requirement that proposals be presented as written narratives rather than presentations, having concluded after considerable experimentation that the narrative form forced a quality of thought the slide deck permitted teams to evade (Bryar & Carr, 2021). The mechanism is specific and worth stating precisely: a slide deck allows ideas to be presented as fragments whose logical relationships and relative importance remain unstated, which permits the author to gloss over weak connections and the audience to fill gaps with charitable assumptions, whereas prose requires the author to state how each idea relates to the next, which exposes the places where the reasoning does not actually connect. The discipline of writing a coherent six-page narrative is harder than producing a twenty-slide deck precisely because the narrative cannot hide its gaps, and the difficulty is the point, since the document that is hard to write is the document whose weaknesses were found and fixed before the strategy was executed rather than after.
The organizational practice that surrounds the narrative memo, in which the document is read in silence at the start of a meeting before discussion begins, reinforces its value by ensuring that the audience engages with the full argument rather than with a presenter’s selective narration of it, which subjects the strategy to genuine scrutiny rather than to the persuasive performance that slides invite.
The Strategy Document and the Avoidance of the Bad-Strategy Trap
The strategy document, the durable articulation of where a product is going and why, earns its value when it avoids what Richard Rumelt (2011) terms bad strategy, which he characterizes as the substitution of ambitious goals, vision statements, and aspirations for the actual content of strategy, namely a diagnosis of the situation, a guiding policy for addressing it, and a coherent set of actions that follow. Rumelt’s contribution is to insist that a real strategy contains a clear-eyed diagnosis of the challenge the organization actually faces, since a strategy that does not name the central obstacle cannot coherently address it, and the most common failure of strategy documents is that they enumerate goals and initiatives without ever diagnosing the problem those initiatives are meant to solve. A strategy document built on Rumelt’s structure forces the product leader to state what is genuinely hard about the situation before proposing what to do about it, which prevents the document from becoming the list of aspirations and disconnected initiatives that masquerades as strategy in most organizations.
The Press-Release-and-FAQ Format and Working Backwards
The press-release-and-FAQ format, developed at Amazon as the instrument of its working-backwards process, addresses a different failure, which is the tendency to design a product around what is feasible to build rather than around what is valuable to the customer (Bryar & Carr, 2021). The format requires the team to write, before building anything, the press release that would announce the finished product as though it were launching, articulating in customer-facing language the value the product delivers and why the customer should care, followed by the frequently asked questions that surface and answer the hard problems the product must solve. The discipline this imposes is to begin from the customer experience and reason backward to what must be built, rather than beginning from what can be built and reasoning forward to a customer who might want it, which inverts the failure mode that produces technically impressive products no customer values. The format also functions as a forcing device for honesty, since a press release that does not describe a compelling customer benefit reveals, before any resources are committed, that the idea is not yet worth building.
The One-Page Narrative and the Compression of Conviction
The one-page narrative, the discipline of compressing a strategy into a single page, is the most demanding format because compression is where understanding is tested most severely, as a strategy that cannot be expressed clearly in one page is frequently a strategy that is not yet clearly understood. The value of the one-pager is not that it is convenient for busy readers, though it is, but that the act of compression forces the author to identify what is genuinely essential and to discard what is merely included, which clarifies the strategy for the author before it clarifies it for any reader. The one-page narrative also serves the propagation function described in the prior module, since a strategy compressed to its essence is portable in a way that a long document is not, traveling through the organization in the form that people can hold in memory and repeat accurately.
Strategy Communication in the Age of AI
The AI transition acts on strategy communication in two directions the product leader should weigh. The first is that AI can now draft, structure, and critique strategy documents, which is genuinely useful for overcoming the blank page and for stress-testing an argument against anticipated objections, but which carries a specific hazard, since the value of these documents was never the prose but the thinking the prose compelled, and a strategy document generated rather than reasoned through delivers the artifact while skipping the cognitive work that was its entire purpose. The product leader must therefore use AI to sharpen and pressure-test thinking that the leader has actually done, rather than to substitute for the thinking, since a fluent document produced without the underlying reasoning is more dangerous than an awkward one produced with it, as it carries the appearance of rigor without its substance. The second is that strategy documents in the AI era must increasingly address questions that did not previously arise, namely how the strategy accounts for the commoditization of capability, where its defensibility resides, and how it positions against an uncertain trajectory of model advancement, which means the content these frameworks must carry has expanded even as the tools for producing them have improved.
The synthesis for the product leader is that strategy communication frameworks are thinking tools first and communication tools second, and that their discipline is the source of their value. The agenda is to write strategy as narrative prose that exposes the gaps slides conceal, to structure strategy documents around diagnosis rather than aspiration, to use the working-backwards format to reason from customer value rather than from feasibility, to compress strategy to a single page as a test of genuine understanding, and to deploy AI as an instrument that sharpens reasoning the leader has done rather than as a substitute for the reasoning itself. The document is the thinking, and the product leader who treats the writing as the work, rather than as the record of work done elsewhere, will produce both better strategies and better organizational alignment around them.
References
Bryar, C., & Carr, B. (2021). Working backwards: Insights, stories, and secrets from inside Amazon. St. Martin’s Press.
Rumelt, R. P. (2011). Good strategy / bad strategy: The difference and why it matters. Crown Business.