Made for Engineers
Build a Decision Room Pack for a Technical Tradeoff
Also useful for: people in Technology
90 min
Advanced
Technology
Engineer
Communicate Better
Career outcome:
Avoid Professional Risk
Assemble eight linked resources for presenting a technical choice, testing the recommendation, recording the call, and sending a precise follow-up.
Create a free account to save your progress and use this Playbook.
Use this when
You need a technical choice approved, challenged, or escalated, and the decision involves competing options, meaningful risk, cost or timeline pressure, and incomplete information.
You'll need
- Decision question
- Options under consideration
- Constraints and non-negotiables
- Available evidence
- Scoring criteria and priorities
- Stakeholders and authority
- Risk tolerance
- Decision deadline
- Known unknowns
You'll get
- The decision question bounded by scope, deadline, and authority
- Every viable option scored against explicit criteria
- Material risks translated into operational or business effects
- Cost and timeline figures labeled by evidence type
- Decision-blocking unknowns separated from deferrable unknowns
- A one-screen meeting visual ready to present
By the end of this playbook
You will have:
- The decision question bounded by scope, deadline, and authority
- Every viable option scored against explicit criteria
- Material risks translated into operational or business effects
- Cost and timeline figures labeled by evidence type
- Decision-blocking unknowns separated from deferrable unknowns
- A one-screen meeting visual ready to present
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: Choose the authentication approach for a customer portal before October 18. Options: Extend the current service, adopt a managed identity platform, or build a dedicated service. Constraints: SSO support, security approval, no stored passwords, launch before the holiday freeze, and limited platform capacity. Evidence: The managed platform passed an integration spike and costs $84,000 annually. Extending the current service is estimated at 10 to 14 engineering weeks, excluding migration support. No reliable estimate exists for a new service. Priorities: Security 35%, delivery time 25%, operational burden 20%, three-year cost 20%. Authority: VP of Engineering, with Security holding approval authority. Risk tolerance: Moderate. Unknowns: Vendor rate limits, legacy-account migration effort, and procurement timing.
Sample assembled prompt
DECISION FRAME Choose whether to extend... Approval is needed by October 18... Detailed migration sequencing is out of... SCORECARD FINDING The managed platform leads... The new-service option can't be responsibly... The current-service option remains viable but... RISK TRANSLATION Risk: Vendor peak-login limits... Effect: Customers could face failed or... Status: Decision-blocking until the limit is... Mitigation: Obtain a contractual limit and... RANGE VIEW Managed platform: $84,000 annual... Current service: 10 to 14 engineering... Dedicated service: Cost and timing not... RECOMMENDATION Proceed toward the managed platform... If either condition fails, run a... READINESS STATUS Ready with named gaps. The preferred option has stronger evidence,...