plan-blisted

# Plan B Framework ## When to Apply - After finalizing any Strategy Kernel (mandatory) - During periodic environmental scans - When early warning KPIs trigger - When buffer enters YELLOW or RED - When the founder is emotionally attached to a single plan ## Core Framework ### 6 Environmental Forces Monitor continuously. Any shift can invalidate the current strategy: | Force | What to Monitor | Trigger | |---|---|---| | **Technology** | Competitor launches, new tools, paradigm shifts | New direct competitor or substitute | | **Cost structure** | API costs, tool pricing, entry barriers | Unit economics change >20% | | **Customer needs** | Support themes, feature requests, win/loss | NPS drop >10 or new theme >30% of tickets | | **Target customer** | Cohort behavior, demographic changes | Best-retaining cohort shifts segment | | **Regulation** | Laws, compliance, industry rules | New regulation affecting operations | | **Social mood** | Sentiment, brand perception, trends | Sentiment spike or channel backlash | **Multi-force escalation:** 2+ forces shifting simultaneously = "Strategy revalidation recommended." ### Pre-Mortem (5-Step Process) 1. **Assume total failure:** "It is 6 months from now. This strategy has completely failed." 2. **Enumerate 3-5 specific failure causes** (concrete, not vague) 3. **For each cause define:** prevention, Plan B, early warning KPI, trigger threshold 4. **Rank by likelihood x impact** 5. **Embed triggers into monitoring** for automatic Pl