The room asks again whether war is locked in: disrupt or die — who breaks the category wins. MBA and tech pages already walk you into Christensen / innovator’s dilemma as the default reason to open a fight, and still score who killed whose product line. That sounds like innovation literacy. It is siege scorekeeping. Tactical Dispositions asks whether a “disrupt” path that still ends in category war you chose is still a fight. You refuse disrupt-or-die as default first.
“Disrupt or die” is already a siege
You did not invent this search. Pages that rank for disruptive innovation, innovator’s dilemma, disrupt or be disrupted, or who breaks the category already want a modern winner: who shatters the old line better, who fits MBA or tech talk. The more the title looks like mandatory war, the more you are scoring louder category war against judgment.
So you can refuse the frame before you follow the playbook. “Disrupt or die” is already 攻城 — attacking the city. 军形篇 asks you to make yourself hard to defeat first. You complete yourself before you race to break the other side; treating “must disrupt” as the default open is reversing that order.
The Art of War is not a vote between two innovation jerseys. It is a sequence you can still use while the room argues about who broke the category first.
You can also refuse the sport of ranking disruption fluency. Disruption vs Sun Tzu is a public comparison shape. It is not a required ops champion. The room wants a mascot for who-killed-the-old-category fluency. You want a next cycle that did not open with a category war you chose not to name. So you can leave the ranking to pages that sell a who-broke-the-category board. You keep the judgment from 军形.
In public discourse, Christensen, innovator’s dilemma, disrupt or die, and disrupt or be disrupted are often read as: disrupt or perish, break the category or lose, strike first and kill the old line — and still score victory by who killed whose product line or who owned the next wave. You do not invent quotes, page numbers, or Tactical Dispositions encyclopedia dumps. You only name that public frame: disrupt-or-die treated as the default reason to open a fight. This site’s founding direction is fewer unnecessary fights. What you stop today is swallowing that license whole.
Live judgment: Hard to defeat; treating disrupt-or-die as default war is still siege
The live judgment you use on this site is short. Make yourself hard to defeat first; only then talk about defeating others. Completing yourself outranks racing to break the other side.
You read that judgment on Hard to defeat. The original lines stay there as evidence, not as decoration. A fight you treated as “must disrupt,” if you still score who killed the old category, is still a category war you chose not to name — still 攻城 under an innovation label.
So you can refuse the strategy dump that turns the comparison into “how to disrupt incumbents” or a kill-your-product-line field manual. Those details can stay elsewhere as background. Your job today is narrower: ask whether disrupt-or-die-as-default is already a still-siege license, and whether plan and relationship can rewrite that license. Treating disrupt as the default open is how urgency hides inside “must break the category, just more advanced.”
The step that makes you look fluent may only complete the room’s disrupt-or-die. So you separate two facts: their push for a disruption scoreboard is not the same as your duty to open a category war now; a loud Disruption comparison is not the same as your duty to lock the next cycle with a category war you chose not to name. Refusing the license outranks looking like you read the board.
Rooms like to rename a chosen category war as innovation. Others already talk about disruption, so asking whether you are hard to defeat first looks slow. The chapter splits that rename. If the resolve is fewer unnecessary fights, a pause is not slow. If the resolve is only that the syllabus requires disrupt-or-die as default war, you already renamed a siege as fluency.
People will tell you that refusing disrupt-or-die as default is already a loss. The chapter does not protect your face for the next ten minutes. It protects the whole and the next cycle. Hard to defeat comes first. If you hold the room by shouting who breaks the category and skip object, goal, and resistance, the round was a small siege — already the opening of an unnecessary fight.
Write object, goal, resistance — then stop the disrupt-or-die license
You name the object: the person, team, or system that must actually move in this comparison — not an abstract “who owns the next disruption wave.” You name the goal: a result that makes the next cycle better, not “backed the disruption school.” You name the resistance: the real block, not the innovation slogan you dislike.
Then you ask one question. Can plan or relationship change your choice before the category war? A changed plan is a different option on the table: shrink the aim, move the window, verify one fact first, so nobody has to collide under a disruption scoreboard. A changed relationship is who is in the conversation, what channel is assumed, and whether this has to be settled by a category war you still chose not to name.
If either path exists, you do not need the disrupt-or-die license. You write one path. You verify only that condition. Being hard to defeat outranks a win on disruption fluency.
Then you stop keeping score of who killed the old category. Your review is three sentences: the judgment, what you verified, what would make the next cycle better. If you skipped siege-style side-taking, the review is shorter. That is the point.
People will tell you that refusing disrupt-or-die as default means you are behind the innovation course. The chapter does not say you never move. It says make yourself complete and hard to defeat first; breaking the other side is not the opening default. If you skip hard-to-defeat because you want to look like you understand disruption talk, you chose the expensive road on purpose.
So you can keep the sequence without announcing it. Hard to defeat first, then break. You do not owe the room a lecture on Disruption versus Sun Tzu. You owe the next cycle one fewer wasteful fight.
This site is not a disruptive-innovation encyclopedia, and it does not teach you how to disrupt incumbents or kill your own product lines. The comparison exists only to serve fewer unnecessary fights. If you arrived looking for who breaks the category or how to force disrupt-or-die as the default win, this is the wrong door.
You can also keep this essay separate from the junxing-hard-to-defeat piece, the Boyd refuse-faster-as-default piece, the blue-ocean refuse-whitespace-as-still-siege piece, the junzheng preserve-before-you-race piece, the never-surrender refuse-no-stop-date piece, the bingshi-spend-fewer piece, the Liddell Hart refuse-indirect-as-still-siege piece, and the refuse-useless-strife pages. Junxing owns chapter 军形 “hard to defeat” judgment without a Christensen / disrupt-or-die frame. Boyd refuses faster OODA as default. Blue ocean refuses whitespace as default escape. Junzheng owns preserve before you race, not a disruption slogan. Never-surrender refuses no-stop-date. Bingshi owns spend fewer. Liddell Hart refuses indirect route as still siege. Refuse-useless-strife is general fewer fights without a disruption frame. This piece owns refusing disrupt-or-die as default before you treat disruption as a license for an unnamed category war. Do not make chapter-only 不可胜, faster-as-default, whitespace escape, preserve-before-race, no-stop-date, spend-fewer, indirect-as-still-siege, or general refuse strife the main frame here.
Questions people ask after “disruptive innovation disrupt or die Sun Tzu”
If I ask whether I am hard to defeat while the syllabus cites disrupt or die, will I look out of touch?
You might. The chapter does not protect your image in the next hour. It protects the whole. Hard to defeat comes first. If you hold the room by shouting who breaks the category and skip object, goal, and resistance, the round was a small siege. So you can let the comparison’s score go. You write what would make the next cycle better. Completeness outranks looking fluent. Fluency is not follow-disrupt-or-die-as-default.
MBA and tech pages center innovator’s dilemma — must I learn how to disrupt incumbents first?
No. Those pages usually sell break-the-category as smarter war that still scores who killed the old line. Tactical Dispositions asks whether you are hard to defeat before you race to break. So you write the scene first: who the object is, what the goal is, where the resistance sits. If plan or relationship can change, you do not need disrupt-or-die as the opening. Leave “how to disrupt incumbents” to outlines that want applause. Your job is to change the choice.
If public talk says disruption means break the category to win, does naming Christensen mean I joined the still-open-war camp?
No. You name a public frame: disruptive innovation and innovator’s dilemma often read as disrupt or die, break the category or lose, still score who killed the product line. You read it to see how that frame walks you into a category war you chose not to name, not to award an author. So you write which layer of “must disrupt” still ends in siege. You do not write “who broke first.” Reading a frame is not cheering a jersey.
Does refusing disrupt-or-die as default mean I am surrendering, so the room will think I dare not innovate?
No. Refusing the license means writing object, goal, and resistance, and verifying only whether plan and relationship can still change the choice — instead of letting “must break the category” walk you into a forced category war. So you can pull one layer of disrupt-or-die back without a speech. If the other person only scores who killed the old line, you still do not join that board. What you protect is a next cycle you can still walk.
Is this the junxing, Boyd, blue-ocean, junzheng, never-surrender, bingshi, Liddell Hart, or refuse-useless-strife essay under a new title?
They differ. Junxing owns chapter 军形 hard-to-defeat judgment without a disrupt-or-die frame. Boyd refuses faster as default. Blue ocean refuses whitespace as default escape. Junzheng owns preserve before race. Never-surrender refuses no-stop-date. Bingshi owns spend fewer. Liddell Hart refuses indirect as still siege. Refuse-useless-strife is general fewer fights without that frame. This piece owns refusing disrupt-or-die as default before you treat disruption as license. So today’s action for you is stopping that license and verifying hard to defeat.
If I already named disrupt-or-die as the default open in a meeting, how can I still use Tactical Dispositions?
You still can. Refusing the license is not pretending you never said it. You name the crack: which step treated disruption as default war, and how the next cycle got locked. You write what next verifies: only whether plan and relationship can still change the choice before the category war. Refuse-disrupt-or-die-as-default still applies after a declaration. So you can halt the next forced break-the-category escalate. Open fewer unnecessary fights next.
Do I need to memorize innovator’s dilemma and all thirteen chapters before I have understood the comparison?
No. Those details are evidence elsewhere, not your disruption checklist for today. The live judgment is: make yourself hard to defeat first; completing yourself outranks racing to break the other side. So you check whether “disrupt or die” is still the default open you chose, whether that license can be rewritten, and whether object, goal, and resistance are written. Skipping hard-to-defeat while memorizing both manuals is encyclopedia reading, not judgment.
The next move is not a Disruption-vs-Sun-Tzu break-the-category champion. You write one path that changes the choice before the category war. If it fits, Contact Us — teaching, training, and content, not crushing a rival, and not winning a disruption class. We reply within two business days. You stop scoring disrupt-or-die as default. Let the next cycle open with one fewer wasteful fight.