"War is a matter of vital importance to the state — the province of life or death; it must be thoroughly studied." — Sun Tzu, Ch. I
This week's thesis: In the workplace, The Art of War is often vulgarized into "office Machiavellianism." Its real core is not conspiracy but cold accounting of resources, timing, information, and minds—exactly what tech leaders in large companies most lack when pushing reorgs, cross-team battles, or fighting for resources. This week unpacks four misread cores: (1) Five Factors / Seven Calculations—weigh before you march; (2) Strike the void, ride the momentum—find the gap, borrow the wave; (3) Know the other, know yourself—the hard part isn't knowing them, it's stripping your self-illusion; (4) Win without fighting—the real battlefield is outside the meeting room.
PRINCIPLE 01
Five Factors, Seven Calculations: Weigh Before You March
五事七计 · The Court Calculus
court calculuspre-decisioncost-of-fight
One-Line Principle + Quote
Before pushing a cross-team battle, run a cold "court calculation" through the Five Factors and Seven Comparisons. If you're losing on four or more—don't fight now. Shrink the scope or change the timing.
"He who, calculating in the temple before battle, finds the most counters in his favor, wins. He who finds few, loses. Many counters bring victory, few bring defeat—how much more so does none?"未战而庙算胜者，得算多也；未战而庙算不胜者，得算少也。多算胜，少算不胜，而况于无算乎？— Sun Tzu, Ch. I "Laying Plans"
The Five Factors / Seven Comparisons in Org Terms
Scene
Setup: you want to push a reorg—move the data team from platform org to product org.
✗ Charge without counting
Write a 50-page technical RFC, book the VP. The VP says "sounds reasonable, but platform org disagrees—go align first." Three months later, no news. You've burned some capital, and the opponent is on guard against your next attempt.
✓ Score, then resize
Score each factor: Dao—80% report support (✓); Heaven—perf done, budget unset (neutral); Ground—must cross platform SVP (neutral); General—you were promoted under a year ago, capital pool shallow (✗); Method—no formal reorg process, requires CEO sign-off (✗).
4+ losses → redesign: don't touch reporting lines, set a cross-org dotted line + quarterly review. Capture 80% of the value at half the capital cost—and lay groundwork for a real reorg in six months.
Court Calculation Checklist
Each of the Five Factors backed by hard evidence (numbers, names, quotes)—not guesses?
For each "must-lose" comparison, do I have a fix? If not, shrink the scope.
Have I calculated the opponent's Five Factors too? A crack in their "Dao" is a window.
Is the failure cost quantified? (Reputation, burned bridges, your team's confidence in you.)
Do I have a Plan B—a minimum version I can run again in a year?
Common Mistakes + Female Lens
Treating "calculation" as pessimism. The point isn't to dissuade you—it's to show what the winning version looks like.
Calculating, then not redesigning. The output of calculation is a modified plan, not anxiety.
Only scoring your side. Cracks in their Dao or changes in their General are often the real opening.
Female Leader's Note
Women in large companies usually have shallower capital pools (more scrutiny, less benefit of the doubt)—each battle costs more in relative terms. Court calculation matters more for women, not because you fear loss more, but because after one loss, you get fewer "next times." Calculating "is this worth it" is capital preservation, not cowardice.
This Week's Action + Reflection
Action: Pick one Q3 push. Score it on Five Factors / Seven Comparisons. If losing ≥ 4, write a smaller version. Reflection: Of last year's battles, how many were "passion-driven launches" vs. "calculated launches"? Compare success rates.
PRINCIPLE 02
Strike the Void, Ride the Momentum
避实击虚 + 因势利导 · Find the Thin Wall, Borrow the Wave
void & substanceborrowed momentumframing
One-Line Principle + Quote
Organizations have no true vacuums, but they have thin walls. Smart leaders don't ram strong territorial claims—they find the gap no one owns and plant a flag there. And they don't push by personal force; they ride waves the big org is already creating.
"The form of an army is like water: water avoids heights and runs downward; an army avoids strength and strikes weakness." "The skilled warrior seeks victory from the momentum, not from individual men."夫兵形象水，水之形避高而趋下；兵之形，避实而击虚。故善战者，求之于势，不责于人。— Sun Tzu, Ch. VI "Weak Points and Strong" / Ch. V "Energy"
Scene
Setup: as a tech lead manager, you want to elevate AI inference standardization to a company-wide initiative.
✗ Hit the strong wall
Challenge platform org directly (they nominally own AI infra). Write a "you're doing it wrong, I'll do it" RFC. You instantly become the invader. The platform org head and two allies block you at review—technically they agree, politically they can't let you win.
✓ Strike the void + borrow the wave
Scan the void: platform org nominally owns it, but no one's actually doing "cross-BU inference standardization"—a true gap. Scan the wave: CFO is pushing AI cost optimization; CEO mentioned in all-hands that inference is 40% of cloud spend. That's momentum. Reframe: "Responding to the CFO's cost initiative, I propose a cross-BU inference standardization working group—chaired by platform org, with my team and two BUs contributing engineering. Projected 15–20% cost reduction." Result: platform org doesn't block—they thank you for elevating their work. CFO provides air cover. You become the de facto technical lead, and no one feels you grabbed power.
Wave-Riding Checklist
Can I list 3 things the CEO / CFO / SVP is currently pushing? (That's the wave.)
Does my proposal hook into at least one of them? (Hooked in = borrowed momentum.)
Who nominally owns this space? Does my framing make them a beneficiary or an invader?
Can I let them chair while I drive? (Make the win theirs.)
Is my 30-second pitch from my needs—or from the company's current agenda?
Common Mistakes
Seeing a void and assuming it's an opportunity—without asking why it's empty. Maybe someone tried and failed. It's a minefield, not free land. Check history first.
Borrowing momentum becomes parasiting on it. If your pitch only superficially connects to the current agenda, exposure hurts worse than a direct attack.
Striking the void successfully, then expanding to grab "real" territory. You expose ambition early and lose the allies you just won.
Trying to create the wave yourself. You're not the CFO or CEO. You don't create momentum—you borrow it. Get this direction wrong and even hard work runs upstream.
This Week's Action + Reflection
Action: Using earnings, the latest all-hands, and CEO/CFO internal memos, list the company's top 3 themes this month. Hook your proposal to one of them. Rewrite the pitch in ≤ 100 words. Reflection: Your most exhausting push in the last six months—did you hit strength head-on with no wave to ride?
PRINCIPLE 03
Know the Other, Then Strip Your Self-Illusion
知彼知己 · The Hard Part Is Knowing Yourself
stakeholder pre-readanti-projectionself-awareness
One-Line Principle + Quote
The hardest part of "know the other, know yourself" isn't knowing the other—it's that when you look in the mirror to "know yourself," you often see a romantic projection, not the real you. Real stakeholder pre-read means stripping that illusion.
"If you know the enemy and know yourself, you need not fear the result of a hundred battles. If you know yourself but not the enemy, for every victory you will also suffer a defeat. If you know neither, you will succumb in every battle."知彼知己者，百战不殆；不知彼而知己，一胜一负；不知彼，不知己，每战必殆。— Sun Tzu, Ch. III "Attack by Stratagem"
Scene
Setup: you need cross-team peer Sara (product VP) to back an architecture change.
✗ Mirror projection
You assume Sara cares about "long-term tech debt" like you do. Your opener: "This architecture will become a bottleneck in three years, we should fix it now." Sara nods politely, meeting ends, nothing moves. She actually cares about Q3 GMV—your framing never touched her ledger.
✓ Three rounds of pre-read
Know-other R1 (public): Read Sara's last-quarter OKRs, her team's hiring plan, the questions she asked in all-hands—she actually cares about cart abandonment and checkout speed. Know-other R2 (back-channel): Find a peer who's worked with Sara. Ask: "How does she decide in meetings? What makes her say no? Whose word does she trust?" Know-self: Ask yourself—is my pitch useful to her, or what I want to say? Strip the tech words: what does my proposal look like in her vocabulary? Rewrite opener: "Sara, I looked at your Q3 goals. Our refactor drops checkout latency from 200ms to 50ms—against your funnel data, 1–2% direct impact on cart abandonment. 20 minutes to align on timing?"
Anti-Projection Checklist for Real Self-Knowledge
Can I restate my proposal in their KPI / OKR language?
Is my "knowing them" based on first-hand data (docs, OKRs, decision records)—or hearsay?
Have I listed at least 3 of my own blind spots—especially "things I assume they care about but they don't"?
"If they reject me, from their angle what's their logic?"—if I can articulate it, I really know them.
What I see as a strength—could they see it as a risk? (Seniority, technical depth can read as threat.)
Common Mistakes + Female Lens
Treating "know the other" as one-time research. They move. OKRs refresh quarterly. Last year's picture may be entirely stale.
Turning "know yourself" into a SWOT self-praise. Real self-knowledge means admitting "in which rooms I have no credibility, and what my framing actually sounds like to them."
Getting dirt from a mutual friend without verifying. Second-hand portraits are the easiest to stereotype—and most likely to make you underestimate.
No "trust broker" for a critical stakeholder. Pushing a big thing through formal email = naked under fire.
Female Leader's Note
"Know yourself" is harder for women, because the external feedback system has systematic underestimation built in—the mirror you look into is itself biased. Counter: once a year, proactively ask 2–3 trusted peers from different backgrounds, "From where you sit, what is my reputation in this company? What are my blind spots?" Write it down. This isn't seeking validation—it's calibrating the mirror you use.
This Week's Action + Reflection
Action: Pick one stakeholder you must engage in the next 30 days. Run all three rounds (public / back-channel / anti-projection). Rewrite the pitch. Reflection: Your last failed push—was it really "didn't know them," or "didn't know yourself"? The latter usually weighs more—and is harder to admit.
PRINCIPLE 04
Win Before the Meeting: The Real Battlefield Is Outside the Room
不战而屈人之兵 · Pre-Wire, Don't Persuade
attack the planpre-wiringratify, not debate
One-Line Principle + Quote
If the debate starts in the meeting, you've already half lost. The highest skill isn't winning the argument—it's making the argument unnecessary. The meeting ratifies an agreement that already exists; it doesn't produce one.
"To win a hundred battles is not the highest excellence; to subdue the enemy without fighting is. Therefore the highest form of war is to attack the enemy's strategy; next, to disrupt his alliances; next, to attack his army; the worst, to besiege walled cities."百战百胜，非善之善者也；不战而屈人之兵，善之善者也。故上兵伐谋，其次伐交，其次伐兵，其下攻城。— Sun Tzu, Ch. III "Attack by Stratagem"
The Pre-Wiring Timeline
Scene
Setup: next week's architecture review, you're proposing to split a monolith into 4 services—a contentious call.
✗ Siege the walled city (the worst form)
Walk into the room, deck up, pitch to 7 stakeholders, hope to out-argue them. Result: the strongest opponent you misjudged (the SRE lead next door) throws three concerns you didn't prepare for. No conclusion, agenda pushed two months out. Capital burned, your proposal labeled "not ready."
✓ Attack the plan + realign alliances
T-7: 1:1 with SRE lead. "I want to propose a split next week. Before we decide, I want to hear your concerns—if I haven't addressed them, I won't force it in the room." Let him vent. T-5: Revise 2 things in the plan. Note in the doc: "per SRE lead's feedback on 2025-Q4 incident"—contribution visible. T-3: 1:1 with the architecture chair: "Looking at the current draft, what push-back would you expect?" Pre-digest it. T-2: 1:1 with the product VP you expect to stay silent. "This affects your Q4 launch by 2 weeks; I'll loan you an engineer in week 3 to bridge." Defuse surprise grenades. Day 0: You aren't pushing your idea anymore—you're ratifying a proposal 6 people already shaped. 30 minutes, done.
Pre-Wiring Checklist
Have I talked 1:1 with everyone who'll speak more than 30 seconds in the room?
Did one opponent become a co-author? (Absorbing the strongest objection = strongest shield.)
Does the doc credit "per X's feedback"—so they don't have to fight in-room for credit?
Is there at least one ally in the room who'll speak up for me?
If the meeting gets postponed, what happens to my progress? (Pre-wiring makes "postpone" hurt less.)
Common Mistakes
Turning pre-wiring into "lobbying." You're not there to persuade—you're there to hear concerns and modify the plan. Lobbying leaves scars; listening builds allies. One-word difference.
Skipping people you assume won't object. Silent people who object in-meeting do the most damage—they'll use process to kill you.
Misusing "disrupt alliances" as backstabbing. Backstabbing once detected is enormously expensive. The real move is letting stakeholders re-evaluate interests, not flipping sides.
Treating pre-wiring as dirty politics. Its essence is respect—giving people the chance to digest, push back, and change course outside the room is more dignified than being overruled in public.
This Week's Action + Reflection
Action: Pick one important meeting next week. List the 5 likely voices. Schedule a 1:1 or async note with each before the meeting. In the room, count how many "surprise" concerns appeared. Reflection: Of the times you were "derailed by a surprise objection in a meeting" last year, how many could have been avoided by a 15-minute 1:1 beforehand?
Going Deeper
Sun Tzu wrote for zero-sum war; companies are cooperative organizations. Are there limits to applying it?
Yes. In a company, "enemies" are rarely individuals—they're misaligned incentives, information gaps, process inertia. Sun Tzu's core is cold accounting of resources and timing—that part is zero-sum-agnostic. Watch out for the "us vs them" frame quietly growing in your head, turning temporarily misaligned peers into objects of war. Each quarter ask: "Whom did I imagine into an enemy these past three months? Really?"
"Win without fighting" vs. Radical Candor—aren't they contradictory?
Layer them. Strategic layer—use Sun Tzu: big issues, cross-team battles, reorgs require pre-wiring; the meeting just ratifies. Tactical layer—use Radical Candor: 1:1s, feedback, coaching demand directness, in-person, no detours. Both refuse "improvising the script in the room." Both require pre-work. Mismatch costs: Sun Tzu for feedback = schemer; Radical Candor for strategy = brute.
What if "court calculus" becomes paralysis—delayed decisions, missed windows?
Set a hard deadline: no proposal gets more than 5 working days of calculation. After 5 days, however imperfect, move to the next step (shrink scope, book a 1:1, write the RFC). Stalling usually isn't over-calculating—it's fearing the uncomfortable conclusion ("I can't fight this now / my capital isn't enough"). Naming that motive matters more than adding more inputs.
Large company vs. startup—where does Sun Tzu apply differently?
Large companies have complex terrain and process as a variable—court calculus and pre-wiring have the highest leverage. Two weeks of prep beats two hours of meeting debate. Startups weight "Dao" and "General" heavily; "Method" barely exists; speed itself is the wave—pre-wiring may make you miss the window. BigCat in a large org: default to Sun Tzu mode.
You calculated and the fight is unwinnable—but your team and your ownership are betting on it. Withdraw or push?
Not binary. Reshape with dignity, three steps: (1) Tell the team your new read immediately—re-scope, not failure declaration; (2) Find the 30% that stands independently, ship that—your team's work doesn't go to zero; (3) Convert the remaining 70% into a "signal collection phase," watching which conditions next quarter could make the calculus flip. In a big org, forcing a doomed fight doesn't burn your capital alone—it burns the team's trust in your judgment, which is the longer wound.