Chullin 29

Hook

In startups, we obsess over the "minimum viable product." We often ask, "Is this enough to count?" But when it comes to critical systems—compliance, security, or product quality—the difference between "half" and "majority" is the difference between a functional asset and a liability. How do you define your "Done" threshold?

Text Snapshot

"The halakhic status of a siman [windpipe/gullet] of which precisely half was cut and half remained uncut is like that of the majority... Rava said: The matter of tereifa [invalidated animal] is different, as we require a majority that is clearly visible." (Chullin 29a)

Analysis

1. Ambiguity is a Liability

The text debates whether a "half-cut" is effectively a "majority-cut." The sages realize that in high-stakes environments, "splitting the difference" creates systemic risk. If you haven’t hit the clear majority threshold, the asset is effectively broken. In business, "pretty much done" is a bug, not a feature.

2. The "Visible Majority" Rule

Rava’s insight is that rules must be "clearly visible" to be valid. Subjective interpretations of progress lead to catastrophic failure. If your team cannot point to a clear, objective metric that defines "complete," you are operating in a state of institutional risk.

3. Context Changes the Requirement

The Gemara distinguishes between "non-sacred" slaughter and "sacrificial" slaughter (where blood must be collected). Not all tasks require the same precision. You must categorize your company’s work: some tasks require "minimum viable," while others require "full integrity."

Policy Move

Implement a "Binary Sign-off" Policy. For all critical technical or legal milestones, eliminate "in-progress" status in reporting. A task is either "0% complete" or "100% complete." If it’s at 90%, it remains at 0% until the final, visible majority of the requirements are met.

Board-Level Question

"When we report progress on our core product/compliance roadmap, are we using 'soft' milestones to mask a lack of finished work, and can we clearly define the 'majority' point where we transition from 'risky' to 'validated'?"

Takeaway

Stop betting on the middle ground. If it isn’t a clear, observable majority, it isn’t done. Metric: % of features/tasks reaching 100% completion vs. % lingering in the "80% done" trap.