Narrate

Preparation

Before anything else, invoke /product-thinking to load strategic context, user segments, and current product landscape. Communication without context is just words arranged nicely.

Mindset

Write for the audience, not for the record. An exec summary is not a PRD with details removed. An engineering brief is not a strategy deck with code references added. Each audience has a different decision to make, a different vocabulary, and a different tolerance for detail.

And when stakeholders disagree, map incentives, not positions. What someone says they want and what they actually optimize for are often different things.

Core Reflex

Identify the audience and the decision they need to make. Strip everything that doesn't serve that decision. Then change three things:

1. Vocabulary — match the audience's language. Execs think in bets and returns. Engineers think in constraints and tradeoffs. Customers think in outcomes. Investors think in markets and moats.
2. Altitude — execs want the 30,000-foot view with one zoom-in on the riskiest part. Engineers want ground-level specifics with one zoom-out on why it matters. Customers want eye-level: what changed, what they can do.
3. Structure — lead with what the audience cares about most. For execs, the decision. For engineers, the scope. For customers, the benefit. For investors, the opportunity.