Failure Essence

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 actions?"
  Interpretation A: "Enterprise, $100K+ deals"
  Interpretation B: "High-NPS users who generate referrals"
  -> DIVERGENT INTERPRETATION detected.

  "Define 'high-value' operationally:
   - What metric defines it?
   - What threshold?
   - What would PROVE this strategy is working?
   - What would PROVE it is failing?"

Applied to: Guiding Policy terms, Driver titles, Action descriptions. Any abstract concept that drives resource allocation.

The test: Can two reasonable people read this and derive opposite actions? If yes, the term is dangerously ambiguous.

3. Withdrawal Decision Protocol

Every Goal, Driver, and major Action created with PRE-COMMITTED stop conditions — defined at launch, not retroactively. Prevents the structural inability to stop.

WITHDRAWAL PROTOCOL (defined at creation):
  Stop Condition 1 (Quantitative):
     Strategy built on it -> Irreversible commitment -> Discovery too late

**Agent flags:** "2 load-bearing assumptions are unverified. Recommend verification before scaling decisions."

**Periodic re-audit:** Flag when load-bearing assumptions become stale or when decisions have scaled beyond the evidence base.

## Decision Rules

1. **Dual objectives require explicit primary/subordinate** — never allow two objectives to compete silently
2. **Ambiguity test on all strategy language** — if two people could derive opposite actions, clarify
3. **Stop conditions at creation** — not retroactively when judgment is compromised
4. **Biweekly re-presentation** — keep exit criteria visible even when not triggered
5. **Load-bearing assumptions must be verified** — or explicitly flagged as unverified risks
6. **Sample size matters** — n=5 is not enough to bet the company on

## Anti-Patterns to Detect

| Anti-Pattern | Signal | Response |
|---|---|---|
| Dual-objective silence | Two competing objectives, no explicit primary | "These objectives conflict under constraints. Which is primary?" |
| Strategic ambiguity | Key terms undefined operationally | "Could two people derive opposite actions from this? Define operationally." |
| No stop conditions | Goal created without withdrawal protocol | "Define stop conditions now. Not when sunk costs compromise judgment." |
| Assumption inflation | n=5 treated as proven fact | "Based on sample of 5. Need n=20+ before building strategy on this." |
| Stale assumptions | Load-bearing assumption >6 months old | "This assumption drives major decisions but is stale. Re-verify." |
| Withdrawal avoidance | Stop conditions triggered but ignored | "Pre-committed conditions are met. Present the decision: continue, pivot, or stop." |

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [masterleopold](https://github.com/masterleopold)
- **Source:** [masterleopold/anty-framework](https://github.com/masterleopold/anty-framework)
- **License:** MIT
- **Homepage:** https://4n7y.com

Install and usage instructions live in the source repository linked above.