Made for Founders
Diagnose a Stalled Company Priority
Also useful for: people in Founders
75 min
Business & Entrepreneurship
Make a Decision
Need to Make a Decision
Trace a stalled priority from visible symptoms to its root constraint, then build a focused recovery plan that protects the company from repeated slippage.
Create a free account to save your progress and use this Playbook.
Use this when
A company priority has missed milestones, progress reports sound vague, several teams blame each other, or the current recovery plan amounts to working harder without fixing the constraint.
You'll get
- The intended outcome rewritten as a testable result
- Verified facts separated from interpretations
- All six cause categories tested against evidence
- The primary constraint named with a confidence level
- Recovery, reduction, pause, or stop options compared
- One recommended move tied to an explicit tradeoff
By the end of this playbook
You will have:
- The intended outcome rewritten as a testable result
- Verified facts separated from interpretations
- All six cause categories tested against evidence
- The primary constraint named with a confidence level
- Recovery, reduction, pause, or stop options compared
- One recommended move tied to an explicit tradeoff
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
Priority: Launch self-serve onboarding this quarter. Outcome: Reach 60% setup completion and first value within one day by November 15. Evidence: Two missed beta dates; most open issues trace to unresolved billing rules. Ownership: Product owns delivery, but no single owner controls finance, legal, engineering, and customer success decisions. Dependencies: Billing policy, cancellation language, activation criteria, and QA. Capacity: Engineering is split across enterprise requests; product is covering a hiring gap. Incentives: Sales creates custom terms, engineering protects reliability, and customer success expects higher support demand. Assumptions: One common setup path appears valid, but standardized billing and unsupported activation remain untested. Constraints: Decision needed Friday; security and contracted work can't move.
Sample assembled prompt
Executive Diagnosis The primary constraint is... Billing ambiguity is the controlling dependency,... Contributing factors: 1. Capacity dilution from enterprise requests. 2. Conflicting incentives around custom contracts... 3. An untested assumption that activation... Recommended Move Reduce the first release... Assign the head of product as... Move two lower-priority roadmap items and... 30-Day Recovery Plan - Day 3:... - Day 5: Product locks the... - Day 10: Engineering completes the... - Day 15: QA passes critical... - Day 20: Ten customers enter... - Day 30: Review completion, time... Escalation Triggers - Billing policy remains... - Critical-path engineering capacity drops below... - Fewer than 7 of 10... - Any security issue blocks payment...