Sabotage
Саботаж
Offense Takes Depth —
creates weaknesses in the opponent's structure
Moats it grows into
This takes; it does not hold. Breaking a rival buys a window, and a window is not a moat — the damage is repaired and the position reverts, and nothing about sabotaging gets deeper with your scale. It is a tactic, and usually an illegal one, not a defence. A moat appears only if you use the window the damage bought to dig something durable yourself; the sabotage never becomes the moat.
Summary
Sabotage wins by breaking the other side's ability to operate — you introduce faults into a rival's supply, infrastructure or code so it fails on its own. It takes ground while the damage lasts, but keeps nothing: the target repairs, hardens, and you have built no defence of your own. Often it is also illegal.
How it works
The mechanism is degradation of the other side rather than improvement of your own. You find a weak point in a rival's operation — a dependency, a process, a system — and damage it, so their product slows, breaks or loses trust without you having to compete on merit. For a window, demand shifts to you because the alternative stopped working.
The window is the whole story. Damage is temporary: the target patches the hole, adds redundancy, and often comes back more resilient than before. You have spent effort and risk to buy time, not to build anything that lasts, and if the sabotage is traced the legal and reputational cost can dwarf the gain. Nothing about the act deepens with your scale.
Do you have it
- A rival's outage or failure, not your own launch, is what moved demand to you.
- Your gains reverse as soon as the target repairs the weakness you exploited.
- The advantage rests on access to a fault you can trigger, not on your product.
- You are exposed to legal or reputational blowback if the act is traced back to you.
How to dig it
- Map the target's real dependencies before acting; a symbolic hit changes nothing.
- Aim at the single point of failure whose loss the rival cannot quickly route around.
- Have your own durable moat ready, so the window the damage buys is not wasted.
- Weigh the legal and reputational cost honestly; a traced attack usually costs more than it wins.
How it erodes
- The target patches the fault and adds redundancy, and the same attack no longer lands.
- The damage is traced to you, and the legal and reputational cost swamps the gain.
- A resilient rival recovers stronger, having hardened exactly where you struck.
- The window closes before you have dug any moat of your own to fill it.
Solo, without capital
There is almost nothing here for an honest solo builder. Sabotage means damaging someone else's operation, which is usually illegal and easy to trace back to a lone actor with no cover. Even where a legal grey area exists, the payoff is a temporary window, not a position a solo builder can keep. The realistic move this quarter is the inverse: harden your own single points of failure so a rival cannot do this to you.
In nature, in business
- Nature
- —
- Business
- Stuxnet, cutting undersea cables
Cases
- Stuxnet — A worm quietly made Iranian centrifuges spin themselves to destruction while reporting normal readings to operators.
- Uber — Reportedly ordered and cancelled thousands of Lyft rides to tie up rival drivers and degrade its service.
- NotPetya — Malware disguised as ransomware wiped the systems of firms like Maersk, a state sabotage tool aimed at an economy.
Combines with
- Espionage — You have to learn the target's real weak points before you can break the right one.
- Infiltration — Getting inside the target's systems or supply chain is what puts the fault within reach.
- Camouflage — Hiding the source of the damage is what keeps the legal and reputational cost off you.
Fights with
- Transparency — You cannot sabotage a rival and run open, visible operations at the same time.
- Neutrality — A saboteur cannot also be the trusted, non-belligerent safe choice a market relies on.