PlaybookPrompts

Score and sequence competing initiatives when everything feels urgent

Productivity & Planning prioritizationstrategyplanning

When every initiative has a champion and every stakeholder says their project is top priority, you need a defensible scoring framework — not a gut call. This prompt builds one from your actual constraints.

Prompt
You are my chief of staff helping me sequence competing initiatives. I cannot pursue all of them at once. Here is a list of the initiatives under consideration: {{INITIATIVES_LIST}}. Here are my team's real capacity constraints: {{CAPACITY_CONSTRAINTS}}. Here are the organization's current top priorities: {{ORG_PRIORITIES}}. Here is the time horizon I am planning for: {{TIME_HORIZON}}.

1. For each initiative, score it on four dimensions using a 1–5 scale. Define the scale before scoring:
   - Strategic alignment: how directly does this advance the org's current priorities?
   - Expected impact: what is the realistic magnitude of the outcome if it succeeds?
   - Confidence: how well-defined is the work and how proven is the approach?
   - Effort required: inverse score — high effort gets a low score.
2. Calculate a weighted total for each initiative. Use equal weighting unless I specify otherwise.
3. Propose a sequencing recommendation: what to do now, what to defer to next quarter, and what to deprioritize or kill.
4. Write a one-sentence rationale for each deprioritized item so I can communicate the decision to stakeholders without ambiguity.
5. Flag any initiative where my scoring inputs were inconsistent or where I may be undercounting effort or overcounting impact.

Do not recommend doing everything in parallel. Parallelism is a constraint, not a solution.
Variables to fill in
  • {{INITIATIVES_LIST}}
  • {{CAPACITY_CONSTRAINTS}}
  • {{ORG_PRIORITIES}}
  • {{TIME_HORIZON}}

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: {{INITIATIVES_LIST}}{{CAPACITY_CONSTRAINTS}}{{ORG_PRIORITIES}}{{TIME_HORIZON}}.
  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.