failure-essencelisted

# Strategic Failure Patterns (Essence of Failure) ## When to Apply - Creating or reviewing Strategy Kernels - When Goals have multiple competing objectives - When strategy language is vague or ambiguous - When a project should potentially be stopped - When assumptions underlying strategy need validation ## Core Framework ### 1. Dual-Objective Trap Detection When a Goal or Driver has two stated objectives, run a conflict stress test: ``` Goal: "Acquire 100 enterprise customers AND maintain 90% gross margin" Conflict Stress Test: "Under what resource/timing constraints do these conflict?" -> Enterprise sales requires high-touch (high CAC) -> 90% margin limits sales investment -> Below $50K deal size, these are mutually exclusive "DUAL-OBJECTIVE CONFLICT detected. Under resource constraints, you cannot maximize both. Which is PRIMARY?" -> User designates primary; other becomes subordinate with floor. ``` **Applied to:** Goal creation, Driver creation, Strategy Kernel formulation. Any time two objectives appear in the same scope. **Resolution:** One objective is PRIMARY (maximized). The other becomes SUBORDINATE with a minimum acceptable floor (not zero, just not maximized). ### 2. Strategic Ambiguity Detection When Strategy Kernel or User Rules contain terms that could be interpreted divergently, test for operationalizability: ``` Guiding Policy: "Focus on high-value customers" Ambiguity Test: "Could two people read 'high-value' and derive opposite