The room asks again which loop owns the next move: Boyd’s OODA or Sun Tzu. Syllabi, ops playbooks, and startup decks already walk you into cycling faster so you can engage now. The question sounds like decision science. It is not. It is siege scorekeeping. The Army on the March does not ask who observes faster. It asks whether the signals say stop or advance, and whether contact can still stay last. You refuse faster as the default first.
“Who cycles faster” is already a siege
You did not invent this search. Pages that rank for Sun Tzu vs Boyd, OODA loop vs Art of War, or Boyd decision cycle already want a modern winner: who iterates faster, who fits MBA or ops talk. The more the title looks like a match, the more you are scoring speed against judgment.
So you can refuse the frame before you follow the playbook. “Who cycles faster” is already 攻城 — attacking the city. 行军篇 puts contact last. It is what you do only when the signals have already said advance, not when urgency renamed speed as resolve.
The Art of War is not a vote between two names. It is a sequence you can still use while the room argues about who closes the loop first.
You can also refuse the sport of ranking loops. Boyd vs Sun Tzu is a public comparison shape. It is not a required ops champion. The room wants a mascot for speed. You want a next cycle that did not open with unread signals. So you can leave the ranking to pages that sell a who-wins board. You keep the judgment from 行军.
In public discourse, Boyd’s Observe–Orient–Decide–Act is often read as: cycle faster and you win — so accelerate into contact. You do not invent briefings, page numbers, or fake quotes. You only name that public frame: faster treated as the default answer. This site’s founding direction is fewer unnecessary fights. What you stop today is swallowing that default whole.
Live judgment: read the signals first; contact last
The live judgment you use on this site is short. While moving, read the signals first. If they say stop, stop. Contact is the last step, not the first.
You read that judgment on Read the signals. The original lines stay there as evidence, not as decoration. Being already on the road is not the same as being ready to engage. Their movement is not the same as your duty to make contact now.
So you can refuse the ops dump that turns the comparison into “how to OODA-crush a rival.” Those details can stay elsewhere as background. Your job today is narrower: ask whether faster is already the default, and whether unread signals can still rewrite that default. Treating faster as the only entry is how urgency hides inside “must close the loop now.”
The step that makes you look fluent may only complete the room’s faster default. So you separate two facts: their push for a quicker cycle is not the same as your duty to raise contact now; a loud OODA comparison is not the same as your duty to lock the next cycle with speed. Refusing the default outranks looking like you read the board.
Rooms like to rename instant contact as resolve. Others already talk about the loop, so asking whether signals say stop 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 playbook requires a faster cycle, you already renamed a siege as fluency.
People will tell you that refusing faster is already a loss. The chapter does not protect your face for the next ten minutes. It protects the next cycle. Reading signals outranks looking decisive. If you hold the room by shouting cycle time 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 faster default
You name the object: the person, team, or system that must actually move in this comparison — not an abstract “who owns the decision cycle.” You name the goal: a result that makes the next cycle better, not “backed the faster school.” You name the resistance: the real block, not the deck title you dislike.
Then you ask one question. Can the signals still change your choice before contact? A written stop signal is a different option on the table: shrink the aim, move the window, verify one fact first, so nobody has to collide with incomplete signals. A changed relationship is who is in the conversation, what channel is assumed, and whether this has to be settled by accelerating into contact.
If either path exists, you do not need the faster default. You write three signals. You verify only whether one of them appears. Whole resolution outranks a win on cycle time.
Then you stop keeping score of who cycles faster. 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 faster means you are behind the ops course. The chapter does not say you never advance. It says contact is not the first step, and unread signals are what you refuse to treat as a license. If you skip reading signals because you want to look like you understand OODA, you chose the expensive road on purpose.
So you can keep the sequence without announcing it. Read signals, then ask stop or advance, then contact last. You do not owe the room a lecture on Boyd versus Sun Tzu. You owe the next cycle one fewer wasteful fight.
This site is not an aerial-attack encyclopedia, and it does not teach you how to crush a rival with a faster loop. The comparison exists only to serve fewer unnecessary fights. If you arrived looking for who wins Boyd vs Sun Tzu, or how to OODA-crush a competitor, this is the wrong door.
You can also keep this essay separate from the Army on the March signals piece, the Clausewitz decisive-battle piece, the Maneuvering preserve-before-race piece, the OpenAI-vs-Claude who-wins piece, and the Operations burn-and-speed essay. The signals piece owns chapter-9 judgment without a Boyd frame. Clausewitz refuses decisive battle as the default. Maneuvering owns preservation before you race for a prize. Who-wins refuses AI vendor scorekeeping. Operations owns burn and growth speed without Boyd. This piece owns refusing faster as the default before you treat OODA as a license to engage. Do not make chapter-only signals, decisive battle, preserve-before-race, vendor scorekeeping, or startup burn the main frame here.
Questions people ask after “Sun Tzu vs Boyd who cycles faster”
If I refuse to say who cycles faster while the playbook compares the two, will I look out of touch?
You might. The chapter does not protect your image in the next hour. It protects the next cycle. Reading signals outranks looking fluent. If you hold the room by shouting cycle time 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-the-faster-default.
MBA and ops pages center the OODA loop — must I learn how to cycle faster first?
No. Those pages usually sell the faster default. The Army on the March asks whether signals say stop before contact. So you can write the scene first: who the object is, what the goal is, where the resistance sits. If signals still say stop, you do not need faster as the opening. Leave “how to close the loop first” to outlines that want applause. Your job is to change the choice, not to award a speed race.
If public talk says Boyd’s loop means cycle faster to win, does naming him mean I joined the speed camp?
No. You name a public frame: faster treated as the default answer. You read it to see how that default walks you into contact before signals are complete, not to award an author. So you write which layer of default changes resistance for you. You do not write “who is stronger.” Reading a frame is not cheering a jersey. You also invent no fake quotes, briefings, or page numbers.
Does refusing faster as the default mean I am surrendering, so the room will think I dare not engage?
No. Refusing the default means writing object, goal, and resistance, and verifying only whether signals still say stop — instead of letting urgency walk you into contact now. So you can pull one layer of faster default back without a speech. If the other person only scores cycle time, you still do not join that scoreboard. What you protect is a next cycle you can still walk, not the engage label of this hour.
Is this the chapter-9 signals, Clausewitz, Maneuvering, AI who-wins, or burn-and-speed essay under a new title?
They differ. The signals piece owns chapter-9 judgment without Boyd. Clausewitz refuses decisive battle as the default. Maneuvering owns preserve before you race. Who-wins refuses AI vendor scorekeeping. Operations owns burn and growth speed without Boyd. This piece owns refusing faster as the default before you treat OODA as a license to engage. So today’s action for you is stopping that default and verifying signals — not rewriting those frames.
If I already named faster as the default in a meeting, how can I still use The Army on the March?
You still can. Refusing the default is not pretending you never said it. You name the crack: which step treated faster as the opening, and how the next cycle got locked. You write what next verifies: only whether signals still say stop or advance. You refuse a second deeper speed escalate from playbook pressure. Refuse-the-default still applies after a declaration. So you can halt the next forced contact. Open fewer unnecessary fights next.
Do I need to memorize Patterns of Conflict and all thirteen chapters before I have understood the comparison?
No. Those details are evidence elsewhere, not your faster checklist for today. The live judgment is: while moving, read the signals first; if they say stop, stop; contact is the last step, not the first. So you check whether faster is the default, whether that default can be rewritten, and whether object, goal, and resistance are written. Skipping signals while memorizing both manuals is encyclopedia reading, not judgment.
The next move is not a Boyd-vs-Sun-Tzu speed champion. You write three signals that can still change the choice before contact. If it fits, Contact Us — teaching, training, and content, not crushing a rival, and not winning a faster-loop class. We reply within two business days. You stop scoring the faster default. Let the next cycle open with one fewer wasteful fight.