Mishneh Torah, Leavened and Unleavened Bread 2-4

Hook

You’re staring at a "clean" codebase or a "cleared" desk, but you know there’s technical debt or a hidden liability buried in the company. The Torah’s law of Chametz (leaven) isn't about being a neat freak; it’s about acknowledging that hidden, unmanaged assets can become a liability that invalidates your entire operation.

Text Snapshot

"What is the destruction to which the Torah refers? To nullify chametz within his heart and to consider it as dust... to resolve within his heart that he possesses no chametz at all... all the chametz in his possession being as dust and as a thing of no value whatsoever." (Mishneh Torah, Leavened and Unleavened Bread 2:2)

Analysis

1. The Power of Intentional Nullification

The Rambam notes that the Torah’s primary requirement is a "firm resolve" in the heart. In business, you cannot manage what you ignore. You must formally decide that "hidden" liabilities—the half-finished projects, the ignored compliance risks—have zero value. If you don’t mentally and legally disown the "leaven" (the rot in your system), you are still liable for it.

2. The Search is a Disciplined Practice

The Sages added the requirement to search by candlelight at night because "a person may possibly have difficulty totally removing all thoughts of ownership." You need systematic, active verification. A founder’s "good intentions" aren't a control process. You must look in the "holes and crevices" where you know issues usually hide.

3. The Principle of Proportionality

Not every corner needs the same level of scrutiny. If a place never sees "leaven" (e.g., a storage room for tools), it doesn't require a search. Focus your limited executive bandwidth on the "holes" where your specific business risks actually congregate.

Policy Move

The "Quarterly Liability Sweep": Implement a policy where every lead must perform a "Nullification Audit." For any project or asset that is effectively "dead" or "unfit for use," the lead must file a formal note of nullification. If it’s not worth the time to fix, it’s not an asset—it’s a liability that must be "burned" (decommissioned/archived).

Board-Level Question

“Which of our 'assets'—projects, legacy code, or partnerships—are we holding onto merely out of habit, and if we were forced to ‘nullify’ them today, would we actually be poorer, or would we finally be free to focus?”

Takeaway

KPI Proxy: Time to Decommission. Track the number of days between an asset being identified as "stale" and its total removal from the company’s books or systems. If your cycle time is increasing, you are accumulating Chametz.