Made for Engineers
Prepare a Technical Recommendation for Leadership Review
Also useful for: people in Software Engineering
120 min
Advanced
Software Engineering
Engineer
Communicate Better
Career outcome:
Avoid Professional Risk
Build a leadership-ready technical recommendation with clear options, evidence, risks, impacts, talking points, and decision follow-up.
Create a free account to save your progress and use this Playbook.
Use this when
You need leadership approval, funding, priority, or direction for a technical choice with meaningful cost, risk, timing, or stakeholder impact.
You'll need
- Decision context
- Problem statement
- Success measures and constraints
- Options considered
- Available evidence
- Stakeholder impacts
- Risks and uncertainties
- Cost, effort, and timeline
- Leadership review context
- Decision authority and milestone
You'll get
- The leadership decision stated in one sentence
- Mandatory constraints separated from preferences
- Every viable option assessed against the same criteria
- Critical claims labeled by evidence strength
- Material risks, dependencies, and stakeholder impacts documented
- The recommendation tied directly to evidence and tradeoffs
By the end of this playbook
You will have:
- The leadership decision stated in one sentence
- Mandatory constraints separated from preferences
- Every viable option assessed against the same criteria
- Critical claims labeled by evidence strength
- Material risks, dependencies, and stakeholder impacts documented
- The recommendation tied directly to evidence and tradeoffs
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: Select a modernization path for a nightly inventory data pipeline before peak season. Options include scaling the current design, rebuilding on managed cloud services, or migrating high-volume jobs in phases. Runtime history and a partial load test are available, but peak-volume behavior and two source-system integrations remain uncertain. Leadership is concerned about recurring cost, reliability, security review time, and delivery before October.
Sample assembled prompt
Decision requested: Approve a phased migration... Recommendation: Choose the phased path because... Approval should be conditional on a... Key tradeoff: The phased path takes... Confidence: Moderate. Runtime evidence is strong, but peak-volume...