Draft a decision-ready strategy memo from the information below. Treat my facts, estimates, and assumptions differently. Do not invent market data, customer evidence, financial results, stakeholder agreement, or implementation capacity. Decision and recipient: [DECISION AND RECIPIENT] Context and problem to solve: [CONTEXT AND PROBLEM] Evidence, constraints, and assumptions: [EVIDENCE AND CONSTRAINTS] Options considered: [OPTIONS]
My tentative recommendation and requested decision: [TENTATIVE RECOMMENDATION]
Write 700–1,000 words in this order: title; decision requested; executive summary of no more than 120 words; context; objectives and non-objectives; options; recommendation; execution plan; risks and mitigations; and explicit next steps. Write for the recipient’s likely decision horizon, using the tone implied by their role. Lead with the decision, not the history.
For each option, include expected benefit, cost or tradeoff, key dependency, and what would make the option fail. Compare options against criteria drawn from the stated problem, such as speed, cost, reversibility, customer impact, or operational load. If numbers are estimates, label them as estimates and show the basis provided. The recommendation must state why it wins against the alternatives and what decision or resource is needed now. The execution plan must identify an owner, first milestone, decision checkpoint, and measurable signal of progress only where the inputs support them.
Before answering, run two checks: confirm the requested decision is explicit and confirm each major assertion is sourced, labeled as an assumption, or removed. End with a short “Open questions” section rather than filling gaps. Ask up to three clarifying questions only if a required input is missing.Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [DECISION AND RECIPIENT] | State the decision needed and who will read or approve the memo. | VP Product needs to choose a Q4 onboarding investment by October 2. |
| [CONTEXT AND PROBLEM] | Explain the current situation and the specific problem the memo addresses. | New teams take 28 days to publish their first workflow; the target is 14 days, and setup abandonment is highest after data import. |
| [EVIDENCE AND CONSTRAINTS] | Provide facts, data, deadlines, budget limits, dependencies, and clearly marked assumptions. | Interviews with 12 admins cite import mapping confusion. Analytics shows 41% abandon that step. One product squad is available for six weeks; no budget for a new vendor. |
| [OPTIONS] | List the realistic options, including the status quo where relevant. | Improve import mapping in-product; add concierge onboarding; leave the flow unchanged and improve help content. |
| [TENTATIVE RECOMMENDATION] | State your current recommendation and the decision, resources, or approval you want. | Fund the in-product mapping work and approve six weeks of the onboarding squad, with a week-three usability checkpoint. |
How to use
- Paste the prompt with a concrete decision, not a broad topic.
- Mark estimates and assumptions in the evidence field before generating.
- Check that the recommendation requests a specific decision and names the tradeoffs.
- Send: “Stress-test the recommendation against the status quo and identify evidence that could reverse it.”
Variations
One-page memo
Use when an executive needs the decision case in a single page.
Write a one-page strategy memo for [RECIPIENT] requesting [DECISION]. Use this context: [CONTEXT], evidence: [EVIDENCE], and options: [OPTIONS]. Return five sections: decision, why now, options compared, recommendation, and next step. Limit it to 500 words. Include only the two or three facts that change the decision, label assumptions, and state the main tradeoff of the recommendation. Do not add market figures or implementation promises. Check that the requested decision is clear in the first two sentences.
Strategy critique
Use when a draft memo needs a rigorous review before circulation.
Critique this strategy memo: [DRAFT MEMO]. The intended reader is [AUDIENCE], and the decision sought is [DECISION]. Return a table identifying unclear decision language, unsupported claims, missing alternatives, untested assumptions, unowned work, and risks without mitigations. Then provide a revised outline, not a full rewrite. Assess whether the recommendation follows from the evidence supplied. Do not supply missing facts; turn them into specific research questions or open questions.
Operating plan
Use after a strategy has been approved and needs execution detail.
Turn this approved strategy into a 90-day operating plan: [STRATEGY]. Available team and constraints: [RESOURCES]. Required outcomes: [OUTCOMES]. Return a phased plan with workstream, owner, milestone, dependency, evidence of completion, and weekly leading indicator. Include a decision log and three risks with trigger-based contingencies. Use only named owners and dates provided; leave unknown fields marked “TBD.” Check that every workstream supports an outcome and that dependencies precede dependent milestones.
Tips
- A strategy memo earns attention by making the decision and its consequence visible before the background.
- Include the status quo as an option when it is genuinely viable; it exposes the cost of inaction.
- Label a forecast as an estimate and state its basis, such as a pilot result or a capacity calculation.
- Use non-objectives to prevent readers from assuming the proposal solves adjacent problems.
FAQ
How is a strategy memo different from a project plan?
A strategy memo explains the choice and why it should be made. A project plan details how an approved choice will be executed.
Should the memo include a recommendation?
Usually yes. Present alternatives fairly, then explain the decision you recommend and the tradeoff you accept.
Can AI create the evidence section?
It can structure evidence you provide, but it should not fabricate research, forecasts, or stakeholder views.