A strategy you cannot encode is a strategy you cannot scale
A strategy only becomes real when it turns into the defaults a system runs on — the floor it will not price below, the claim it will not approve without review, the segment it always routes a certain way. A strategy that resists encoding is usually one that was never precise enough to begin with: if you cannot turn it into a rule a system could follow, you have a feeling, not a plan. The aim is not rigidity but legibility — rules that are few, explicit, and expensive to change. The test I apply: could this decision survive my absence?
There is a moment in every growing company where strategy stops being a document and starts being a set of defaults. The deck said premium positioning. The system says: never discount below this floor, never approve this claim without review, always route this segment here. The second version is the one that actually runs the business.
I have come to believe that a strategy which resists encoding is usually a strategy that was never precise enough to begin with. If you cannot turn it into a rule a system could follow, you have a feeling, not a plan.
Architecture is where strategy goes to become real.From the essay
This is not an argument for rigidity. It is an argument for legibility. The rules should be few, explicit, and expensive to change — so that changing one is a decision, not an accident. The worst systems are full of invisible rules nobody remembers writing.
The test
Here is the test I apply: could this decision survive my absence? If the answer depends on me being in the room, it is not yet a system — it is a dependency. And dependencies do not scale. They just wait to fail at the worst possible moment.