Daily Rambam · Startup Mensch · Bite-Sized
Mishneh Torah, Sabbath 11
Hook
You think you’re “just” optimizing a process, but you’re actually killing the ecosystem that sustains your business. Founders often treat "waste" or "inefficiency" as things to be ruthlessly culled, but the Torah warns that how you end a process—and the intent behind it—defines your liability.
Full Experience in the App
Listen. Chat. Go deeper.
Audio playback, interactive chevruta, Hebrew tools, and every daily learning track — only in Derekh Learning.
Text Snapshot
"A person who takes the life of a living beast... is liable... A person who strangles a living creature performs a derivative of slaughtering... one is liable even if one returns it to the water before the fish actually dies." (Mishneh Torah, Sabbath 11:1–2)
Analysis: The Ethics of Ends
1. The Cost of "Collateral" Impact
The text notes that removing a fish from water until it is near death creates liability, even if you put it back. In business, you may think you can "choke" a subsidiary, a department, or a vendor relationship for a short-term cash injection and then "put them back in the water" later. The law disagrees: The harm is in the act, not just the final result.
2. Intent Over Outcome
The Rambam distinguishes between killing for a purpose versus "destructive intent." If you are building, you are liable; if you are merely breaking, you are not. Rule: If your process change is purely destructive (culling staff or products without a strategic "replacement" architecture), you are not just inefficient—you are violating the moral mandate of construction.
3. The Permanence Test
Liability attaches when an act leaves a "permanent mark" (e.g., writing that stays). If your business pivots leave no lasting value—just friction—you are "writing on water." Rule: If the impact of your decision won't outlast the current quarter, it is ethically and strategically irrelevant.
Policy Move: The "Reverse-Impact" Audit
Before any major organizational cut or pivot, implement a "Persistence Check." If you cannot articulate how the removed resource or process will be replaced by a more robust "permanent mark" (growth, better product, efficiency), the act is forbidden. Require leadership to document the replacement value before the destructive act is approved.
Board-Level Question
"Are we currently 'strangling' a business unit for short-term liquidity, or are we actively building a replacement that will endure longer than the current entity we are deconstructing?"
Takeaway
Don’t be a butcher of processes; be a master of transitions. If you aren't building something that lasts, you aren't leading—you’re just clearing the desk.
derekhlearning.com