Zevachim 117

Hook

You’re a founder, not a kindergarten teacher. You know that "fairness" isn't always about treating everyone identically. Sometimes, giving everyone the same thing means giving no one what they truly need. You’ve got a superstar engineer who wants to use a bleeding-edge framework for a critical module, a sales team demanding different CRM features for their enterprise clients versus SMBs, and a rising star asking for a remote work setup while everyone else is in-office.

Your gut says "different strokes for different folks" makes sense, but your legal team whispers "discrimination," and your ops lead screams "scalability nightmare." How do you reconcile the need for standardized processes and equitable treatment with the undeniable reality that different people, different roles, and different customer segments demand different approaches? When does differentiation become discrimination, and when is standardization just stifling? This isn’t a soft-skills problem; it’s an operational and strategic tightrope walk with real ROI implications. Torah's ancient wisdom, surprisingly, offers a surprisingly sharp framework for this modern founder dilemma.

Text Snapshot

The Gemara in Zevachim 117 delves into the intricate laws of ritual purity and offerings, revealing a profound principle of differentiated treatment:

"“Outside the camp you shall put them; that they will not defile their camps” (Numbers 5:3). The use of the plural “camps” indicates: Give a specific camp to this group, and give a specific camp to this group…"

"“He shall dwell alone; outside the camp shall his dwelling be” (Leviticus 13:46). The word “alone” teaches that another ritually impure person should not dwell with him."

"Moses said… “You shall not do all that we do here this day, every man whatsoever is fitting in his own eyes. For you have not as yet come to the rest and to the inheritance” (Deuteronomy 12:8–9)… fitting offerings [yesharot]… you may sacrifice, but you may not sacrifice obligatory offerings."

Analysis

Insight 1: Differentiated Fairness, Not Identical Treatment

The Torah explicitly states, "Give a specific camp to this group, and give a specific camp to this group." This isn't just about ritual purity; it's a foundational principle of intelligent segmentation. The text identifies various categories of individuals (e.g., zavim, corpse-impure) and assigns them distinct "camps" or zones of access based on their specific status. Crucially, it uses the plural "camps" to emphasize that a single, uniform exclusion zone isn't sufficient; different groups require different, tailored boundaries.

In business, "fairness" is often misinterpreted as "identical treatment." This text smashes that notion. True fairness, especially for a founder obsessed with ROI, means providing appropriate conditions, resources, or access levels based on distinct needs, roles, or customer segments. Trying to force a single "camp" (i.e., a one-size-fits-all policy, product, or operational structure) onto fundamentally different groups leads to inefficiency, dissatisfaction, and ultimately, failure. Your enterprise clients, with their complex integrations and compliance needs, demand a different "camp" (support, SLA, feature set) than your SMBs. Your senior engineers, who've earned autonomy and demonstrated expertise, require a different "camp" (flexibility, decision-making power) than new hires who need more structured guidance.

Decision Rule: Categorize your stakeholders (customers, employees, partners) based on clearly defined attributes that genuinely impact their needs or your operational requirements. Design policies, products, and processes that are "specifically camped" for each group, ensuring that the differentiation is rooted in objective criteria, not arbitrary bias. Don't fear segmentation; embrace it as a path to optimized value delivery and engagement.

KPI Proxy: "Segment-Specific Policy Adherence & Satisfaction Rate." Measure how well policies designed for specific employee or customer segments are adopted and rated for effectiveness by those segments. A high score suggests successful, differentiated fairness.

Insight 2: The Precision of Boundaries and "Alone" Status

The Gemara further refines this concept with the leper: "He shall dwell alone; outside the camp shall his dwelling be. The word 'alone' teaches that another ritually impure person should not dwell with him." This isn't just about putting someone in a different "camp"; it’s about absolute, non-negotiable isolation for specific, high-impact cases. Even other "impure" individuals cannot share the leper's space. This highlights scenarios where certain risks or conditions are so potent that they demand complete segregation to prevent broader "defilement" or negative externalities. The text later describes how a Levite who unintentionally kills someone is exiled "from one Levite city to another Levite city," or even "to another area within his city." Even within a designated "refuge," further precise isolation can be required.

For founders, this translates to mission-critical security, compliance, or risk management protocols. Some issues simply cannot be allowed to spread or compromise core operations. Think about a cybersecurity breach: you don't just put the compromised server in a "different network segment"; you often isolate it entirely, and perhaps even isolate the type of data it held from other sensitive data. Or consider a team member who consistently violates ethical standards or poses a direct threat to company culture or data integrity: they must be isolated, perhaps even from similar "problematic" individuals, to prevent contagion. The "alone" status isn't about punishment; it's about safeguarding the integrity of the whole system. The example of the Levite killer suggests that even well-intentioned mistakes might require a highly specific form of internal exile or isolation to ensure the safety and trust of the broader community.

Decision Rule: Identify your "leper-level" risks – situations where contamination, data breaches, severe ethical violations, or critical system failures could catastrophically impact the entire organization. For these, implement "alone" protocols: absolute isolation, stringent access controls, and non-negotiable boundaries. Don't compromise on these core safeguards; their integrity protects the entire "camp."

KPI Proxy: "Critical Incident Containment Time" or "Severity 1 Bug Escape Rate." This measures how quickly and effectively you isolate and prevent the spread of high-impact issues, reflecting the strength of your "alone" protocols.

Insight 3: Strategic Autonomy vs. Core Obligation – The "Fitting in His Own Eyes" Dilemma

Perhaps the most potent business lesson comes from the discussion of offerings: "Moses said… “You shall not do all that we do here this day, every man whatsoever is fitting in his own eyes. For you have not as yet come to the rest and to the inheritance” (Deuteronomy 12:8–9)… fitting offerings [yesharot]… you may sacrifice, but you may not sacrifice obligatory offerings." During a transitional period, individuals were permitted to bring "fitting" (voluntary, discretionary) offerings on private altars but not "obligatory" (compulsory) ones. This is a brilliant model for balancing individual initiative with core organizational requirements.

This text gives founders explicit permission, and even a directive, to distinguish between what is "obligatory" and what is "fitting in one's own eyes." "Obligatory offerings" represent the non-negotiable core: your company's mission, compliance with regulations, foundational product stability, core values, and essential operational processes. These must be standardized and centralized, ensuring consistency and reliability. "Fitting offerings," on the other hand, are areas where individuals or teams can exercise autonomy, experiment, and pursue initiatives that they deem beneficial or innovative. This is where bottom-up innovation, creative problem-solving, and individual growth thrive.

The caveat, "For you have not as yet come to the rest and to the inheritance," is critical. It implies that this balance is dynamic and context-dependent. In early-stage startups, more might be "fitting in his own eyes" as you search for product-market fit. As you scale and move towards "rest and inheritance" (market leadership, maturity), more aspects might become "obligatory" to maintain efficiency and brand consistency. The challenge is to explicitly define these two categories and empower teams within the "fitting" zones while rigorously enforcing the "obligatory" ones.

Decision Rule: Clearly delineate "obligatory" tasks, processes, and standards (non-negotiable for core business function, compliance, and brand integrity) from "fitting" areas (where individual or team autonomy, experimentation, and discretionary effort are encouraged). Empower teams to make "fitting" contributions within defined boundaries, but ensure unwavering adherence to "obligatory" requirements. Regularly re-evaluate this balance as the company evolves.

KPI Proxy: "Innovation-to-Core Conversion Rate." This metric tracks the percentage of successful "fitting" projects (innovations, experiments) that are eventually integrated into the "obligatory" core product or process offerings, demonstrating effective strategic autonomy leading to tangible value.

Policy Move

Two-Tiered Project Framework: "Obligatory" vs. "Fitting" Initiatives

To implement the "fitting in his own eyes" principle while safeguarding "obligatory" core functions, a company should adopt a Two-Tiered Project Framework. This framework formally categorizes projects and initiatives, assigning distinct governance models, resource allocation, and reporting requirements based on their strategic impact and risk profile.

Tier 1: Obligatory Offerings (Core Projects)

• Definition: Projects critical to the company's immediate survival, regulatory compliance, foundational product stability, and direct revenue generation from existing offerings. These are non-negotiable for the organization's current health.
• Governance: Centralized oversight (e.g., C-level sponsorship, PMO-managed), strict adherence to approved tech stacks, security protocols, and compliance standards. Rigorous budget and timeline controls.
• Examples: Major product releases, security patches, compliance updates (e.g., GDPR, SOC2), core infrastructure upgrades, critical bug fixes, maintaining existing customer SLAs.
• Resource Allocation: Priority access to shared resources, dedicated teams, higher budget certainty.

Tier 2: Fitting Offerings (Exploratory/Innovation Projects)

• Definition: Projects that are "fitting in his own eyes"—discretionary, exploratory initiatives aimed at future growth, new market exploration, process improvement, or innovative feature development that do not immediately impact core stability or compliance.
• Governance: Decentralized ownership (e.g., team-led, hackathon projects), flexible tech choices (within an approved sandbox), lighter oversight focused on learning and iteration, not just delivery.
• Examples: R&D for new product lines, internal tool development, experimental marketing campaigns, process automation pilots, employee-led initiatives for cultural improvement.
• Resource Allocation: Dedicated innovation budget, protected time for teams (e.g., 20% time), often leveraging existing talent.

This framework directly addresses the text's distinction between "obligatory" and "fitting" offerings, providing a clear structure for where standardization is paramount and where autonomy is encouraged. It allows for the necessary "different camps" for different types of work, ensuring that critical operations are protected while fostering innovation.

KPI Proxy: "Innovation-to-Core Conversion Rate." Track the percentage of Tier 2 projects that successfully mature, demonstrate significant value, and are then promoted to Tier 1 for full integration and scaling.

Board-Level Question

"Given our current stage of growth and the imperative to both scale efficiently and continue innovating, how do we strategically define our 'obligatory offerings' (non-negotiable core processes, values, and compliance standards) versus areas where we empower 'fitting in their own eyes' autonomy and experimentation, ensuring we're building towards our 'rest and inheritance' without stifling critical innovation or risking foundational stability?"

This isn't an operational question; it's a strategic one for the board. It forces a discussion on the company's fundamental risk appetite, resource allocation philosophy, and long-term vision. Defining "obligatory" sets the boundaries for core stability and compliance, protecting the company's current value. Defining "fitting" articulates the scope for future growth, employee empowerment, and market differentiation. The phrase "rest and inheritance" from the text grounds this question in a long-term strategic context, prompting leadership to consider how the current balance between standardization and autonomy positions the company for sustainable success, not just short-term gains. It's about designing an organizational architecture that can both endure and evolve, a critical decision with direct impact on long-term shareholder value and employee engagement.

Takeaway

Torah teaches that effective leadership isn't about uniform rules, but about intelligent differentiation, clear boundaries, and a strategic balance between individual autonomy and core organizational imperatives. Know when to give a "specific camp" for tailored treatment, when to enforce "alone" status for critical risks, and when to empower "fitting in his own eyes" while safeguarding the "obligatory." This isn't just ethics; it's smart business.