The room asks again whether war is locked in: fail fast — who ran more experiments wins. Product and VC pages already walk you into Eric Ries / Lean Startup as the default reason to open a fight, and still score who pivoted faster. That sounds like validated learning. It is siege scorekeeping. Waging War asks whether a “learning” path that still ends in experiment-war you chose is still a fight. You refuse fail-fast as default first.
“Fail fast” is already a siege
You did not invent this search. Pages that rank for lean startup, fail fast, validated learning, Eric Ries, or who pivots to product-market fit already want a modern winner: who burns experiments for speed better, who fits startup talk. The more the title looks like mandatory war, the more you are scoring louder experiment-war against judgment.
So you can refuse the frame before you follow the playbook. “Fail fast” is already 攻城 — attacking the city. 作战篇 asks you to set a stop date first. Consumption itself is harm; count whether you can afford it, then set a stop date. Treating “must fail fast” as the default open is reversing that order.
The Art of War is not a vote between two startup jerseys. It is a sequence you can still use while the room argues about who pivoted more.
You can also refuse the sport of ranking experiment fluency. Lean Startup vs Sun Tzu is a public comparison shape. It is not a required ops champion. The room wants a mascot for who-ran-more-experiments fluency. You want a next cycle that did not open with an experiment-war you chose not to name. So you can leave the ranking to pages that sell a who-pivoted-faster board. You keep the judgment from 作战.
In public discourse, Eric Ries, Lean Startup, fail fast, validated learning, and pivot are often read as: fail fast, validated learning, pivot until you win — and still score victory by who ran more experiments or who pivoted to fit first. You do not invent quotes, page numbers, or Waging War encyclopedia dumps. You only name that public frame: fail-fast 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: Stop date; treating fail-fast as default war is still siege
The live judgment you use on this site is short. Consumption itself is harm. Count whether you can afford it, then set a stop date. A long campaign leaves both sides worse.
You read that judgment on Stop date. The original lines stay there as evidence, not as decoration. A fight you treated as “must fail fast,” if you still score who ran more experiments, is still an experiment-war you chose not to name — still 攻城 under a startup label.
So you can refuse the strategy dump that turns the comparison into “how to fail fast” or an experiment field manual. Those details can stay elsewhere as background. Your job today is narrower: ask whether fail-fast-as-default is already a still-siege license, and whether plan and relationship can rewrite that license. Treating fail-fast as the default open is how urgency hides inside “must pivot first, just more advanced.”
The step that makes you look fluent may only complete the room’s fail-fast. So you separate two facts: their push for an experiment scoreboard is not the same as your duty to open an experiment-war now; a loud Lean Startup comparison is not the same as your duty to lock the next cycle with an experiment-war you chose not to name. Refusing the license outranks looking like you read the board.
Rooms like to rename a chosen experiment-war as learning. Others already talk about Lean Startup, so asking stop date 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 fail-fast as default war, you already renamed a siege as fluency.
People will tell you that refusing fail-fast 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. Stop date comes first. If you hold the room by shouting who pivoted more 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 fail-fast license
You name the object: the person, team, or system that must actually move in this comparison — not an abstract “who owns the next validation wave.” You name the goal: a result that makes the next cycle better, not “backed the experiment school.” You name the resistance: the real block, not the startup slogan you dislike.
Then you ask one question. Can plan or relationship change your choice before the experiment-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 an experiment scoreboard. A changed relationship is who is in the conversation, what channel is assumed, and whether this has to be settled by an experiment-war you still chose not to name.
If either path exists, you do not need the fail-fast license. You write one path. You verify only that condition. Stop date outranks a win on experiment fluency.
Then you stop keeping score of who ran more experiments. 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 fail-fast as default means you are behind the product course. The chapter does not say you never move. It says consumption itself is harm; set a stop date first. If you skip stop-date because you want to look like you understand Lean Startup talk, you chose the expensive road on purpose.
So you can keep the sequence without announcing it. Stop date first, then spend. You do not owe the room a lecture on Lean Startup versus Sun Tzu. You owe the next cycle one fewer wasteful fight.
This site is not a Lean Startup encyclopedia, and it does not teach you how to draw a lean canvas, run experiments, or score who pivoted more. The comparison exists only to serve fewer unnecessary fights. If you arrived looking for who pivoted faster or how to force fail-fast as the default win, this is the wrong door.
You can also keep this essay separate from the zuozhan write-the-stop-date piece, the waging-war economics-and-speed piece, the blitzscaling refuse-scale-at-all-costs piece, the disruption refuse-disrupt-or-die piece, the Boyd refuse-faster-as-default piece, the never-surrender refuse-no-stop-date piece, the junzheng preserve-before-you-race piece, and the refuse-useless-strife pages. Zuozhan owns chapter 作战 “stop date” judgment without a Lean / Ries / fail-fast frame. Waging-war owns consumption, cost, stop-loss / startup-speed in general, not a fail-fast frame. Blitzscaling refuses scale-at-all-costs as default. Disruption refuses disrupt-or-die as default. Boyd refuses faster OODA as default. Never-surrender refuses no-stop-date. Junzheng owns preserve before you race, not a fail-fast loop slogan. Refuse-useless-strife is general fewer fights without a Lean frame. This piece owns refusing fail-fast as default before you treat Lean Startup as a license for an unnamed experiment-war. Do not make chapter-only 止损, general speed-economics, scale-at-all-costs, disrupt-or-die, faster-as-default, no-stop-date, preserve-before-race, or general refuse strife the main frame here.
Questions people ask after “lean startup fail fast Sun Tzu”
If I ask stop date while the syllabus cites fail fast, will I look out of touch?
You might. The chapter does not protect your image in the next hour. It protects the whole. Stop date comes first. If you hold the room by shouting who pivoted more 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. Stop date outranks looking fluent. Fluency is not follow-fail-fast-as-default.
Product and VC pages center Lean Startup — must I learn how to run experiments and draw a lean canvas first?
No. Those pages usually sell fail-fast as smarter war that still scores who ran more experiments. Waging War asks stop date before you spend the force. 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 fail-fast as the opening. Leave “how to fail fast” to outlines that want applause. Your job is to change the choice.
If public talk says fail fast means pivot until you win, does naming Ries mean I joined the still-open-war camp?
No. You name a public frame: Lean Startup and fail fast often read as fail fast, validated learning, pivot until win, still score who ran more experiments. You read it to see how that frame walks you into an experiment-war you chose not to name, not to award an author. So you write which layer of “must fail fast” still ends in siege. You do not write “who pivoted more.” Reading a frame is not cheering a jersey.
Does refusing fail-fast as default mean I am surrendering, so the room will think I dare not validate?
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 fail fast” walk you into a forced experiment-war. So you can pull one layer of fail-fast back without a speech. If the other person only scores who ran more experiments, you still do not join that board. What you protect is a next cycle you can still walk.
Is this the zuozhan, waging-war, blitzscaling, disruption, Boyd, never-surrender, junzheng, or refuse-useless-strife essay under a new title?
They differ. Zuozhan owns chapter 作战 stop-date without a Lean frame. Waging-war owns consumption and speed in general. Blitzscaling refuses scale-at-all-costs. Disruption refuses disrupt-or-die. Boyd refuses faster as default. Never-surrender refuses no-stop-date. Junzheng owns preserve before race. Refuse-useless-strife is general fewer fights without that frame. This piece owns refusing fail-fast as default before Lean as license. So you stop that license today and verify stop date.
If I already named fail-fast as the default open in a meeting, how can I still use Waging War?
You still can. Refusing the license is not pretending you never said it. You name the crack: which step treated fail-fast 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 experiment-war. Refuse-fail-fast-as-default still applies after a declaration. So you can halt the next forced experiment escalate. Open fewer unnecessary fights next.
Do I need to memorize Lean Startup and all thirteen chapters before I have understood the comparison?
No. Those details are evidence elsewhere, not your experiment checklist for today. The live judgment is: consumption itself is harm; count whether you can afford it, then set a stop date. So you check whether “fail fast” is still the default open you chose, whether that license can be rewritten, and whether object, goal, and resistance are written. Skipping stop-date while memorizing both manuals is encyclopedia reading, not judgment.
The next move is not a Lean-Startup-vs-Sun-Tzu experiment champion. You write one path that changes the choice before the experiment-war. If it fits, Contact Us — teaching, training, and content, not crushing a rival, and not winning a startup class. We reply within two business days. You stop scoring fail-fast as default. Let the next cycle open with one fewer wasteful fight.