Activate when: user says 'this is taking too long', 'everyone else is doing X', 'should we take the easier path', 'is this worth it', 'we need to build a moat', 'choosing which capability to invest in long-term', or 'should we persist or pivot on this hard path'. Do NOT activate when: the path is only hard but not value-building (sunk-cost rationalization), or when the vindication horizon exceeds the organization's survival window. More: deciqai.com/s/narrow-gate-strategy
Scanned 9/3/2026
Install to Claude Code
npx -y skills add deciqAI/knowledge-skills --skill narrow-gate-strategy --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Narrow Gate Strategy?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/deciqai-narrow-gate-strategy)More formats (shields.io, HTML) on the badges page.
---
name: narrow-gate-strategy
description: "Activate when: user says 'this is taking too long', 'everyone else is doing X', 'should we take the easier path', 'is this worth it', 'we need to build a moat', 'choosing which capability to invest in long-term', or 'should we persist or pivot on this hard path'. Do NOT activate when: the path is only hard but not value-building (sunk-cost rationalization), or when the vindication horizon exceeds the organization's survival window. More: deciqai.com/s/narrow-gate-strategy"
---
# Narrow Gate Strategy
## Overview
The narrow gate is the path that is genuinely difficult, genuinely right, and genuinely compounding — avoided by most who prefer immediate legibility over long-term leverage. Three simultaneous conditions: (1) hard enough to deter most, (2) right — builds durable value not just scar tissue, (3) compounds — each phase creates conditions for the next to generate disproportionate returns.
Composes with **[second-order-thinking]** (map long-game consequences before choosing), **[margin-of-safety]** (prevent overextension in lean phases), and **[okr-goal-setting]** (orient goals toward phase structure, not short-cycle legibility metrics).
## When to Use
- Choosing which capability, market, or technology to invest in over a multi-year horizon.
- Evaluating whether to persist or pivot when a hard path is showing slow early returns.
- Designing a moat-building strategy requiring patient accumulation rather than fast acquisition.
- Auditing whether current resource allocation is building durable advantage or appearing busy.
- When facing the temptation to "do what's working for everyone else."
**When NOT to use:** Path is hard but wrong (not a narrow gate). Vindication horizon exceeds survival window. Speed dominates compounding. "Narrow gate" is rationalizing sunk cost.
## Coaching Novices (Adaptive Front Door)
- **Engine mode:** user has a concrete case → run The Process directly.
- **Coach mode:** user unfamiliar or no concrete case → guide step by step.
In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.
1. **What it is:** Narrow Gate Strategy — choose the path that is hard, right, and compounding; build it phase by phase instead of the wide crowded path that looks easier but leads to mediocre outcomes.
2. **Check fit:** "Is there an 'obvious' move most people in your domain are making? What hard thing would very few attempt, and would it compound into structural advantage?"
3. **Elicit the real case:** "Describe both the wide gate and the narrow gate. What makes the narrow gate hard — and what makes it right?"
> **[WAIT — do not advance until user responds]**
4. **Run The Process one step at a time:** Map each of the four phases for their specific situation.
> **[WAIT — do not advance until user responds]**
5. **Close by naming the insight:** "What structural advantage would you have after all four phases that the wide gate could never produce? Name it."
> **[WAIT — do not advance until user responds]**
## The Process
**Output artifact:** Narrow Gate Map **Stop-rule:** If at Step 3 you cannot articulate the compounding mechanism, stop — a merely hard path is not a narrow gate.
1. **Identify the wide gate.** Name ≥2 obvious paths most participants are taking. Gate: described from genuine appeal, not straw man.
2. **Locate the narrow gate.** Specify hardness (time, skill, capital, ambiguity) AND rightness (durable value, structural advantage). Gate: hard AND right.
3. **Identify the compounding mechanism.** How does each phase's investment create conditions for the next's disproportionate return? Gate: chain is explicit.
4. **Map the four phases.** P1 Value Breakthrough (价值破局期): faint light (微光), narrow entry. P2 Resource Building (资源构建期): hidden spring (隐泉), fertile ground (沃土), dark path (暗路). P3 Potential Energy (势能积累期): long road (远路), collective wisdom (众智), thick momentum (厚势). P4 Endgame Breakthrough (终局突破期): long slope (长坡), forest-sea (林海). Gate: each phase has observable markers.
5. **Define phase-transition criteria.** Observable conditions for each transition — not time periods. Gate: testable.
6. **Assess survivability.** Can you reach Phase 3 before resources are exhausted? Gate: Phase 2 survivability confirmed.
### Output: Narrow Gate Map
```
Domain / Initiative: Date:
Wide Gate Options: 1.[Name: why wide] 2.[Name: why wide]
Narrow Gate — Description: / Hardness: / Rightness: / Compounding mechanism:
P1 Value Breakthrough: Faint light: / Entry: / Success marker:
P2 Resource Building: Hidden spring: / Fertile ground: / Dark path: / Success marker:
P3 Potential Energy: Long road: / Collective wisdom: / Thick momentum: / Success marker:
P4 Endgame Breakthrough: Long slope: / Forest-sea: / Endgame position:
Phase transitions: P1→P2: / P2→P3: / P3→P4:
Survivability: Min resource threshold P2: / Runway: / Survivable?:
```
*→ Method in Action: [The Wright Brothers and Controlled Flight (1899–1903)](examples/wright-brothers-and-controlled-flight-1899-1903.md)*
## Narrow Gate Packs
**Tech/Deep Tech:** Narrow gate = foundational capability (hardware, data, model) that takes 3–7 years, cannot be acquired off the shelf. **Brand/Consumer:** Narrow gate = community and trust built through earned relationships over years. **Research:** Narrow gate = methodological or data capability in underfunded area foundational for the next paradigm. **Career:** Narrow gate = rare skill combination not legible as valuable until context shifts.
## Applying It Well
1. Audit rightness separately from hardness — sunk cost is not compounding.
2. Pre-commit to phase-transition criteria before entering Phase 2 (the most dangerous phase).
3. Write the compounding mechanism in one paragraph before starting — if you can't, you have a hope, not a strategy.
4. The wide gate looks better in Phase 1 and Phase 2. That is the defining feature, not a bug.
5. 走暗路,行远路,战持久. Walk the dark path, travel the far road, fight the long battle.
6. Survivability through Phase 2 is a hard constraint. Set checkpoints at phase-transition criteria, not calendar intervals.
*→ Primary sources: [references/sources.md](references/sources.md)*
## Common Rationalizations
**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**
| Fake move | Reality |
|---|---|
| [D] "We're taking the narrow gate" without auditing rightness. | Hard AND right. Audit the compounding mechanism. |
| [D] "Everyone else is wrong" without specifying what they're missing. | Specify the structural advantage the narrow gate builds that the wide gate cannot. |
| [D] Treating Phase 2 slowness as evidence of a wrong path. | Phase 2 is designed to look slow. Check if phase-transition criteria are being met. |
| [D] "Long-term" framing to avoid phase-transition criteria. | Long-term is not a blank check — criteria make the path testable. |
| [D] "We've invested 3 years, so we must be right." | Sunk cost is not compounding. Have Phase 2 assets been built? |
| [D] "The market will eventually see the value" without a mechanism. | Specify Phase 4 endgame conditions and what triggers market recognition. |
| [D] Narrow gate in one domain, wide gate in supporting capabilities. | Mixed strategies produce neither speed nor compounding. |
| [D] "This is our moat" before Phase 3 momentum is visible. | Moats are Phase 4 outcomes, not Phase 1 declarations. |
| [D] Switching to wide gate in Phase 2 because competitors look strong. | Phase 2 is when wide gate competitors look strongest. Switching destroys accumulated investment. |
| [D] "We'll pivot to narrow gate once we have more resources." | Phase 1 is the cheapest entry point — it only gets more expensive. |
| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |
## Red Flags
- Narrow gate described aspirationally without specifying Phase 2 assets being accumulated.
- No phase-transition criteria — strategy described as "long-term" without testable milestones.
- Compounding mechanism absent or circular. Survivability through Phase 2 not assessed.
- Narrow gate framing applied retrospectively. Wide gate alternatives dismissed without genuine analysis.
- Phase 2 exited early due to external pressure, not met phase-transition criteria.
## Verification
- [ ] Wide gate alternatives described from genuine appeal, not straw men.
- [ ] Narrow gate has both hardness AND rightness — durable value specified.
- [ ] Compounding mechanism explicit: P1 unlocks P2 because [X]; P2 creates P3 because [Y].
- [ ] All four phases have observable success markers and testable phase-transition criteria.
- [ ] Survivability through Phase 2 assessed against current resource runway.
- [ ] Narrow Gate Map complete and reviewable by a third party. Stop-rule applied.
---
*Part of **deciqAI Knowledge Skills** — 237 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/s/narrow-gate-strategy** · Built by deciqAI · github.com/deciqAI · Contributions welcome.*
*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/narrow-gate-strategy.json*
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!