Mishneh Torah, Sabbath 3-5

Hook

Founders, we’re built to push boundaries. But what about the unintended consequences of a perfectly legal or seemingly benign action? The Rabbis, sharp as any founder, understood this game-theory of human behavior long before modern risk management.

Text Snapshot

The Mishneh Torah permits initiating work on Friday that completes itself on Shabbat, like when we "open an irrigation channel to a garden... causing it to continue to fill throughout [the Sabbath] day." However, the text immediately adds restrictions to other activities, such as placing food on a fire, "lest one stir the coals on the Sabbath," or reading by a lamp, "lest one tilt [the lamp]."

Analysis

1. Anticipate Second-Order Effects

Don't just greenlight an action because its immediate impact is permissible. Always ask: what’s the natural next step, even if unintentional? The text explicitly states, "A pot may be placed over a fire... With regard to this matter, however, there are certain restrictions that were enacted lest one stir the coals on the Sabbath." The initial act is fine; the potential for subsequent, prohibited action is the trigger for the decree.

2. Design for Human Nature, Not Ideal Behavior

People will optimize, even if it means bending rules. If a permitted setup makes a forbidden action tempting or easy, restrict the setup. "It is forbidden to insert a ladle into a pot to remove [food] while it is on a fire on the Sabbath, because while doing so, one stirs it." The act of stirring, a form of cooking, is a forbidden labor. The Rabbis block the opportunity for it.

3. Contextual Risk Assessment

The same action isn't always treated the same. Risk changes with the environment. "With regard to an oven... we are not allowed to leave food in it or on it... Since [an oven] is very hot, a person will not divert his attention [from the fire]." A high-heat oven (high temptation/high impact) demands stricter rules than a low-heat range.

Policy Move

Implement a "Slippery Slope Review" for all new product features, marketing campaigns, or operational processes. Before launch, identify at least two "second-order" behaviors (even if unintentional) that could lead to ethical or legal non-compliance. KPI Proxy: Proactive Risk Identification Rate (Number of identified 'slippery slope' risks per new feature/process)

Board-Level Question

"Beyond immediate compliance, what systems are in place to proactively identify and mitigate behaviors that, while not inherently problematic, could lead to unintended ethical or legal breaches down the line?"

Takeaway

Ethical design isn't about rigid rules; it's about understanding human psychology and building guardrails. The sharpest founders see around corners, anticipating where good intentions might slip.