PlaybookPrompts

Restructure team goals after a strategy pivot mid-year

Business Strategy planningleadershipokrs

A mid-year pivot invalidates half your OKRs but you still need people pointed at something concrete. This prompt helps you rewrite team-level goals quickly without throwing away all existing momentum.

Prompt
You are an operator helping a founder realign team goals after a strategic change. Our original strategy and goals for the year were {{ORIGINAL_STRATEGY_AND_GOALS}}. The pivot or strategic change we are making is {{PIVOT_DESCRIPTION}}. The teams or functions affected are {{AFFECTED_TEAMS}}. We are currently at {{CURRENT_MONTH}} in the year.

1. Review the original goals and classify each as: (a) still fully valid under the new strategy, (b) partially valid and needs rewriting, or (c) obsolete and should be dropped.
2. For each goal marked partially valid, rewrite it to align with the new strategy. Keep the same measurement format if possible so progress to date isn't wasted.
3. Identify any new goals the pivot creates that were not in the original set. Write them in the same format as the existing goals.
4. Write a short all-hands message (max 150 words) explaining the goal changes to the team. It should acknowledge what is being dropped and why, without over-explaining or apologizing.
5. Flag any team or function whose goals are now in conflict with each other due to the pivot—these need a separate conversation before the new goals are published.

Assume people are already aware of the strategic change. Do not re-explain the pivot—just deal with the goal implications.
Variables to fill in
  • {{ORIGINAL_STRATEGY_AND_GOALS}}
  • {{PIVOT_DESCRIPTION}}
  • {{AFFECTED_TEAMS}}
  • {{CURRENT_MONTH}}

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: {{ORIGINAL_STRATEGY_AND_GOALS}}{{PIVOT_DESCRIPTION}}{{AFFECTED_TEAMS}}{{CURRENT_MONTH}}.
  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.