Daf A Week · Startup Mensch · Bite-Sized

Nedarim 88

Bite-SizedStartup MenschJune 28, 2026

Hook

Founders often struggle with the "intent vs. impact" trap. You design a policy to protect the company (like a restrictive covenant or a budget control), but in practice, it cripples your best talent. How do you maintain control without strangling utility?

Text Snapshot

The Gemara in Nedarim 88a wrestles with whether a blind person is liable for accidental killing. The debate centers on interpreting specific phrases: does "without seeing" exclude the blind, or include them? The Sages conclude: "There is no contradiction here... the ruling follows from the context of the verse" (Nedarim 88a:1:1).

Analysis

Insight 1: Context Trumps Universalism

The Sages refuse to apply a blanket rule to the "blind" across all legal domains. Sometimes, the context of the law (the "forest") matters more than the abstract category of the person. Decision Rule: Don’t apply generic "corporate policy" without assessing the specific operational context. A policy designed for standard employees often creates unintended liability for high-performers or unique roles.

Insight 2: The "Gift" Loophole

The Mishnah discusses a father-in-law who forbids his son-in-law from benefiting from his money, yet wants to support his daughter. He grants her funds with a specific condition: "that your husband has no rights to it" (Nedarim 88a:1:1). Decision Rule: Legality is found in the specificity of the carve-out. If your organizational constraints are too broad, you lose the ability to support your most important partners.

Insight 3: Knowledge as a Metric

Rabbi Meir argues that "without knowledge" is the trigger for liability (Nedarim 88a:1:1). Decision Rule: If you cannot track the "knowledge" of your team (their awareness of risk), you cannot effectively distribute responsibility.

Policy Move

The "Carve-Out" Clause: Implement a "Founder’s Exception" process. For every restrictive policy (e.g., spending caps, data access), define a "conditional gift" exception where managers can bypass the constraint by documenting the specific intent and acknowledging the fiduciary risk.

Board-Level Question

"Are we enforcing policies because they are logically consistent, or because they serve the actual context of our current growth stage?"

Takeaway

Rigidity is a sign of a weak strategy. Distinguish between the letter of your policy and the context of your business goals. Use specific, documented exceptions—not vague hand-waving—to empower your team while maintaining control.