Daf Yomi
Chullin 130
In another voice
Hook
You’re scaling, and you’re obsessed with "fairness." You want a universal playbook for every department. But here’s the reality: treating all your assets as if they share the same rules is a recipe for operational gridlock. Sometimes, the "right" thing to do depends entirely on the status of the asset.
Listen to this lesson. Ask it questions.
Audio, a chevruta that cites its sources, Hebrew tools, and every daily cycle, in the app.
Text Snapshot
Mishnah Chullin 130: "The gifts of the priesthood... apply to non-sacred animals, but not to sacrificial animals... the priest has only that which is stated with regard to that matter."
Analysis
1. Contextual Differentiation
The Mishna establishes that logic (a fortiori) has limits. Just because a rule applies to one category (non-sacred animals) doesn't mean it scales to another (sacrificial animals). In business, your "standard" policies for general hires or products often fail when applied to "sacrificial" assets—those core, high-stakes projects or key hires that have different internal "sanctity" and structural requirements.
2. The Limit of "Fairness"
The Gemara notes that if we didn't have specific limitations defined, we would mistakenly force rules where they don't belong. Applying a one-size-fits-all fairness metric across different tiers of assets creates confusion. Fairness isn't treating everything the same; it's respecting the distinct "due" of each category.
3. The "No Claimant" Defense
The Talmud explores the idea that some assets have no specific claimant, making them exempt from standard collection enforcement. If you don't define exactly who owns the responsibility or the benefit, the system breaks down. Ambiguity in policy is the enemy of execution.
Policy Move
Implement a "Status-Based Policy Audit." Categorize your company assets/projects into "Standard" and "Strategic/Sacrificial." Audit your SOPs: Do your standard HR or operational rules conflict with the specific needs of your high-value "sacrificial" projects? If a rule doesn't explicitly fit, don't force it via bad logic.
Board-Level Question
"Are we applying our 'Standard' operating procedures to 'Strategic' assets, and is that causing us to lose focus on what is truly unique about our growth engine?"
Takeaway
Know your category. Don't try to force a universal rule where the system requires a specific one. Define the "due" for each asset tier clearly, or expect the system to fail when you try to enforce it.
Metric: Percentage of SOPs that explicitly account for asset-class exceptions.
Tomorrow's lesson, already explained.
Today's is done. Tomorrow morning's arrives the same way: one short, source-cited email on the day's page. Every day of the cycle has one.
derekhlearning.com