“Security against defeat implies defensive tactics; ability to defeat means taking the offensive.”
First make safe, then make progress; confusing the two leaves you exposed while attacking or stagnant while hiding.
Chapter 4 names its two modes and refuses to blend them: security against defeat implies defensive tactics; ability to defeat means taking the offensive. The line reads like a definition but functions as a diagnostic — most strategic mush is one mode wearing the other’s clothes, attacking from insecurity or fortifying when the moment demands the lunge.
A profitable niche software firm keeps "exploring" new markets — trade shows, pilots, experiments — while its core product quietly rots: support queues, aging architecture, one departure from crisis. It feels aggressive; it is actually undefended and wandering. The corrective was vulgar and unheroic: two years of consolidation, rebuilding the moat — after which expansion, when it resumed, was itself defensible.
The modes are sequential in a campaign, not exclusive in a portfolio — Sun Tzu defends one ground while attacking another. The error is mixing them within a single decision: the half-committed launch that is neither safe nor striking, the hedge that dulls both. Pick the mode per front, and resource it like you mean it.