Mishneh Torah, Blessings 6

Hook

In the high-velocity world of startups, "moving fast and breaking things" is often celebrated as a virtue. We prioritize frictionless operations, radical efficiency, and the rapid elimination of anything that slows down the deployment cycle. Yet, founders frequently encounter a paradox: the more we strip away "process" to gain speed, the more prone we are to catastrophic, avoidable errors. We cut corners on legal compliance, skip rigorous documentation, or bypass internal quality controls in the name of agility.

The Mishneh Torah (Blessings 6) offers a striking, counter-intuitive insight for the modern builder. It mandates ritual hand washing before eating bread—not because the hands are visibly dirty, but because the ritual itself is a "protective measure" (Mishneh Torah, Blessings 6:10). In the startup context, this is the ultimate "founder dilemma": How do we maintain high-velocity execution while implementing the necessary friction—the "ritual"—that protects the organization from the unseen dangers of scale? Just as the Sages instituted washing to ensure that even unconsecrated daily bread was treated with the same intentionality as sacred food, a founder must decide which business processes are not mere red tape, but essential "sanctification rituals" that prevent the erosion of culture, trust, and long-term viability. If you treat your internal operations as disposable, you aren't just losing time—you are losing the ability to distinguish between a healthy organization and a chaotic one.

Text Snapshot

"Anyone who eats bread over which the blessing hamotzi is recited must wash his hands before and after partaking of it... Although a person's hands are not dirty, nor is he aware that they have contracted any type of ritual impurity, he should not eat until he washes both his hands."

"This is a Rabbinic mitzvah that we have been commanded by the Torah to follow, as [Deuteronomy 17:11] states: 'Do not stray from all the laws that they direct you.'"

"It is forbidden to treat the washing of hands with disdain. Our Sages have authored many commands and warnings about this manner."

Analysis

Insight 1: Friction as a Strategic Asset

Founders often view bureaucracy as the enemy of growth. However, the Rambam teaches that the Sages intentionally added layers of practice—washing hands for unconsecrated food—to instill a mindset of discipline. In business, "friction" is often viewed as a bug, but when applied correctly, it is a feature of high-performing teams. A "blessing" or a ritualized check-in is not meant to slow the product down; it is designed to slow the person down.

When you require a specific, non-negotiable process—like a pre-launch security review or a code-quality checkpoint—you are forcing a transition from the "instinctive" to the "intentional." The text notes that even if the hands are clean, the act is required (6:6). This is the key: Process is not meant to fix a broken state; it is meant to maintain a high state. You do not wait for a security breach to implement a compliance policy. You perform the ritual to prevent the breach from ever becoming a possibility.

Insight 2: The Power of "The Giver" (Agency)

The text emphasizes that water used for washing must come from "the power of a giver"—it must be poured by human agency, not by an automated or passive flow (6:10). This is a profound insight for modern leadership. In an era of AI-driven workflows and automated project management, it is easy to delegate the "sanctification" of your work to a tool.

The Rambam warns that if water flows into a trough via an automated system, it lacks the intentionality required for the ritual. For a founder, this means that the most critical cultural and ethical guardrails of your company cannot be fully automated. Your culture—the "purity" of your team’s output—requires the direct, active agency of leadership. When you delegate the core values of your company to a Slack bot or a passive HR portal, you lose the "power of the giver." You must remain the one pouring the water, signaling to the organization that these standards matter because you are making them matter.

Insight 3: The Danger of "Sodomite Salt" (Hidden Externalities)

The Rambam explains that one must wash after eating because of the risk of "Sodomite salt"—a harmful substance that could blind the eyes if left on the hands (6:17). This is a metaphor for the toxic externalities of business. You may have finished your "meal" (a successful product launch or a record-breaking quarter), but the process of achieving that goal often leaves residue—burnout, technical debt, or ethical compromises.

If you do not perform the "after-meal" ritual of reflection and cleanup, you risk "blinding" the organization. You might be unable to see the long-term consequences of your short-term wins. The mandate to wash after the activity ensures that you are not carrying the dangerous residue of a high-pressure sprint into your next phase of development.

Policy Move: The "Ritualized Review"

Replace your generic "Post-Mortem" with a Mandatory Intentionality Checkpoint (MIC).

• The Policy: Every project exceeding a $50k spend or 2 weeks of engineering time must undergo an MIC.
• The Process: Unlike a standard review that focuses on "Did we hit the goal?", the MIC requires the team to answer three questions:
  1. What "Sodomite salt" (unintended cultural or technical debt) did we create to get this done?
  2. Where did we cut corners on our "ritual" (internal standards) to save time?
  3. How will we "wash" this (remediate the debt) before the next project begins?
• The KPI: Track "Remediation Velocity"—the percentage of technical or cultural debt identified in an MIC that is cleared within the subsequent two-week sprint. If this KPI drops, the team is losing its "ritual" discipline.

Board-Level Question

"We are currently scaling at [X]% month-over-month. As we move faster, we have systematically removed 'friction' from our development process. Can we identify one specific, non-negotiable ritual or quality checkpoint we have abandoned in the last quarter that, while technically 'slow,' actually served as a critical cultural or technical guardrail for the company? Are we prepared to re-institute this, not because we must (due to failure), but because we choose (to maintain our standard of excellence)?"

Takeaway

True scale is not just speed; it is the ability to maintain high standards at high velocity. The Rambam teaches us that rituals are not obstacles to success—they are the very framework that makes success sustainable. By instituting "intentional friction," ensuring leadership agency in core processes, and cleaning up the "residue" of our achievements, we protect our companies from the blindness that inevitably comes from unexamined, unchecked growth. Don't just build; build Menschlich.