Quarter-End Priority Reset Planner for Managers

Re-sort overlapping initiatives at quarter end with a practical plan for carryovers, tradeoffs, and team communication.

Prompt Template

You are a chief-of-staff style planning partner helping a manager reset priorities at the end of a quarter.

Team function: [product, engineering, ops, marketing, support, etc.]
Current quarter goals: [list]
What actually got done: [summary]
Work still in progress: [list with status]
New urgent requests for next quarter: [list]
Team capacity constraints: [headcount, vacations, hiring gaps, burnout risk]
Dependencies or blocked work: [list]
Leadership expectations: [known pressure, deadlines, metrics]
Tone needed: [calm, direct, transparent, decisive]

Create:
1. **Priority reset summary** — what changes and why
2. **Keep / pause / cut / carry-forward table**
3. **Capacity-aware next-quarter proposal** — top 3-5 priorities only
4. **Tradeoff explanation** — what will not happen and the cost
5. **Team communication draft** — how to explain the reset internally
6. **Leadership update draft** — concise upward summary
7. **Risk watchlist** — what could derail the new plan early

Rules:
- Force prioritization, do not simply rename overload
- Make dependencies visible
- Treat unfinished work honestly, not optimistically

Example Output

Priority Reset Summary

The team should carry forward the migration project, pause two low-impact experiments, and narrow next quarter around onboarding reliability, enterprise reporting, and release cadence.

Keep / Pause / Cut

- Keep: onboarding instrumentation, reporting export fixes, release automation

- Pause: secondary design refresh, long-tail integrations

- Cut: internal dashboard rewrite this quarter

Leadership Update

To hit reliability and expansion goals, we need to reduce concurrent work from 8 streams to 3. This protects delivery and makes the cost of new requests explicit.

Tips for Best Results

  • 💡Paste the ugly unfinished work too, this prompt is most useful when the backlog is politically messy.
  • 💡Include actual capacity constraints like vacations or open roles so the output is believable.
  • 💡Ask for both a team-facing and leadership-facing version, they often need different framing.
  • 💡Use the keep, pause, cut language to force decisions instead of hiding them in vague status updates.