Framework
Pruning Trigger Template
TL;DR
Pre-defined criteria for when to prune a branch, established before branching begins.
Pre-defined criteria for when to prune a branch, established before branching begins. Prevents holding dead branches too long or pruning arbitrarily.
When to Use Pruning Trigger Template
Complete before launching any branch. Define success metrics, automatic triggers, escalation process, and responsible parties upfront.
How to Apply
1
Define Success Metrics
Set primary metric, secondary metric, and minimum viable threshold before launch
Questions to Ask
- What's the primary success metric (e.g., $500K ARR by month 12)?
- What's the secondary metric (e.g., 90% retention)?
- What's minimum viable threshold (below = automatic prune consideration)?
2
Set Automatic Pruning Triggers
Define specific conditions that automatically trigger prune evaluation
Questions to Ask
- Primary metric <50% of target at review?
- Secondary metric declining 3+ consecutive months?
- Branch consuming >25% resources without proportional return?
- Trunk weakening >10% due to branch resource drain?
- Customer retention <60% annually?
- Team attrition >40% annually?
3
Establish Escalation Process
Define yellow flag (1 trigger), red flag (2 triggers), and shutdown (3+ triggers) responses
Questions to Ask
- Yellow: 30-day recovery plan, 90-day improvement window?
- Red: Immediate review, 60-day improvement plan?
- Shutdown: Immediate prune, execute within 30-90 days?
4
Assign Responsible Parties
Define accountability for metrics, review, and final decisions
Questions to Ask
- Who is Branch Leader (accountable for metrics)?
- Who is Executive Sponsor (reviews monthly, owns escalation)?
- Who has Final Decision Authority (CEO/Board)?