Daily Rambam Accelerated · Startup Mensch · Bite-Sized
Mishneh Torah, Rest on a Holiday 7-8
Hook
Ever feel like your startup is in a perpetual "sprint" where the distinction between "urgent maintenance" and "growth work" has evaporated? You’re burning out your team, not by building the future, but by treating every day like a fire drill.
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
"It is forbidden for a person to delay the performance of these or similar labors intentionally so that he will be able to perform them during [Chol Ha]Mo'ed... Whenever a person ignores his work, leaving it for [Chol Ha]Mo'ed with the intention of performing it then, and actually [begins] to do so, the [Jewish] court must destroy [the fruits of this labor]." (Mishneh Torah, Rest on a Holiday 7:8)
Analysis
Insight 1: The Integrity of Time
The law punishes those who "game the system" by deferring routine work to a period meant for reflection. In business, this is the "technical debt trap." If you defer necessary maintenance to your downtime, you aren't being efficient; you are effectively killing your ability to innovate.
Insight 2: The "Great Loss" Threshold
Rambam permits work during restricted times only if it prevents a "great loss" (davar avud). If your "urgent" tasks are just standard operations, you are violating the principle of protected time. If the task doesn't prevent a disaster, it shouldn't be done during your team's "holy" or restorative windows.
Insight 3: Skill vs. Strategy
The text mandates that professionals must deviate from their usual, high-efficiency methods during restricted times. For founders, this means: when you must work, change your workflow. If you perform high-intensity, high-skill tasks during off-hours, you normalize the grind.
Policy Move
The "Hard Stop" Audit: Implement a policy where any work scheduled during designated "rest" periods (weekends, holidays, or off-sprints) must be accompanied by an "Incident Report" justifying why this task qualifies as a davar avud (preventing a catastrophe). If it’s just "getting ahead," it gets blocked.
Board-Level Question
"Are we currently suffering from 'intentional deferral'—where our team is holding back work just to fill gaps in our calendar, and what does this say about our actual velocity?"
Takeaway
Metric: Track the percentage of "Emergency" tickets opened during off-hours. If that number is high, you don't have emergencies; you have a broken workflow that incentivizes procrastination. Stop managing the crisis and start managing the calendar.
derekhlearning.com