Strategy is what generals write. Doctrine is what soldiers carry. This is the second one.
Most people who read strategy books don't change how they make decisions. They find the frameworks interesting, maybe quote them in a conversation, and then go back to deciding things the way they always have — by instinct, by imitation, or by whoever had the strongest opinion in the room.
That's not a reading problem. It's a format problem. Strategy books are written to be read. Doctrine is written to be used under pressure.
The difference matters because most decisions don't happen in calm moments. They happen when you're tired, when the information is incomplete, when two good options are in front of you and a third bad one keeps looking attractive. In those moments, what you need isn't a philosophy seminar. You need a check — a question you can run in under sixty seconds that tells you whether you're about to make a mistake.
That's what this manual gives you. Forty-plus thinkers, compressed into operational triggers. Not summaries of their ideas. Not what they believed. What their ideas do to a decision when you apply them.
Operator application: You cannot build a team, a partnership, or a contractor relationship on the assumption that people will do what's right because it's right. They'll do what's incentivized, what's visible, what's measured, and what has consequences attached. Build the incentive structure correctly and you don't need to rely on goodwill.
The failure mode: Mandeville gets misused when operators justify paying people badly. That's not the insight. The insight is that institutional design matters more than individual character.
Stripe checkout · card or Link · markdown delivery via email after order confirmation