PlaybookPrompts

Write a one-page annual plan the whole team will actually read

Business Strategy planningoperationsleadership

Annual plans balloon into decks nobody references by February. This prompt produces a single-page document that captures priorities, constraints, and success criteria without the bloat.

Prompt
You are an operator helping a founder write a lean annual plan. Our company is {{COMPANY_DESCRIPTION}}. Our top three strategic priorities for {{PLAN_YEAR}} are {{TOP_THREE_PRIORITIES}}. Key constraints (budget, headcount, runway) are {{KEY_CONSTRAINTS}}. Last year's results to build from: {{PRIOR_YEAR_RESULTS}}.

1. Write a single-paragraph 'context and position' section (max 80 words) that describes where we stand at the start of the year—honest about both advantages and gaps.
2. For each of the three priorities, write: (a) a one-sentence goal, (b) the specific metric we will use to measure success, (c) the target value and deadline, and (d) the single biggest risk to achieving it.
3. Write a 'what we are not doing' list of three to five explicit de-prioritizations. These should be real trade-offs, not obvious non-starters.
4. Write a 'decision rules' section: two or three criteria the team can use to resolve prioritization conflicts without escalating to leadership every time.
5. Format the full output so it fits on one printed page if font size is 11pt. Flag anything that should be cut if length is the constraint.

Do not pad the document. Brevity is the goal.
Variables to fill in
  • {{COMPANY_DESCRIPTION}}
  • {{PLAN_YEAR}}
  • {{TOP_THREE_PRIORITIES}}
  • {{KEY_CONSTRAINTS}}
  • {{PRIOR_YEAR_RESULTS}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{COMPANY_DESCRIPTION}}{{PLAN_YEAR}}{{TOP_THREE_PRIORITIES}}{{KEY_CONSTRAINTS}}{{PRIOR_YEAR_RESULTS}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.