The prompt
Score 10 of 10, Excellent
Use it when You have been told to cut your team's budget by a set amount and need options that reach it, with the effect of each on goals and people.
- {{team}}
- {{cut_amount}}
- {{period}}
- {{approver}}
- {{budget_lines}}
- {{total_budget}}
- {{goals}}
- {{protected}}
Full prompt and why it works
Prompt
# Role You help a manager decide where to cut their team's budget. You lay out options with their effect on goals and people, show every calculation, and leave the decision with the manager. # Goal Find ways to cut {{team}}'s budget by {{cut_amount}} over {{period}}, for me to choose from and then explain to {{approver}} and my team, so that the cut lands where it does the least harm to what we have committed to. # Success criteria - Every option reaches the target, with the arithmetic shown line by line. - Each option says what it does to our goals, our people and the people who depend on us. - One-time savings and recurring savings are kept apart, because they solve different problems. # Constraints - Use only the budget lines and facts below. Do not invent costs, prices, notice periods or cancellation terms. - Do not count the same saving twice across lines. - Any option that removes a role, cuts a contractor or changes anyone's hours is marked "[HR review]", and you do not choose which person is affected. - Do not touch lines marked as protected unless no option reaches the target without them; if so, say that plainly. # Output Use a Markdown heading for each part. 1. Budget lines: a table with the columns Line, Annual cost, Type (fixed, contracted, discretionary), How hard to cut, Notes. 2. Options: three to five packages that each reach {{cut_amount}}, each as a short table of the cuts and their savings, then the effect on goals, people and risk, and how easy it is to reverse. 3. Ranking: the options in order, with one or two sentences on why. 4. What to protect, and why. 5. Talking points: under 150 words for {{approver}} and under 200 words for my team, plain and honest about what changes. For example, a line in an option could read: "Pause the conference budget for the year: saves [amount], recurring; effect: no external speaking slots; low risk, easy to restart." That example shows the form only. # Stop rules If the budget lines do not add up to the total I gave, stop and show the difference before building options. If the target cannot be reached without cutting people costs, say so first, before any option. If a line's contract terms are unknown, mark it "[contract terms to check]" rather than assuming it can be ended early. # Context Budget lines (line, cost, what it pays for, any contract terms): """ {{budget_lines}} """ Total budget: {{total_budget}} Our goals for the period: {{goals}} What must be protected, and why: {{protected}}
Variables
- {{team}}
- Your team, for example "the marketing team".
- {{cut_amount}}
- The amount to cut, for example "$120,000" or "10% of the annual budget".
- {{period}}
- Over what time, for example "the rest of this financial year".
- {{approver}}
- Who signs off the cut, for example "my VP and the finance partner".
- {{budget_lines}}
- Each budget line with its cost, what it pays for and any contract terms you know.
- {{total_budget}}
- The team's total budget for the period.
- {{goals}}
- What the team is committed to deliver in the period.
- {{protected}}
- Lines that must not be cut and why, or "none".
Why it works
- What good looks like. Every option must reach the target with the arithmetic shown, and one-time savings are kept apart from recurring ones, so the plan cannot look better than it is.
- What to avoid. Changes to roles, contractors or hours are marked [HR review], and the model never chooses which person is affected.
- If unsure. Budget lines that do not add up stop the work, and unknown contract terms are marked to check instead of assumed to be cancellable.