Made for Engineering Managers
Make the Priority Cut Everyone Has Been Avoiding
Also useful for: people in Engineering Managers, people in Software Engineering Managers
90 min
Advanced
Engineering Managers
Engineering Manager
Improve Team Performance
Career outcome:
Avoid Professional Risk
Decide which engineering initiatives continue, pause, shrink, or stop when demand exceeds real team capacity.
Create a free account to save your progress and use this Playbook.
Use this when
Your team has more committed work than available capacity, every initiative has a vocal sponsor, and avoiding a cut is putting delivery, reliability, or team health at risk.
You'll need
- Decision horizon
- Team goals
- Candidate initiatives
- Capacity constraint
- Existing commitments
- Dependencies
- Available evidence
- Stakeholder realities
- Risk posture
- Decision authority
You'll get
- Every candidate initiative assigned a Continue, Pause, Shrink, or Stop decision
- A forced ranking with no unresolved ties
- Protected obligations supported by explicit evidence
- Released capacity assigned or reserved as a deliberate buffer
- Decision risks, assumptions, review triggers, and owners documented
- Stakeholder talking points ready for the decision meeting.
By the end of this playbook
You will have:
- Every candidate initiative assigned a Continue, Pause, Shrink, or Stop decision
- A forced ranking with no unresolved ties
- Protected obligations supported by explicit evidence
- Released capacity assigned or reserved as a deliberate buffer
- Decision risks, assumptions, review triggers, and owners documented
- Stakeholder talking points ready for the decision meeting.
Sample
This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.
Sample input
Decision horizon: Next two quarters. Goals: Complete the billing migration before the vendor exit, reduce payment failures, and support an enterprise launch without increasing on-call load. Initiatives: Billing migration, checkout reliability, enterprise reporting, developer portal, and search redesign. Capacity: 38 engineer-weeks after support, incidents, and leave. Total requested work is about 70 engineer-weeks. Commitments: Billing vendor contract ends in November. Enterprise reporting was discussed with customers but has no signed deadline. The VP publicly supports the developer portal. Dependencies: Billing and checkout both need the same senior engineer. Checkout also depends on a platform event pipeline. Evidence: Payment failures affect 2.8 percent of transactions. The migration estimate has medium confidence. Portal adoption is based on interviews rather than usage data. Stakeholders: Finance owns the vendor exit, Sales expects reporting, and the VP sponsors the portal. Risk posture: Balanced. Authority: I can change scope and sequencing, but my director must approve stopping VP-sponsored work.
Sample assembled prompt
Executive decision: Continue the billing migration... Shrink enterprise reporting to the three... Pause the developer portal pending evidence... Stop the search redesign for this... Forced ranking: 1. Billing migration 2. Checkout reliability 3. Enterprise reporting minimum scope 4. Developer portal 5. Search redesign Decisive tradeoffs: - Billing... - Checkout beats reporting because current... - Reporting beats the portal because... - The portal beats search because... Capacity decision: - Billing migration: Continue,... - Checkout reliability: Continue with the... - Enterprise reporting: Shrink to three... - Developer portal: Pause until a... - Search redesign: Stop for this... - Risk buffer: Reserve 4 engineer-weeks... Review trigger: Reconsider the portal if... Revisit checkout scope if payment failures...