Daily Rambam · Startup Mensch · Bite-Sized
Mishneh Torah, Sabbath 7
Hook
You think you’re “hustling,” but you’re actually just creating technical debt. Founders often confuse activity with impact. The Mishneh Torah teaches us that not all work is created equal; some tasks are structural ("primary categories"), and others are merely symptomatic ("derivatives"). If you can’t distinguish between the two, you’ll spend your life paying for mistakes that don’t actually move the needle.
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
"There are primary categories and [their] derivatives... If one performs an activity that constitutes a primary category [of forbidden labor] and its derivatives in one period of lack of awareness, he is obligated to bring merely one sin offering." (Mishneh Torah, Sabbath 7)
Analysis
1. The Principle of Intent (Kavanah)
The law differentiates between the nature of the work and the intent behind it. Maimonides notes: "All of these [activities] are considered a single primary category... for they share a commonality, since all these activities have a single intent." In business, stop obsessing over the specific task and start auditing the intent. If your team is performing five different "derivatives" (tasks) that all aim at the same outcome, simplify the process.
2. Efficiency of Risk
The text treats a primary category and its derivatives as a single unit of liability. If you are going to incur a risk or expend resources, ensure you are hitting the primary driver of your business model, not just the side-hustle derivatives. Don’t pay the "tax" of complexity for a derivative task.
3. Structural Clarity
Maimonides forces us to categorize work. If a task doesn’t build the "Sanctuary" (the core value proposition), it’s likely just noise. Every task must map to a primary category. If it doesn't, cut it.
Policy Move
The "Root-Cause Audit": Implement a quarterly review where every team project must be tagged as either a "Primary" (core product/growth driver) or a "Derivative" (maintenance/optimization). If a derivative task consumes more than 20% of a sprint, it must be either automated or folded into a primary initiative.
Board-Level Question
"Are we currently investing in the 'Sanctuary' (our core value), or are we inadvertently paying the cost of complex 'derivatives' that don't scale?"
Takeaway
Don't be a technician of derivatives. Be a builder of primary categories.
KPI Proxy: Primary vs. Derivative Ratio (Hours spent on core product innovation vs. hours spent on peripheral task maintenance).
derekhlearning.com