Menachot 80

Hook

Founders often treat "pivot" capital or redundant assets as sunken costs. We hoard talent and inventory "just in case," then act surprised when that bloat kills our agility. The Talmud here isn't just debating temple offerings; it’s auditing your resource allocation strategy.

Text Snapshot

"The verse states: ‘He sacrifices it,’ indicating that only one thanks offering requires loaves, but not two." (Menachot 80a)

Analysis

1. The Multiplier Trap

The text distinguishes between an "obligatory" offering and a "voluntary" increase. When you over-prepare (bringing two offerings when one suffices), you create "loaves"—additional, mandated baggage. In business, this is operational overhead. Every redundant asset requires its own maintenance cost.

2. The Definition of "Leftover"

The Sages argue over whether the offspring of an offering is a "new asset" or a "leftover." If you view your secondary resources as "leftovers" of a failed experiment, you treat them with neglect. If you view them as "enhancements," you expect them to carry the same weight as the primary asset. Rule: Categorize assets by their utility, not their origin.

3. The "No Brain" Fallacy

Levi suggests complex workarounds to salvage lost assets, and the response is, "It seems to me that he has no brain in his skull." If your recovery strategy for a failed project is more expensive than the project itself, stop pivoting. Rule: A bad asset is not a "guarantee"; it’s a liability.

Policy Move

The "Asset Sunset" Policy: Implement a quarterly review where any "redundant" or "backup" resource (codebase, staff role, or inventory) must justify its existence as a standalone primary asset. If it requires "loaves" (additional management time/budget) but isn't a primary driver, liquidate it.

• KPI Proxy: Asset Utilization Ratio (Total revenue / Total active assets). If this drops, you are carrying "two thanks offerings" when you only need one.

Board-Level Question

"We are currently holding [Project X] as a 'backup' or 'guarantee.' If we had to launch this today as our only source of revenue, would we build it this way? If not, why are we subsidizing its existence?"

Takeaway

Stop hedging with expensive, redundant assets. You are not "increasing thanks"; you are increasing overhead. Efficiency comes from clarity, not from keeping every option on life support.