Ask your boss for resources with trade-off math

Turn a request for extra budget, tools, or headcount into a clear business case based on operational trade-offs and capacity limits.

You getExecutive Summary, capacity Math & Bottleneck and three Decision Options

Prompt

Prompt
You are an executive operations advisor helping a manager present a realistic resource request to leadership.

- Analyze my current bottleneck, requested resource, and the operational trade-offs.
- Frame the situation objectively around delivery velocity, financial impact, or error risk rather than team stress.
- Present three realistic options: approve the request, maintain status quo with explicit trade-offs, or a phased middle ground.
- Keep the tone calm, constructive, and oriented around business goals.

Output format:
- Executive Summary (3 sentences maximum)
- Capacity Math & Bottleneck (quantified current state vs. projected gain)
- Three Decision Options (Option, Cost/Effort, Direct Trade-off)
- Recommended Action & 1-on-1 Talking Points

My raw notes about the situation are below:

Example output

Example for: requesting a mid-level QA engineer to alleviate release delays

Executive Summary

Our development output has grown 40% this quarter, but manual QA bandwidth remains capped at 80 hours per release cycle. Without dedicated testing support, release cycle times will slip by an estimated 4 business days per sprint. Approving one contractor or shifting delivery dates resolves this bottleneck immediately.

Capacity Math & Bottleneck
  • Current state: 6 engineers generate 24 pull requests weekly; 1 lead handles all staging verification (roughly 18 hours/week spent on regression tests instead of architecture).
  • Bottleneck: Regression testing backlog delays sprint deployments by an average of 3.5 days.
  • Projected gain: Adding 1 dedicated tester reclaims 18 engineering leadership hours weekly and reduces release verification time from 4 days to 24 hours.
Three Decision Options
  1. Approve 3-Month QA Contractor ($18k total): Maintains release velocity on the Q3 roadmap and protects lead engineer focus on core stability.
  2. Deprioritize Q3 Feature Beta: Absorb testing within current team by dropping two planned client-facing feature deliverables to accommodate quality checks.
  3. Shared Internal Rotation: Split staging verification across the 6 engineers, reducing overall sprint feature velocity by 15% without added monetary budget.
Recommended Action & 1-on-1 Talking Points
  • Recommendation: Approve a 3-month contract resource to validate delivery throughput before deciding on full-time hiring in Q4.
  • Talking point: "We can either add testing capacity for $6k monthly or adjust our Q3 milestone delivery date out by three weeks to maintain our quality bar."
Written by AI from this prompt. Your results will vary.

Paste your raw notes describing the workload, requested tool or role, and current bottlenecks directly into ChatGPT, Claude, or Gemini. As a follow-up, ask the model to draft a 5-sentence email summarizing the request for a busy executive.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management