Made for Engineers
Recover a Stalled Technical Decision
Also useful for: people in Software Engineers
75 min
Advanced
Software Engineers
Engineer
Communicate Better
Career outcome:
Avoid Professional Risk
Turn a looping technical debate into a clear diagnosis, focused evidence plan, decision meeting, and documented next move.
Create a free account to save your progress and use this Playbook.
Use this when
A technical decision keeps returning to review, meetings repeat the same arguments, evidence requests remain open-ended, or nobody is clearly authorized to close the issue.
You'll need
- Decision statement
- Consequence of delay
- Current state
- Decision deadline
- Options considered
- Stakeholders and authority
- Debate history
- Constraints
- Technical context
You'll get
- The decision framed as a specific choice
- The primary stall classified with supporting facts
- Decision authority confirmed or formally escalated
- Decision-changing uncertainties separated from low-value questions
- Evidence work limited by thresholds and time boxes
- A closure meeting scheduled or an asynchronous deadline set
By the end of this playbook
You will have:
- The decision framed as a specific choice
- The primary stall classified with supporting facts
- Decision authority confirmed or formally escalated
- Decision-changing uncertainties separated from low-value questions
- Evidence work limited by thresholds and time boxes
- A closure meeting scheduled or an asynchronous deadline set
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 whether billing should remain in the shared database or move toward an independent datastore before an enterprise launch. Current state: Repeated debate with no decision. Deadline: October 9. Options: Extend the shared schema, split immediately, or isolate billing logic now and delay the data migration. Authority: Architecture review is required, but the final decision owner is unclear. Debate: Platform prioritizes lower operational overhead. Billing prioritizes release independence and tighter access control. More load testing was requested without a defined threshold. Constraints: No new on-call rotation, fixed launch date, rollback required, stricter access controls needed. Evidence: Billing creates 12 percent of database writes. Two reporting incidents involved lock contention.
Sample assembled prompt
STALL DIAGNOSIS Primary blocker: Unclear authority. The architecture group reviews the change,... Secondary blocker: Undefined evidence threshold. More load testing was requested without... Underlying tradeoff: Lower near-term operating cost... SMALLEST CLOSURE PATH 1. Engineering director confirms the final decision... 2. Platform supplies current capacity and... 3. Security confirms whether logical controls... 4. No broad benchmark is run... 5. A 45-minute closure review occurs... CONDITIONAL RECOMMENDATION Choose logic isolation with... Choose the independent datastore now if... Don't select an immediate split... DECISION RULE The confirmed decision owner... Lack of consensus doesn't extend... Material dissent is recorded with the... FOLLOW-THROUGH - Record the decision and... - Assign implementation and migration owners. - Update launch dependencies and estimates. - Close superseded design tasks. - Set a review trigger tied...