Mishneh Torah, Sabbath 9

Hook: The "Minimum Viable Effort" Trap

Founders often think their contribution doesn't count if the project isn't "finished." You’re building the product, your co-founder adds the database, another lead deploys the server. You tell yourself, "I didn't launch it, so I’m not responsible for the outcome." Maimonides disagrees. In business, as in the laws of Shabbat, the intent to create a finished result makes you liable, even if your individual input was small.

Text Snapshot

"When one person brought fire, another brought wood, another brought a pot... all are liable for cooking. For anyone who performs an activity that is necessary for cooking is considered as [having performed that forbidden labor]." (Mishneh Torah, Sabbath 9:10)

Analysis: 3 Decision Rules

1. Shared Liability: If your team works with "shared intent" to reach a specific product milestone, every contributor owns the result. You cannot outsource your ethics to the person who clicked "deploy."
2. The "Small Limb" Standard: The law defines liability by the utility of the action (e.g., heating enough water to wash a small limb). If your contribution, however small, moves the needle toward a functional state, you are fully "cooking."
3. Intent vs. Outcome: If you act independently, you aren't liable for the group's error. But if your actions are part of a coordinated strategy, your individual contribution is irrelevant; the total system output is what you are held accountable for.

Policy Move: The "Contribution Audit"

Implement a "Dependency Matrix" for all high-stakes product changes. Before any major release, document exactly who contributed which component. If a feature fails or causes harm, the policy should explicitly state that "I just wrote the code, I didn't push the button" is not a valid defense. Everyone who contributed to the "pot" is responsible for the "stew."

Board-Level Question

"If our current product causes a significant customer loss, which of our internal 'contributors'—from dev to sales—would be legally and ethically 'liable' under our current team structure, and does our culture reflect that shared burden?"

Takeaway

Complexity is not an alibi. Whether you’re building software or a business, if you provide the "fire" or the "wood," you are cooking the meal. Own the whole stack, or stop touching the ingredients.

KPI Proxy: % of cross-functional team members who can articulate the business impact of their specific sub-task.