Mishneh Torah, Sabbath 18

Hook

The founder’s dilemma is rarely about "doing nothing." It is almost always about the "minimum viable effort" required to move the needle. We are obsessed with thresholds: What is the minimum spend to validate an ad? What is the minimum feature set to launch a beta? What is the minimum equity to keep a co-founder hungry? We intuitively understand that business progress is gated by "measures"—if you don’t reach the threshold, the market doesn’t care, and your effort is effectively wasted energy.

However, the Torah’s perspective on the Sabbath, as codified by Maimonides in Mishneh Torah, Sabbath 18, forces us to confront a terrifying reality: in the eyes of the law, intent defines the threshold.

When you are scaling, you often treat your "minimums" as objective constants. You assume that if a feature is below a certain size, it has no impact. But Rambam teaches us that when a person has a specific, personal desire for a substance, the standard threshold drops to "the slightest amount" Mishneh Torah, Sabbath 18:20.

This is the hidden risk in startup culture. We assume that because a project, a line of code, or a side-hustle is "small," it is inconsequential. We tell ourselves it doesn’t "count" toward our overall load or liability because it hasn't reached a "significant" threshold. But the text warns: if you have a specific intent for that small thing, it is no longer small. It is a "purposeful work."

Founders, you are currently carrying things you think are too small to matter. You are building in "private domains" (your internal vision) and transferring them to "public domains" (the market). You think you’re under the threshold of liability or consequence because the scale is small. The text argues that your intent is the multiplier. If you care about it, it’s not "half a measure"—it’s a full commitment. Are you prepared for the liability of everything you actually care about?

Analysis

Insight 1: The Principle of "Purposeful Work"

The core of the Sabbath prohibition is m’lechet machshevet—purposeful work Mishneh Torah, Sabbath 18:1. In a business context, this is the ultimate KPI of ethics. You are not just responsible for the "big" outcomes (the IPO, the massive launch); you are responsible for the intent behind every micro-decision.

Rambam notes that for most things, there is a legal minimum (the shiur)—for food, the size of a dried fig; for liquids, a revi'it Mishneh Torah, Sabbath 18:4, 7. But this threshold vanishes when the intent is specific. If you transfer a tiny, "sub-threshold" amount of a resource because you have a specific, niche use for it, you are liable Mishneh Torah, Sabbath 18:20.

Decision Rule: Do not hide behind "insignificance." In your organization, if you claim a project is "too small to matter" but your team is obsessed with it, it is not small—it is your primary work. If you have "intent," you have "liability." Stop justifying minor unethical shortcuts by saying, "It’s only a small amount of data/capital/effort." If it serves a purpose, it’s a full-scale action.

Insight 2: The Multiplier of Intent vs. Commodity

The text highlights a fascinating distinction: "When a person has an individual desire for an object that makes it beneficial for him, he is liable even though most people would not use that object for that purpose" Mishneh Torah, Sabbath 18:16.

This speaks to the danger of "founder bias." You might look at a failed feature or a discarded pivot and think it has no value. But if you (or your team) still hold a desire for it, it still occupies space in your company’s "domain." You are still "carrying" it.

Decision Rule: Audit your "storage" of ideas and side-projects. If you are keeping "half-measures" of projects in your pipeline just because you have a personal attachment to them, you are effectively performing the labor of maintaining them. If they aren't reaching the threshold of market success, kill them. Don't carry "half-measures" that clutter your organizational capacity. You are liable for the energy they consume, regardless of their lack of "market size."

Insight 3: Aggregation of Liability

Rambam explains that if you perform a forbidden act in parts—transferring half a measure, then another half—you may be liable if the actions are connected Mishneh Torah, Sabbath 18:27. The "connection" can be spatial (within three handbreadths) or psychological (single period of unawareness).

This is a warning against "salami-slicing" unethical behavior. Many founders think that if they break a project into tiny, non-violating pieces, the sum total is safe. The text suggests that if the intent remains consistent, the pieces aggregate into a single act of violation.

Decision Rule: If you are consistently making "small" compromises across different departments (HR, finance, product) that individually seem below the "threshold" of a crisis, assume they are aggregating. The market doesn't care if your ethics violation was committed in twelve 1% increments or one 12% block. If the intent and the domain are the same, the liability is the same.

Policy Move

The "Zero-Threshold Intent Audit"

Most companies have a "materiality threshold" for reporting issues (e.g., "only flag things over $5,000"). This is a mistake. Based on the principle of m’lechet machshevet—where intent eliminates the need for a size-based threshold—you should implement a "Purpose-Based Reporting Policy."

The Process Change:

1. Remove the Size-Gate: Require reporting on any activity, regardless of size, if it deviates from the company’s stated ethical guidelines, provided that the activity is purposeful.
2. Intent-Mapping: Once a quarter, hold a "Project Inventory" where leaders must justify why they are still "carrying" (maintaining/storing) sub-scale projects. If a project is not reaching the "dried fig" size (i.e., not delivering value), and you don't have a specific "medicinal" (strategic) reason to keep it, it must be purged.
3. The KPI: Track "Zombie Projects"—the count of initiatives that are below the performance threshold but are still being "carried" by the team.

This forces the organization to admit: "We are keeping this tiny, useless project because we are emotionally attached to it." By labeling it as "purposeful," you force the team to acknowledge the liability. If you aren't willing to call it "work," you shouldn't be doing it. Stop the "half-measure" culture. Either commit to the scale required for success or drop the intent entirely.

Board-Level Question

The "Liability of Intent" Inquiry

When you sit down with your leadership team, ask them this:

"We have a list of 'small' initiatives—things we aren't counting as core business because they are below our usual KPIs—but we continue to spend time and energy on them. If we were legally liable for the 'intent' behind these, rather than just the 'size' of their impact, which of these would we immediately shut down, and why are we lying to ourselves about their importance in the meantime?"

This shifts the conversation from "what is the ROI?" to "what is the weight?" A project that consumes your team’s focus but provides no market return is a liability, not an asset, regardless of how small it seems. You are paying for the "transfer" every day.

Takeaway

Stop measuring your life and your business by the size of the result. Start measuring it by the weight of your intent. If you care about it, it is a full-scale project. If it doesn't meet the threshold, stop "carrying" it. You are responsible for the work you intend to do, not just the work that succeeds.