Breaking The Line

---
name: breaking-the-line
description: Reject conventional approaches when they favor the entrenched opponent. Create chaos where your superior execution can prevail.
license: MIT
metadata:
  version: 1.0.3504
  author: sethmblack
repository: https://github.com/sethmblack/paks-skills
keywords:
- breaking-the-line
- structure
- writing
---

# Breaking the Line

Reject conventional approaches when they favor the entrenched opponent. Create chaos where your superior execution can prevail.

**Source Expert:** Horatio Nelson
**Category:** Strategy / Competitive Tactics

---

## When to Use

- Conventional approaches consistently favor the incumbent or larger competitor
- You have advantages that standard engagement cannot leverage
- The opponent expects a particular form of competition
- Playing by established rules leads to predictable defeat
- You need to create conditions where execution quality matters more than position

**Trigger Phrases:**
- "The conventional approach isn't working"
- "How do I disrupt the status quo?"
- "They have the advantage in a standard fight"
- "Playing by the rules means losing"
- "How do I change the game?"
- "We can't outspend them"

---

## Inputs

| Input | Required | Description |
|-------|----------|-------------|
| `situation` | Yes | The competitive context you face |
| `opponent_position` | Yes | How the opponent is arrayed; their strengths |
| `your_capabilities` | Yes | What you do better than them |
| `conventional_approach` | Yes | What traditional competition looks like |
| `why_conventional_fails` | Yes | Why playing by the rules leads to defeat |

---

## The Historical Context

At Trafalgar, Nelson faced a Franco-Spanish fleet with more ships and larger vessels. Traditional naval doctrine called for forming a parallel line of battle and trading broadsides. This approach would favor French ships with their larger crews and heavier guns.

Nelson rejected the convention entirely. Instead of forming a parallel line, he divided his fleet into two columns and drove perpendicular into the enemy line. The leading ships took terrible fire with no reply - but once they broke through, they could concentrate against fragments of the enemy fleet while the van sailed uselessly ahead, unable to turn in time to help.

The approach created chaos - a "pell-mell battle" where British gunnery, seamanship, and offensive spirit could prove decisive. What looked like tactical insanity was strategic genius: Nelson chose to fight the battle where his advantages mattered most.

The result: 22 of 33 enemy ships captured or destroyed; zero British ships lost.

---

## Workflow
### Step 1: 1. Map the Conventional Battlefield

Before you can break the line, you must understand it:

**The Expected Engagement:**
- How is competition normally conducted in this space?
- What are the "rules" everyone follows?
- What metrics define success in conventional terms?

**Who It Favors:**
- Why does conventional competition advantage the incumbent?
- What resources or positions do they have that matter in standard engagement?
- What can they do better than you in a conventional fight?

### Step 2: 2. Identify Your Unconventional Advantages

What do you have that doesn't matter in conventional competition but could be decisive in chaos?

- **Execution speed:** Can you iterate faster?
- **Quality at detail level:** Can you do specific things much better?
- **Agility:** Can you adapt faster to changing conditions?
- **Commitment:** Can you concentrate force where they cannot?
- **Unconventional assets:** What do you have that they dismiss?

### Step 3: 3. Find the Point of Penetration

Where can you break through their formation?

- **Gaps in coverage:** Where are they weak or absent?
- **Assumptions they don't question:** What do they believe that might be wrong?
- **Dependencies they trust:** What do they rely on that could be disrupted?
- **Timing vulnerabilities:** When are they unable to respond?

### Step 4: 4. Design the Unconventional Attack

Your approach must:

- **Accept initial costs:** The leading ships at Trafalgar took fire without reply; this was the price of breaking through
- **Create chaos they cannot manage:** Your attack should produce conditions where their size becomes liability
- **Position you for decisive advantage:** Once through the line, you must be able to concentrate force

**Key Questions:**
- What are you willing to sacrifice to achieve penetration?
- How will chaos benefit you more than them?
- What happens after you break through?

### Step 5: 5. Prepare for Pell-Mell

Once the line breaks, the battle becomes chaotic. You must be ready:

- **Your people must know your intent:** The Nelson Touch - shared understanding enables action in chaos
- **Superior execution matters:** Practice the fundamentals that will matter in close combat
- **Concentration of force:** Know where to direct effort once breakthrough occurs

### Step 6: 6. Commit Fully

Breaking the line is not a hedge. It's a decisive commitment that risks everything on unconventional victory.

- **No half-measures:** Partial commitment gets the costs without the benefits
- **Accept initial losses:** The leading ships will suffer; this is the price of breakthrough
- **Move with speed:** Hesitation allows the opponent to reform

---

## Outputs
```markdown
## Breaking the Line Analysis

### The Conventional Battlefield
**How competition normally works:** [Standard approach]
**Who it favors and why:** [Incumbent advantages]
**Why conventional means defeat:** [Your disadvantages in standard engagement]

### Your Unconventional Advantages
- [Advantage 1]: Why this matters in chaos
- [Advantage 2]: Why this matters in chaos
- [Advantage 3]: Why this matters in chaos

### The Point of Penetration
**Target:** [Where you'll break through]
**Why this works:** [Their vulnerability here]
**What you sacrifice to achieve it:** [Initial costs accepted]

### The Attack Design
**The Move:** [What you will actually do]
**Expected Initial Cost:** [What you'll suffer during penetration]
**Chaos Created:** [How this disrupts their formation]
**Your Advantage in Chaos:** [Why you win in pell-mell conditions]

### After the Breakthrough
**Where to concentrate force:** [Focus of post-penetration effort]
**What victory looks like:** [End state you're creating]

### Commitment Requirements
- [What must be sacrificed]
- [What cannot be hedged]
- [Speed required]

### Risks and Mitigations
| Risk | Probability | Mitigation |
|------|-------------|------------|
| [Risk 1] | [%] | [How to address] |
| [Risk 2] | [%] | [How to address] |
```

---

## Outputs

**Primary Output:** A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data.

**Format:**
```markdown
## Analysis: [Topic]

### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]

### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]
```

**Example output:** See the Example section below for a complete demonstration.

## Constraints

- Do not use this analysis as the sole basis for critical decisions
- Do not apply this framework to situations outside its intended scope
- Acknowledge that analysis is based on available data, which may be incomplete
- Honor the complexity of real-world situations that resist simple categorization
- Present findings with appropriate confidence levels
- Recognize the limits of the methodology

## Additional Notes

**Best practices:**
- Use this skill when the situation clearly matches its intended use cases
- Combine with related skills for comprehensive analysis
- Iterate on outputs if initial results don't fully meet requirements

**Common variations:**
- Adjust the depth of analysis based on available time and information
- Scale the approach for different levels of complexity
- Adapt the output format to audience needs

**When to skip this skill:**
- The situation doesn't match the core use cases
- Simpler approaches would be more appropriate
- Time constraints require faster methods

## Example

**Input:**
- Situation: Enterprise software startup competing with dominant incumbent
- Opponent position: Incumbent has 80% market share, massive sales team, deep customer relationships, comprehensive product
- Your capabilities: Faster development, better UX, modern architecture, passionate small team
- Conventional approach: Build feature parity, hire sales team, compete on traditional enterprise metrics
- Why conventional fails: They have 10x resources; feature-for-feature competition takes years; their sales team overwhelms ours

**Output:**

## Breaking the Line Analysis

### The Conventional Battlefield
**How competition normally works:** Build comprehensive product, hire enterprise sales team, compete for RFPs, match feature checklists, win deals through relationships and brand recognition.

**Who it favors and why:** Incumbent has 10x engineering resources, established customer relationships, brand trust, massive sales organization. They win enterprise deals on reliability and completeness.

**Why conventional means defeat:** We cannot build feature parity in less than 5 years. We cannot hire enough salespeople to match their coverage. Competing on their terms guarantees slow death.

### Your Unconventional Advantages
- **Development speed:** We ship in weeks what takes them quarters
- **UX quality:** Our product is actually enjoyable to use
- **Modern architecture:** We can integrate with tools they cannot
- **Focus:** We can obsess over one use case while they manage hundreds
- **Agility:** We can pivot based on customer feedback in days

### The Point of Penetration
**Target:** Developer-led adoption in cloud-native companies

**Why this works:** Their enterprise sales motion is irrelevant to companies that buy bottom-up. Their legacy architecture cannot integrate with modern developer toolchains. Their UX is designed for procurement, not users.

**What you sacrifice:** The traditional enterprise market (for now). Revenue from companies that require enterprise sales processes.

### The Attack Design
**The Move:** Build the best product for a specific developer workflow. Make it free to start, easy to adopt, delightful to use. Let developers pull us into organizations rather than pushing through procurement.

**Expected Initial Cost:** Lower initial deal sizes. Dismissed by enterprise analysts. Ignored by traditional buyers. Revenue growth looks smaller than VC-funded competitors doing enterprise sales.

**Chaos Created:** When their customers' developers prefer our tool, their enterprise sales process becomes liability. Their comprehensive product becomes bloat. Their relationships with IT become less relevant as developers gain influence.

**Your Advantage in Chaos:** In a pell-mell where developer preference determines adoption, our UX and speed win every engagement. Every day a developer uses us creates switching cost they cannot overcome with sales calls.

### After the Breakthrough
**Where to concentrate force:** Companies where developers have significant influence on tooling decisions; modern technology companies; teams within traditional enterprises that operate with more autonomy.

**What victory looks like:** Become the de facto choice for developers first, then expand to enterprise deals when companies want to standardize on what developers already use.

### Commitment Requirements
- Accept that enterprise analysts will dismiss us
- Do not hire enterprise sales team to hedge
- Ignore RFPs and procurement processes entirely
- Invest everything in product and developer experience
- Move faster than they can respond

### Risks and Mitigations
| Risk | Probability | Mitigation |
|------|-------------|------------|
| Developers don't have enough influence | 30% | Focus on companies where they demonstrably do |
| Incumbent copies our approach | 40% | Their architecture makes true copy impossible; their sales team fights bottom-up |
| We run out of runway before breakthrough | 25% | Keep costs low; revenue from developer adoption; may need to extend runway |

---

## Anti-Patterns

**DON'T:**
- Break the line without superior execution capability (chaos destroys the unprepared)
- Attempt half-measures (partial perpendicular attack gets maximum damage, minimum benefit)
- Confuse unconventional with undisciplined (Nelson's attack was precisely calculated)
- Expect initial costs to be zero (the leading ships took fire; accept this)
- Break the line without shared intent (chaos without coordination is just chaos)

**The Test:** If your unconventional approach doesn't scare you a little, it's probably not unconventional enough.

---

## Integration

This skill pairs with:
- **Nelson Touch Command:** Breaking the line requires even stronger shared intent - chaos demands coordination through understanding
- **Decisive Engagement:** Once through the line, seek total victory not partial advantage
- **Lightning Campaign (Caesar):** Speed after breakthrough is essential
- **Maneuver vs Attrition Assessment (Boyd):** Breaking the line is maneuver warfare thinking applied