A quarterly plan with 14 priorities ships zero. A good planning prompt forces 3-5 priorities, names what gets cut, computes capacity, and identifies what we won’t learn this quarter.
Who this is for
Function leads / PMs running quarterly planning, founders setting OKRs, engineering managers committing to a roadmap.
When not to use these prompts
Don’t use these as a wish list. Don’t use them when leadership won’t accept “no” — planning becomes theatre.
Prompt anatomy / structure formula
Every prompt should carry six elements:
- Role: who AI plays — chief of staff / manager / analyst.
- Context: team / org / scope / data.
- Goal: one deliverable — plan, memo, talking points, doc.
- Constraints: word count, must-include fields, audience seniority.
- Tone: confident, neutral, factual.
- Examples: 1-2 prior samples to anchor format.
Best for
- OKR / outcome drafting
- Capacity vs commitments math
- Trade-off framing
- Quarter kickoff memo
- Mid-quarter check-in
12 copy-ready prompt templates
1. Outcome-first priorities
Quarter: `{quarter}`. Generate 3-5 priorities. Each: (a) outcome (not output — what changes for users / business), (b) success metric, (c) why this not something else, (d) what we explicitly won't do.Variables to swap: quarter
2. Capacity math
Team has `{n}` people, `{weeks}` weeks effective. Map each priority to estimated person-weeks. Sum. If sum > capacity, list which priorities to cut. Don't pretend everything fits.Variables to swap: n, weeks
3. Outcome vs output check
Audit my priorities for output-thinking ("ship feature X") vs outcome ("X% lift in retention"). Rewrite each as outcome. If output is the goal, name the outcome it serves.4. Trade-off statement
For each priority, write a 1-sentence trade-off statement: "By doing X, we accept slower progress on Y." If you can't name a trade-off, the priority is probably untested.5. Bet ranking
Some priorities are "must-deliver", some are "bet" (learning). Classify each as: (a) Commitment, (b) Bet (we'll learn within Q whether to continue), (c) Stretch. Don't mark all as commitment.6. Quarter kickoff memo
Write the team kickoff memo: (1) Our 3-5 priorities, (2) What we won't do, (3) How we'll measure success, (4) Risks we're watching, (5) First milestones. ≤ 500 words.7. Cross-team dependency map
For each priority, list dependencies on other teams: (a) What we need, (b) When, (c) Who owns. Flag any dependency without an "owner" name.8. Mid-quarter check-in
Week 6 of quarter. Audit: (1) Which priorities are on / off track, (2) Should we cut any priorities now to focus, (3) Where the team is over-committed. Output a recalibration memo.9. Quarter retro
End of quarter. Retro: (1) Priorities shipped, (2) Priorities not shipped (and why), (3) What we learned that surprised us, (4) Process changes for next quarter. Output ≤ 300 words.10. “What we won’t learn”
For this quarter, name 3 things we won't learn (questions we won't answer). Naming them surfaces gaps. Decide: which can wait, which need a small bet next quarter.11. Leadership pitch
Pitch the quarterly plan to leadership in 5 sentences: (1) Theme, (2) 3 priorities + outcomes, (3) Trade-off accepted, (4) What we need from them, (5) Risks we're watching.12. Planning hygiene audit
Audit the plan: (1) > 5 priorities? Trim. (2) Any "improve X" with no metric? Make it concrete. (3) Capacity math actually done? (4) Trade-offs explicit? Output fix list.Common mistakes
- No specific context — output is generic.
- Skipping fact-check — AI invents numbers.
- Vague audience — over/undershoots seniority.
- No word limit — readers won’t finish.
- Same template every situation — readers tune out.
- No “decision needed” framing.
- Forgetting to attach source data.
How to push results further
- Specify audience level.
- Cap length: 1-page tactical, 3-bullet executive.
- Lead with the ask / decision needed.
- Attach source data link.
- Read aloud before sending.
- AI drafts; humans review.
- Save best examples; reuse format, refresh content.
Practical depth notes
Use these prompts as starting points, not final answers. For Quarterly Planning Prompts: 12 Templates Beyond a Wish List, the useful extra work is to replace every generic placeholder with a real constraint: audience, channel, length, brand voice, examples to imitate, and examples to avoid. Run at least two versions with different constraints, then compare the outputs side by side instead of accepting the first polished response.
A good result should pass three checks: it is specific enough that another person could reuse it, it avoids vague praise or filler, and it gives you an editable artifact rather than a broad suggestion. If the output feels generic, add one concrete reference, one forbidden pattern, and one measurable success criterion before rerunning the prompt. Before saving a prompt as reusable, test it on one realistic input and one edge case. The realistic input proves the template can produce the normal deliverable; the edge case shows whether it handles messy constraints, missing context, or an unusual audience. Keep the better output, but also keep the failed version with a note on what was missing. That small failure log is what turns a prompt collection from a list of nice sentences into a practical working library. One final check: compare the finished result against the original goal in a single sentence. If that sentence is hard to write, the output is probably polished but unfocused. Tighten the goal, remove decorative language, and rerun only the weak section instead of regenerating the entire piece.
FAQ
- How long should this doc be?: Tactical: 1 page. Executive: 3 bullets + link.
- Can AI replace the analyst / manager?: Drafts and templates yes; judgment no.
- How often refresh?: Cadence-driven; adjust when audience signals fatigue.
- Should risks be included?: Always. Pretending no risk exists erodes trust.
- How to fact-check?: Attach sources; peer review numbers.
- Can AI generate data?: No — AI invents plausible numbers. Connect real data.