Mishneh Torah, Circumcision 2-3

Hook

You're a founder, staring down a deadline. You need a critical feature shipped, a key hire made, or a funding round closed. Your team is stretched, talent is scarce, and the clock is ticking. You ask yourself: "Who can do this? Does it have to be perfect, or just done? What corners, if any, can I cut without sinking the ship?" This isn't just about efficiency; it's about survival, about making the pragmatic calls that keep your startup alive while staying true to its vision. This isn't theoretical; it's the daily grind of balancing speed with quality, delegation with control, and expediency with integrity. The Rambam, in his Mishneh Torah, offers a surprising, sharp framework for navigating these very dilemmas, teaching us how to build with purpose and execute with ruthless, ethical pragmatism.

Text Snapshot

From Mishneh Torah, Circumcision 2-3:

• "Circumcision may be performed by anyone... Even a person who is himself not circumcised, a slave, a woman, or a minor may perform the circumcision, if an adult male is not present. A gentile, however, should not be allowed to perform the circumcision at all. Nevertheless, if he does so, there is no need for a second circumcision."
• "The optimum manner of performing the mitzvah is to use an iron utensil... Throughout the Jewish community, it has become customary to use a knife."
• "Any [mohel] who does not perform metzitzah should be removed from his position."
• "If, [after circumcision,] a portion of the foreskin is left that covers the majority... the child is considered to be uncircumcised... If only a small portion... does not disqualify the circumcision."
• "The preparation of articles that are necessary for the circumcision does not supersede the prohibitions against labor on the Sabbath... since it was possible to bring the knife on Friday."
• "If... the idolator intends to fulfill the mitzvah of circumcision, it is a mitzvah to circumcise him."

Analysis

The Rambam's meticulous laws of brit milah are a masterclass in operational ethics, offering founders three critical decision rules for delegation, quality, and resource management.

Insight 1: Fairness – Competence and Outcome Over Status (But Know Your Non-Negotiables)

The Rambam kicks off with a seemingly radical directive: "Circumcision may be performed by anyone... Even a person who is himself not circumcised, a slave, a woman, or a minor may perform the circumcision, if an adult male is not present." This isn't about Kumbaya; it's pure, unadulterated pragmatism. When the ideal candidate (an adult male) isn't available, the mitzvah is too critical to delay. You widen the talent pool drastically, prioritizing the competence to execute the task over the status or conventional qualifications of the performer. A "slave" or "minor" might not be the CEO's first choice, but if they can deliver the core function, the Rambam says: "Go for it."

However, this isn't a free-for-all. The Rambam immediately draws a bright, non-negotiable line: "A gentile, however, should not be allowed to perform the circumcision at all." This isn't about skill; it's about the fundamental identity and intent tied to the act. As the Yitzchak Yeranen commentary on 2:1:1 clarifies, "the word 'at all' (klal) implies that a gentile should not perform it regardless of whether he is circumcised or not... or whether a Jew is available or not." This task is so intrinsically linked to a specific covenantal identity that external delegation is completely off-limits.

Decision Rule for Founders: Hire for demonstrated capability and a "get-it-done" attitude, especially in a lean startup. Don't let rigid traditional titles or pedigrees limit your talent search when speed and execution are paramount. But critically, identify your company's "gentile line"—those core functions, values, or intellectual property areas that cannot be delegated outside your most trusted, mission-aligned team members or partners, regardless of external skill. These are the tasks where the who and why are as important as the what.

Insight 2: Truth – Outcome Validation Trumps Flawed Origin (But Define "Done" Rigorously)

Here's where the Rambam truly shines with ROI-minded pragmatism: "Nevertheless, if he does so [a gentile performs the circumcision], there is no need for a second circumcision." This is a bombshell. Despite the clear prohibition against a gentile performing the mitzvah, if the physical act of circumcision is completed, the physical state is achieved. You don't scrap the work and start over. As Yitzchak Yeranen on 2:1:2 explains, the Rambam holds that "the physical act of cutting (the ma'aseh) is done, even if the mitzvah is not fulfilled lishmah (for its own sake)." The prohibition was "external" to the act itself; once the desired physical outcome is achieved, it stands. This is a powerful lesson in valuing results.

Yet, this isn't an excuse for sloppiness. The Rambam also states, "Any [mohel] who does not perform metzitzah should be removed from his position." This step, involving suction to prevent internal bleeding, is critical for safety and proper healing. If it's skipped, the entire procedure is considered incomplete, and the mohel loses his license. Similarly, "When one performs a circumcision without performing pri'ah, it is considered as if the circumcision was not performed." These are non-negotiable components of the "definition of done."

Decision Rule for Founders: Don't waste time and resources re-doing work if the desired outcome has been achieved, even if the process was unconventional or less-than-ideal ("suboptimal origin"). Celebrate the win. However, ensure your "definition of done" for all critical tasks includes non-negotiable steps that directly impact safety, core functionality, or user experience. Skipping these makes the entire effort "as if... not performed," requiring a complete restart or rendering the work useless. Regularly audit your "definition of done" for all core product features and operational processes. KPI Proxy: "Defect Escape Rate" – the percentage of critical defects (like a missed metzitzah or pri'ah) that make it past QA and into production, indicating a failure to meet the fundamental "definition of done." Aim for a near-zero rate for mission-critical functions.

Insight 3: Competition – Ruthless Prioritization and Forethought Prevail

The Rambam outlines a pragmatic approach to quality control and resource allocation, especially under pressure (like Shabbat). While still engaged in the operation, the mohel "should go back and remove both the tzitzim that disqualify the circumcision and the tzitzim that do not disqualify the circumcision." This means: fix everything you can while you're in the zone, at minimal marginal cost. But once the activity is interrupted, or the "project" is considered largely done, you only return for the absolute essentials: "Once he has interrupted his activity, he must return and remove any tzitzim that disqualify the circumcision, but he does not return to remove any tzitzim that do not disqualify the circumcision." This is ruthless prioritization: critical bugs get fixed post-launch; minor aesthetic tweaks or "nice-to-haves" wait for the next sprint or are abandoned.

This pragmatic urgency, however, does not excuse poor planning. The Rambam emphatically states: "The preparation of articles that are necessary for the circumcision does not supersede the prohibitions against labor on the Sabbath... since it was possible to bring the knife on Friday." You don't get to break fundamental rules because you failed to prepare. As Ohr Sameach on 2:1:1 explains, there's a clear distinction between the mitzvah itself and preparatory steps. The mitzvah pushes boundaries; preparations don't. If you forget your knife, you delay the mitzvah to the ninth day. This forces founders to distinguish between true emergencies (the mitzvah itself) and self-inflicted crises (poor planning).

Decision Rule for Founders: Integrate a "fix-it-all-while-you're-in-it" mentality for ongoing tasks, minimizing re-engagement costs. Post-launch, apply a strict triage: only critical fixes for "disqualifying tzitzim" get immediate attention. Non-critical improvements are backlogged. Most importantly, ruthlessly plan all "preparatory articles" for major launches or critical operational windows. Your failure to plan does not constitute an emergency for the wider team or justify compromising core ethical/legal boundaries. If it could have been done Friday, do it Friday.

Policy Move

"The Founder's Fulcrum: A Three-Tier Operational & Delegation Framework"

To operationalize these insights, your startup will implement a "Founder's Fulcrum" policy, categorizing all key tasks into three tiers based on their criticality, delegation flexibility, and required foresight. This ensures disciplined pragmatism, maximizes speed where appropriate, and safeguards core mission integrity.

1. Core-Covenant Critical (CCC) Tasks: These are functions directly tied to your company's core mission, ethical promise, or legal compliance, where the identity and intent of the performer are non-negotiable.

   • Examples: Data privacy oversight, core IP development, financial reporting, direct customer trust functions.
   • Rambam's Parallel: "A gentile, however, should not be allowed to perform the circumcision at all," and "Any [mohel] who does not perform metzitzah should be removed from his position."
   • Policy: Restricted to named, highly-vetted internal personnel or strategic partners with explicit alignment to company values and certifications. Rigorous "definition of done" with zero-tolerance for critical defects.
   • KPI Proxy: "CCC Task Audit Failure Rate" – percentage of CCC tasks found to be non-compliant with defined standards or performed by unauthorized personnel (target: 0.00%).

2. High-Impact Operational (HIO) Tasks: These are critical operational functions where the outcome is paramount, allowing for flexible delegation based purely on competence, even if the performer isn't the "optimal" choice.

   • Examples: Non-IP-sensitive coding, marketing content creation, customer support, sales outreach.
   • Rambam's Parallel: "Circumcision may be performed by anyone... Even a person who is himself not circumcised, a slave, a woman, or a minor may perform the circumcision, if an adult male is not present. Nevertheless, if he does so [a gentile performs it, but the outcome is there], there is no need for a second circumcision."
   • Policy: Wide delegation is encouraged. Focus is on delivering the specified outcome. If the outcome is achieved, even if the method was unconventional, it stands. Quality checks are outcome-focused; minor "non-disqualifying" issues are noted for future improvement, not immediate re-work post-completion.
   • KPI Proxy: "HIO Outcome Achievement Rate" – percentage of HIO tasks that meet their defined success criteria (target: 95%+).

3. Preparatory & Support (PPS) Tasks: These are foundational or supporting activities that enable CCC or HIO tasks, requiring meticulous pre-planning to avoid last-minute crises.

   • Examples: Tool provisioning, environment setup, logistical arrangements, documentation.
   • Rambam's Parallel: "The preparation of articles that are necessary for the circumcision does not supersede the prohibitions against labor on the Sabbath... since it was possible to bring the knife on Friday."
   • Policy: Strict pre-planning is mandatory. "Could it have been done yesterday?" is the governing question. Failure to prepare does not justify breaking established rules or creating an emergency for other teams. Delegation to external vendors or less-specialized personnel is permissible for tasks that are only "Rabbinically prohibited" (minor regulatory or internal policy constraints) when it enables a CCC or HIO task to proceed on schedule.
   • KPI Proxy: "PPS Task Delay Impact Rate" – percentage of CCC/HIO tasks delayed due to insufficient or untimely PPS task completion (target: <1%).

Board-Level Question

Given our ambitious growth targets and the constant pressure to move fast, how are we ensuring that our operational agility (as represented by the Rambam's permission to delegate critical tasks to "anyone" based on competence) doesn't inadvertently erode the fundamental "covenant" we have with our customers and stakeholders (as seen in the absolute prohibition against a "gentile" performing the core mitzvah and the removal of a mohel for missing a critical step)? Specifically, what mechanisms are in place to rigorously distinguish between tasks where "outcome trumps origin" and allows for flexible delegation, versus those core functions where the identity, intent, and non-negotiable quality steps of the performer are paramount, safeguarding our long-term value proposition and brand integrity?

Takeaway

The Rambam teaches us that true operational excellence is a disciplined dance between ruthless pragmatism and unwavering commitment to core principles. Delegate broadly for speed, but guard your "covenant" fiercely. Value outcomes, but define "done" with uncompromising clarity on critical steps. And always, always plan ahead—your lack of foresight is not the company's emergency. Build with purpose; execute with precision.