Momentum and Form

Activate when: user says 'we have a better product but we're losing,' 'they're growing despite less funding,' 'our moat isn't protecting us,' 'the market shifted under us,' 'we just need to hire harder,' or is diagnosing why strong incumbents lose to weaker newcomers, evaluating a market entry, or asking whether a strategy depends too much on specific people. Do NOT activate when: the decision is purely tactical (not strategic), or the context is cooperative/ethical leadership where 'winning configurationally' is the wrong frame.

Overview

Competitive advantage is two distinct things, not one: form (形, xíng) — the structural stock built before any contest (capital, distribution, brand, product, org capability) — and momentum (势, shì) — the configurational force that converts form into outcome (timing, terrain, market direction). Most strategic failures trace to conflating them. Composed from Sun Tzu's Art of War, Chapters 4–5, c. 5th century BCE.

Composes with signaling-games, feedback-loops, s-curve-technology-adoption, and inversion.

When to Use

• Strong form but losing share to a less-capitalized competitor
• Growth momentum but limited structural assets — extend momentum or build form?
• Evaluating a new venture or market entry for form-momentum fit
• Strategy discussion reduces to a single "moat" question
• Proposed strategy depends on heroic individual performance
• Someone says: "we have the better product, why aren't we winning?" / "they're growing despite less capital" / "we should hire harder"

When NOT to use: regulated industry where form is decisive and momentum is uniform; purely tactical decision; cooperative/ethical context where "winning configurationally" is the wrong frame.

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: competitive advantage has two layers — what you've built (form) and how the configuration is working in your favor right now (momentum). Most strategic failures mistake one for the other.
2. Check fit against When to Use / When NOT to use. Uniform-momentum or tactical? Point elsewhere.
3. Elicit the real situation — a concrete competitive case. Don't run on hypotheticals.

[WAIT — do not advance until user responds]

4. Run The Process one layer at a time: form first, then momentum, then the gap.

[WAIT — do not advance until user responds]

5. Close by naming the configurational fix; explicitly reject "work harder" as the move.

[WAIT — do not advance until user responds]

The Process

Run the Form-Momentum Diagnosis. Separate the two layers; locate the imbalance; design the configurational fix.

1. Inventory the form. Capital, distribution, brand, product, customers, org capability, IP. What can't competitors easily replicate? Be specific.
2. Inventory competitor form. Same dimensions, honestly. Can't articulate it? Analysis is incomplete.
3. Map the momentum. Prevailing direction: demand shift, technology change, regulatory direction, capital flow. Classify: Tailwind / Headwind / Cross-current.
4. Diagnose the combination. High form + tailwind: defend and consolidate. High form + headwind: legacy-incumbent trap — reposition before form erodes. Low form + tailwind: race to convert momentum into form. Low form + headwind: withdraw or pivot.
5. Test against the shì diagnostic. Does the strategy win by configuration or heroic individuals? If heroic, find the configurational fix — not better people.
6. Identify the configurational fix. Change terrain, timing, or channel; build the missing form component; decouple from permanent headwinds.
7. Plan form-building under momentum. Every quarter of momentum converts into form (cash, brand, distribution, lock-in). Momentum without form-building is a story, not a strategy.

Output: Form-Momentum Diagnosis

text

Our form: [capital / distribution / brand / product / customers / org capability / IP]
Competitor form: [same dimensions, honest]
Momentum: [prevailing direction] → Tailwind / Headwind / Cross-current
Combination: [high/low form × tailwind/headwind/cross-current]
Diagnosis: [where the imbalance is; configuration win or heroic-individual win?]
Configurational fix: [specific change] | Stop: [heroic approach rejected] | Build: [form to build now]
Falsifier: [what would tell you this diagnosis is wrong]

→ Method in Action: Sun Tzu's Art of War, Chapters 4–5

Pack: Form-Momentum Patterns in Business

• Legacy-incumbent trap (high form + headwind): Kodak, Blockbuster, IBM mainframes. Fix: reposition form before it erodes.
• Startup-on-momentum (low form + tailwind): early Zoom 2020, early Stripe. Fix: convert momentum into form each quarter.
• Configurational moat (high form + tailwind): Google, Amazon, TSMC. Fix: extend platform density.
• Heroic-individual dependency: strategy works only with 3 specific salespeople. Fix: redesign the configuration.
• Wrong-terrain competition: premium product in price-sensitive segment. Fix: change terrain, not form.
• Platform-shift: mainframe→PC→web→mobile→cloud→AI. Fix: identify which form transfers and which becomes obsolete.

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Fake move	Reality
[D] "We just need to work harder / hire harder"	势 test: if it requires heroic effort, the configuration is wrong. Find configuration that carries the work.
[D] Treating form and momentum as a single thing	High form + adverse momentum → reposition. Low form + favorable momentum → build form. Opposite actions.
[D] "Our moat is so strong nothing can hurt us"	Form without momentum loses. The legacy-incumbent trap is real form + silently shifted momentum.
[D] Riding momentum without building form	When configuration shifts (and it always shifts), you collapse. Convert each quarter.
[D] Treating Sun Tzu as generic inspiration	Specific analytical claim about two layers of advantage and the consequences of mismatch — not a poetic resource.
[D] Confusing 势 with "luck"	Momentum is configurational, not random. Work on configuration.
[D] Confusing form-priority with "be cautious"	Build non-defeat first; then act on vulnerability decisively.
[D] Using military analogies to romanticize aggression	Sun Tzu is skeptical of fighting. The analogy is to configuration, not aggression.
[D] Applying this where "winning" is the wrong frame	Cooperative/ethical contexts are not 势 contexts.
[D] "We have momentum, that's enough"	Momentum without form is a story. Build the stock before configuration shifts.

→ Add [O] entries here after each real use — paste the actual failure pattern | What went wrong and why

Red Flags

• Strategic plan does not separately analyze form and momentum
• "Hire more / find a 10x engineer" proposed as the fix for what is actually a configurational mismatch
• Strong form losing share to a less-capitalized competitor with no acknowledgment that momentum has shifted
• Strong growth momentum and no plan for converting it into durable form in the next 12 months
• "We just need to execute better" as the diagnosis for a configurational mismatch

Verification

• Form inventoried specifically (capital, distribution, brand, product, customers, org capability, IP) — not vaguely
• Competitor form inventoried with equal specificity, honestly
• Momentum identified with evidence; classified as tailwind/headwind/cross-current
• Strategy tested against shì diagnostic: configuration win or heroic-individual win?
• If heroic individuals required, a configurational alternative has been considered
• If high form + adverse momentum, a repositioning plan exists (not "extend form further")
• Observable falsifier named — what would tell you the diagnosis is wrong?

---

Part of deciqAI Knowledge Skills — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.