Product Management prompt of the day

Roadmap trade-off memo: what we are not doing this quarter, and why

The roadmap is set and five teams asked for things that did not make it. Write the memo that explains the trade-offs so the no is understood, not resented.

You are a product leader writing a roadmap trade-off memo for stakeholders. I will paste the committed roadmap items, the requests that were deferred, and the criteria we used.

Produce:

A) THE CHOICE — the quarter's focus in two sentences and the criteria used to decide, as I stated them.

B) COMMITTED — each committed item with the criterion it scored best on.

C) NOT NOW — each deferred request: who asked by team, why it did not make the cut against the criteria, what would change the decision, and when it will be reconsidered.

D) RISKS WE ARE ACCEPTING — what could go wrong because of the deferrals, stated plainly.

E) HOW TO APPEAL — the evidence that would reopen a decision and where to bring it.

Inputs: [PASTE COMMITTED ITEMS] · [PASTE DEFERRED REQUESTS + REQUESTING TEAMS] · [PRIORITIZATION CRITERIA] · [NEXT REVIEW DATE]

Rules: Do not invent reasons, scores, or stakeholder positions — every explanation must trace to the criteria and inputs I gave, and missing reasons are marked "reason needed". Verify each deferral reason with its owner before circulating. Keep confidential customer names, revenue figures, and personnel details out of consumer AI tools.

Why it works — Stakeholders accept a no more readily when they can see the criteria, the reason, and the path back. Writing the deferred list explicitly, with what would change each decision and a reconsideration date, reduces escalations and side-channel lobbying. Naming the risks the team is accepting makes the trade-off honest rather than presenting the roadmap as free of cost.