Daily Rambam · Startup Mensch · Bite-Sized
Mishneh Torah, Prayer and the Priestly Blessing 3
Hook
Most founders run their business in a state of perpetual "compensation mode"—constantly fixing yesterday’s missed opportunities or failed launches while trying to hit today’s targets. You are bleeding efficiency because you treat "catch-up" as a substitute for execution. The Rambam warns: there is no permanent fix for a missed window.
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
"Anyone who intentionally allowed the proper time for prayer to pass without praying, cannot rectify the situation and cannot compensate for his failure to pray... If he unintentionally failed to pray or was unavoidably detained or distracted, he can compensate for the prayer during the time of the prayer closest to it." (Mishneh Torah, Prayer and the Priestly Blessing 3:7-8)
Analysis
1. The Death of Retrospective Perfection
The Rambam distinguishes between intentional neglect (no compensation possible) and unintentional error (compensation allowed). In business, if you miss a product-market fit window because you were lazy, no amount of "hustle" will retroactively fix it. You don't get the time back; you only get to deal with the present consequences.
2. The "Closest Window" Rule
When you err, you don't just add a task to your backlog. You must integrate the correction into the current cycle. You perform the current duty first, then the compensation. If you try to fix the past before securing the present, you compromise both.
3. Asymmetric Accountability
"One who errs and recites neither... can only compensate for the last of them." You can only fix so much at once. Stop trying to clear a mountain of debt in one sprint; you are capped by the reality of the current cycle’s capacity.
Policy Move
The "Closing Window" Audit: Implement a "No Backlog Compensation" policy for non-critical tasks. If a non-essential project or feature deadline is missed by more than 25% of its cycle, kill it rather than forcing "compensation" (crunch time). Redirect that energy to the current, healthy initiatives.
Board-Level Question
"Are we spending more than 20% of our current engineering/sales bandwidth on 'compensating' for missed deadlines from last quarter? If so, why are we prioritizing past failures over present market opportunities?"
Takeaway
Stop trying to rewrite history. If you missed the window, accept the loss of that time and focus on the current obligation. Efficiency is not about fixing the past; it’s about not missing the present.
KPI Proxy: Backlog Recovery Ratio (Time spent on "fix-it" tasks vs. Time spent on new value creation). Aim for <10%.
derekhlearning.com