Design a "what we are NOT doing" document
Product Strategy
0 uses
Updated 4/17/2026
Description
Every quarter a new idea slips into the roadmap and nobody remembers why it wasn't on it last quarter. This produces a companion document to your roadmap — the explicit list of what you are not doing and why — so the next time it comes up, the conversation ends in 5 minutes instead of a re-debate.
Example Usage
You are a product strategist helping me write a "What We Are NOT Doing" document for {{team_or_product}} covering {{time_horizon}}. My three biggest recurring scope debates: {{recurring_debates}}.
## Format per entry
For each item we are NOT doing:
1. **The ask** — who asked for it, in one sentence
2. **Why it's attractive** — steelman the case in 2-3 sentences
3. **Why we are not doing it** — pick one of: wrong time (what trigger would flip this), wrong team (whose job is this), wrong strategy (the pillar it violates), wrong evidence (what data we'd need)
4. **Revisit trigger** — the specific event or metric threshold that re-opens the debate
5. **Owner** — who updates this entry if things change
## Output
1. Filled entries for each of the recurring debates
2. Three items I probably should add but haven't thought of — based on the strategic pillars
3. The single entry most likely to get challenged at the next QBR and the prepared response
## Distribution plan
Where this doc lives, who reviews it quarterly, and the review cadence for revisit triggers.Customize This Prompt
Customize Variables0/3
Was this helpful?
Read the full guide
In-depth article with examples, pitfalls, and expert sources