The room asks again whether you should add force: the flywheel is turning, and whoever pushes again should win. Growth pages walk you into a Jim Collins and Amazon keep-pushing frame as the default reason to open or continue a fight, and still score who spins harder. That sounds like momentum. It is siege scorekeeping. Energy asks whether that path still ends in a fight you chose. You refuse momentum as still siege first.
“Keep pushing” is already a siege
You did not invent this search. Pages that rank for flywheel effect, Jim Collins, Amazon flywheel, or who must never ease off already want a modern winner: who keeps adding force, who fits growth talk. The more the title looks like a mandatory push, the more you are scoring louder momentum-war against judgment.
So you can set the license down before you follow the playbook. “Keep pushing” is already 攻城 — attacking the city. 兵势 asks you to spend fewer first. Momentum exists to shorten the fight and spend fewer people, not to hand you a pass because the wheel is already turning. Treating “it is spinning, so push again” as the default open reverses that order.
The Art of War is not a vote between two flywheel jerseys. It is a sequence you can still use while the room argues about who pushed longer.
You can also refuse the sport of ranking spin speed. Flywheel vs Sun Tzu is a public comparison shape. It is not a required growth champion. The room wants a mascot for who-spins-faster. You want a next cycle that did not open with a force-add you chose not to name. So you can leave the ranking to pages that sell a who-pushed-harder board. You keep the judgment from 兵势.
In public talk, Jim Collins’s flywheel and the loop an Amazon shareholder letter calls a flywheel are often read as keep pushing: the wheel turns faster, so you push harder. You do not invent quotes, page numbers, or an Energy encyclopedia. You only name that public frame: faster-means-add-force treated as the default reason to open or continue a fight. This site’s founding direction is fewer unnecessary fights. What you stop today is swallowing that license whole.
Live judgment: Spend fewer; treating momentum as default war is still siege
The live judgment you use on this site is short. Use momentum to shorten conflict and spend fewer people. Ordinary force is enough when timing and coordination line up — you do not need more destruction.
You leave the original lines on the Energy page as evidence, not as decoration. A fight you treated as keep-pushing because the wheel is already turning, if you still score who pushed harder, is still a force-add you chose not to name — still 攻城 under a flywheel label. The page also asks you: Once combined, do the forces point toward less waste, or more escalation?
So you can refuse the strategy dump that turns the comparison into “how to draw a flywheel” or a growth-loop field manual. Those details can stay elsewhere as background. Your job today is narrower: ask whether keep-pushing-as-default is already a still-siege license, and whether plan and relationship can change the choice before you add force. Treating spin speed as the default open is how urgency hides inside “the wheel is already turning, just one more push.”
The push that makes you look fluent may only add the room’s force for them. So you separate two facts: their push for a flywheel scoreboard is not the same as your duty to open a momentum-war now; a loud flywheel comparison is not the same as your duty to lock the next cycle with a force-add you chose not to name. Refusing the license outranks looking like you read the board.
Rooms like to rename a chosen force-add as momentum. Others already talk about the flywheel, so asking spend-fewer 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 keep-pushing as default war, you already renamed a siege as fluency.
People will tell you that letting the wheel slow is already a loss. The chapter does not protect your face for the next ten minutes. It protects the whole and the next cycle. Spend fewer comes first. If you hold the room by shouting who pushed harder 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 keep-pushing license
You name the object: the person, team, or system that must actually move in this comparison — not an abstract “who owns the next spin.” You name the goal: a result that makes the next cycle better, not “backed the keep-pushing school.” You name the resistance: the real block, not the flywheel slogan you dislike.
Then you ask one question. Can plan or relationship change your choice before you add more force? A changed plan is a different option on the table: shrink the scope, move the window, verify one fact first, so nobody has to collide under a spin-speed scoreboard. A changed relationship is who is in the conversation, what channel is assumed, and whether this has to be settled by a force-add you still chose not to name.
If either path exists, you do not need the keep-pushing license. You write one path. You verify only that condition. Spend fewer outranks a win on spin speed.
Then you stop keeping score of who pushed harder. 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 keep-pushing means you are behind the growth course. The chapter does not say you never move. It says use momentum to shorten conflict and spend fewer people. If you skip spend-fewer because you want to look like you understand flywheel talk, you chose the expensive road on purpose.
So you can keep the sequence without announcing it. Ask whether the force points toward less waste or more escalation, then decide whether to commit it. You do not owe the room a lecture on flywheel versus Sun Tzu. You owe the next cycle one fewer wasteful fight.
This site is not a flywheel encyclopedia, and it does not teach you how to draw a flywheel, design a growth loop, or score who spins faster. The comparison exists only to serve fewer unnecessary fights. If you arrived looking for who pushed harder or how to force keep-pushing as the default win, this is the wrong door.
You can also keep this essay separate from the bingshi spend-fewer piece, the blitzscaling refuse-scale-at-all-costs piece, the lean-startup refuse-fail-fast piece, the north-star refuse-one-number piece, the OKR refuse-stretch-cascade piece, the never-surrender refuse-no-stop-date piece, and the Boyd OODA refuse-faster-decision-loop piece. Bingshi owns the spend-fewer judgment itself, with no Flywheel, Collins, or Amazon slogan frame. Blitzscaling refuses scale-at-all-costs as default. Lean refuses fail-fast as the default open. North star refuses one number. OKR refuses stretch-goal cascade. Never-surrender refuses having no stop date. Boyd refuses faster decision loops; your subject here is accumulated momentum, keep pushing because the wheel is already turning. This piece owns refusing that momentum frame as the default reason to open or continue a fight, before you treat a spinning wheel as a license for an unnamed force-add. Do not make chapter-only bingshi, scale-at-all-costs, fail-fast, one number, stretch cascade, no stop date, or faster loops the main frame here.
Questions people ask after “flywheel Sun Tzu”
If I ask spend-fewer while the syllabus says keep pushing the flywheel, will I look afraid to add force?
You might. The chapter does not protect your image in the next hour. It protects the whole. Spend fewer comes first. If you hold the room by shouting who pushed harder 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. Spend fewer outranks looking fluent. Fluency is not follow-keep-pushing-as-default.
Growth pages center the flywheel — must I learn how to draw one and design a growth loop first?
No. Those pages usually sell keep-pushing as momentum-shaped war that still scores who spun harder. Energy asks you to spend fewer first. So you write the scene first: who the object is, what the goal is, where the resistance sits. If plan or relationship can change your choice, you do not need keep-pushing as the opening. Leave “how to draw a flywheel” to outlines that want applause. Your job is to change the choice, not to award a louder siege.
If public talk says a faster wheel means add more force, does naming Collins or the Amazon flywheel mean I joined the still-open-war camp?
No. You name a public frame: Collins’s flywheel and the Amazon shareholder letter’s flywheel are often read as keep pushing, the wheel turns faster so you push harder. You read it to see how that frame walks you into a force-add you chose not to name, not to award anyone. So you write which “must push again” layer still ends in siege. You do not write who spun faster. Reading a frame is not cheering a jersey.
Does refusing keep-pushing as default mean I am surrendering, so the room will think I stopped the wheel?
No. Refusing the license means writing object, goal, and resistance, and verifying only whether plan and relationship can still change your choice before you add force — instead of letting “the wheel is turning, so push again” walk you into a forced momentum-war. So you can pull one keep-pushing layer back without a speech. If they only score who pushed harder, you still do not join that board. What you protect is a next cycle you can still walk.
Is this the bingshi, blitzscaling, lean, north-star, OKR, never-surrender, or Boyd essay under a new title?
They differ. Bingshi owns spend-fewer without a flywheel slogan. Blitzscaling refuses scale-at-all-costs. Lean refuses fail-fast as default. North star refuses one number. OKR refuses stretch-goal cascade. Never-surrender refuses no stop date. Boyd refuses faster decision loops, not accumulated momentum. This piece owns refusing keep-pushing as the default reason to open or continue a fight. So you stop that license today and verify spend fewer.
If I already named keep-pushing as the default open in a meeting, how can I still use Energy?
You still can. Refusing the license is not pretending you never said it. You name the crack: which step treated keep-pushing as default war, and how the next cycle got locked to spin speed. You write what next verifies: only whether plan and relationship can still change your choice before you add force. Refuse-momentum-as-still-siege still applies after a declaration. So you can halt the next forced push. Open fewer unnecessary fights next.
Do I need to memorize flywheel playbooks and all thirteen chapters before I have understood the comparison?
No. Those details are evidence elsewhere, not your checklist for today. The live judgment is short. Use momentum to shorten conflict and spend fewer people. Ordinary force is enough when timing and coordination line up — you do not need more destruction. So you check whether “keep pushing” is still the default open you chose, whether that license can be rewritten, and whether object, goal, and resistance are written. Skipping spend-fewer while memorizing both manuals is encyclopedia reading, not judgment.
The next move is not a flywheel-versus-Sun-Tzu spin contest. You write one path that changes the choice before you add more force. You read that judgment on Spend fewer. If it fits, Contact Us — teaching, training, and content, not crushing a rival. We reply within two business days. You stop scoring momentum as a reason to keep pushing. Let the next cycle open with one fewer wasteful fight.