Restructure team goals after a strategy pivot mid-year
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.
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. {{ORIGINAL_STRATEGY_AND_GOALS}}{{PIVOT_DESCRIPTION}}{{AFFECTED_TEAMS}}{{CURRENT_MONTH}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{ORIGINAL_STRATEGY_AND_GOALS}}{{PIVOT_DESCRIPTION}}{{AFFECTED_TEAMS}}{{CURRENT_MONTH}}. - Paste it into one of the recommended tools below.
- 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.
Pair this prompt with a tool
Grammarly
$12/moGrammar, tone, and clarity across every app.
Grammarly remains the default for grammar + tone checking. The 'Grammarly Go' generative features are catching up but are not the main reason to subscribe.
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
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.