The vocabulary of the doctrine, in one place. Each term links to the essay where it is developed in full.
Foundations
Two enterprises can start in the same place and end in opposite ones. A compounding enterprise turns every system into leverage for the next, so each capability lowers the cost of the one after it. An accumulating enterprise turns every system into another thing to maintain, so each addition raises the cost of the next. The difference is not effort or budget. It is architecture, and it decides whether the company bends upward or downward as it grows.
Read the essayAI does not transform an enterprise. It amplifies the one that already exists. Artificial intelligence is a multiplier, and a multiplier does not change the sign of the number it acts on. Applied to a coherent organization it expands leverage, velocity, and margin. Applied to a fragmented one it accelerates the confusion. AI does not create the underlying condition. It reveals it, then amplifies it.
Read the essayTechnology run as a cost center produces disposable systems that decay from the day they ship. Run as a product company, it produces compounding assets: platforms, data, and workflows that make every future capability cheaper to build. The architecture of returns is the practice of funding outcomes rather than activities, so the technical estate becomes an asset that pays returns instead of a liability that demands maintenance.
Read the essayTechnical Stewardship
Technical stewardship is the discipline of scaling through elimination rather than accumulation. It treats every line of custom code and every added system as a liability to be justified, not a feature to be celebrated. The steward's metric is functional leverage over structural surface area: the most capability carried by the least estate. Saying no is the core act, and it is only sustainable when the standard, supported path is also the easiest one.
Read the essayThe paved path is governance built as infrastructure rather than enforced as approval. Instead of gating work at the end with reviews, you build the secure, compliant, well architected way to do something and make it the fastest way to do it. The controls become the road the team is already driving on. Done right, correctness is the quick option, and governance turns from a brake into acceleration.
Read the essayOperational Leverage
Operational leverage is the ratio between what a business produces and what it must spend to produce it. Technology decisions move that ratio directly. Coherent architecture lifts it by absorbing complexity and removing manual work. Fragmented architecture erodes it by taxing every transaction and adding headcount to compensate. Every architecture decision eventually lands on the balance sheet, in margin, working capital, and the cost of each transaction, whether leadership traces it there or not.
Read the essayComplexity is a cost the accounting never names. Every redundant system, duplicated process, and workaround levies a small charge on every transaction that passes through it. Individually invisible, in aggregate it is the operational tax: the difference between a company that converts growth into profit and one that converts growth into overhead. It stays hidden until a transaction, when a buyer prices the earnings that survive without the people holding the systems together, and the tax returns as a discount on the offer.
Read the essayHuman Velocity
Human velocity is the speed at which a team can turn intent into shipped outcomes. It rises when people own problems rather than process tickets, when cognitive load is kept low enough for them to think, and when the systems around them are clear rather than fractured. It is not about working faster. It is about removing the structural and behavioral friction that consumes a team's finite attention before it ever reaches the work.
Read the essayBehavioral debt is the accumulated cost of interpersonal friction that leadership chose not to resolve. Like technical debt, it compounds when ignored, but it compounds faster, because it is paid in attention, the most constrained resource a team has. It is invisible on the org chart and absent from every dashboard, which is why it grows. The remedy is not forced harmony but early, deliberate correction, before tolerance hardens into culture.
Read the essay