Mishneh Torah, Circumcision 2

Hook

The founder’s greatest trap is the "purity fallacy"—the belief that a business process, a product launch, or a critical hiring decision must be executed by the "perfect" person under "perfect" conditions to count as a success. In the high-stakes world of startups, founders often paralyze their own growth by waiting for the ideal candidate, the perfect tech stack, or the "right" market alignment. They treat their venture like a fragile ecosystem that will collapse if a non-expert touches the controls.

But look at the reality of scaling: if you wait for the "perfect" conditions to ship, you have already failed. The Mishneh Torah on circumcision offers a radical, counter-intuitive lesson for the entrepreneur. It posits that the result (the fulfillment of the covenant) is paramount, and the agency—while prioritized for the expert—is secondary to the completion of the task.

Consider this: "Circumcision may be performed by anyone... if an adult male is not present." The text doesn't say "don't do it if the expert isn't there." It says "do it." It acknowledges that there is a hierarchy of operators (adult males, then minors, then others), but it forbids stagnation. In your startup, you are likely hoarding tasks because you believe only you—or a high-cost consultant—can handle them. You are confusing "optimum" with "mandatory."

The Rambam is teaching us that the failure to execute is a greater ethical breach than the imperfection of the executor. If the "expert" is absent, you don't wait for the market to move on without you; you empower the next available resource to ensure the mission succeeds. You are in the business of completion, not just curation. If you aren't willing to delegate the "sacred" tasks of your business to the capable, even if they aren't the "traditional" choice, you aren't building a company—you’re building a bottleneck. It’s time to move from being the gatekeeper of every detail to the architect of the outcome.

Analysis

Insight 1: The Principle of Functional Competence vs. Status

The Rambam establishes a clear hierarchy: "Although a father is commanded... if he is not present... it may be performed by another person." This is a masterclass in organizational design. The mitzvah (the mission) is the primary directive. The father (the founder) has the primary responsibility, but the system must be robust enough to survive his absence.

In business, we often conflate "personnel status" with "functional competence." We assume that only a VP or a C-suite executive can handle a "Level 1" task. The text disagrees. It allows a minor, a slave, or a woman to perform the act if the primary actor is unavailable. The decision rule here is simple: If the mission-critical output is at risk of not happening, the barrier to entry for the operator must be lowered to the level of competence required to complete the task, not the status of the person who usually does it. You do not stop the line because the foreman is out; you train the operator to finish the work.

Insight 2: Completion as the Ultimate KPI

"Nevertheless, if he does so [a gentile], there is no need for a second circumcision... because the deed has already been completed." This is a jarring, hard-truth moment for any founder. The Rambam acknowledges that the actor was "wrong" (a gentile should not be allowed), yet the result is valid and irreversible.

The insight for you: Stop obsessing over the "how" when the "what" is already achieved. Many founders get caught in a loop of "re-doing" work because it wasn't done with their specific polish or by their specific vendor. If the customer is satisfied and the product works, stop wasting cycles on "re-circumcising" your own processes. If the goal is reached—the market is captured, the code works, the contract is signed—don't let your ego about "proper procedure" force you into a second, unnecessary cycle of labor. Respect the reality of the accomplished fact.

Insight 3: The Danger of "Splinters" (Quality Control vs. Perfectionism)

The text distinguishes between "strands of flesh that disqualify" and "strands that do not." It demands that the mohel remove the disqualifying strands even after he has "interrupted his activity," but it forbids him from returning to remove the minor, non-disqualifying ones.

Decision rule: Distinguish between "Blocking Defects" and "Aesthetic Friction." A blocking defect (a disqualifying strand) is anything that prevents the product from functioning as promised. That must be fixed, even if it disrupts your workflow. But the "non-disqualifying" strands? Leave them. Perfectionism is often just a form of vanity. When you spend hours "polishing" a feature that the customer doesn't even see, you are violating the Rambam’s wisdom. Identify your "disqualifying strands" (the bugs that kill the product) and fix them immediately. Everything else is secondary. If you don't have a clear definition of what "disqualifies" your product, you are suffering from infinite loop syndrome.

Policy Move: The "Completion Audit"

The Policy: Implement a "Completion Audit" for every stalled project or initiative that has been waiting for "senior oversight" for more than 48 hours.

The Process:

1. Define the "Disqualifying Strand": Before any project begins, the project lead must define the minimum criteria for a successful output. What does the work have to do to be considered "done"?
2. The "Next-Available-Mensch" Clause: If the primary owner (the "Father") is unavailable for 48 hours, the project lead is empowered to delegate the task to the most competent person available, regardless of title or previous experience, provided they meet the minimum safety/quality threshold.
3. The "No-Redo" Rule: Once a project is marked "complete" by the delegated operator and meets the "Disqualifying Strand" criteria, it is officially considered "done." Management is strictly forbidden from "re-doing" the work for aesthetic reasons.

Why this works: It forces you to define what success actually looks like (the milah), rather than hiding behind the excuse of needing "perfect" resources. It creates a culture where the outcome is the hero, not the person who performed the task.

KPI Proxy: Time-to-Completion Variance. Measure the delta between when a project could have been finished by a secondary operator and when it was finished by the primary owner. If your variance is high, you are bottlenecking your own growth.

Board-Level Question

"If we were forced to execute our next major product milestone without our 'first-choice' team members, which specific aspects of the process would we classify as 'disqualifying strands' that we would absolutely stop the clock to fix, and which are merely 'aesthetic strands' that we would choose to ignore to ensure we hit the launch window?"

This question forces your leadership team to move away from the myth of perfection and toward the reality of strategic triage. It reveals whether your team understands the difference between a product that works and a product that satisfies their own pride. If they cannot answer, they are likely over-engineering the process at the expense of the market.

Takeaway

The Torah doesn't want you to be a perfectionist; it wants you to be a finisher. The Mishneh Torah confirms that the world is built by those who show up and get the job done, not by those who wait for the perfect conditions or the perfect person. Your job as a founder is to create a system where the "mitzvah" of your business—the value you provide to your customers—is achieved as efficiently as possible.

Stop waiting for the "ideal" to arrive. The "ideal" is often just a delay tactic for the insecure. Identify your disqualifying constraints, empower your team to clear them, and accept the "good enough" that actually works. Completion is the only metric that earns you the right to keep playing the game. Everything else is just noise.