Daily Rambam · Startup Mensch · Standard
Mishneh Torah, Rest on the Tenth of Tishrei 3
Hook
Every founder eventually hits the "Exception Wall."
In the early days, your startup is a fluid, high-trust tribe. Decisions are made on the fly, and rules are non-existent. But as you scale, chaos threatens to tear the company apart. To survive, you write playbooks. You establish policies: strict travel budgets, standardized software procurement, rigid remote-work boundaries, and structured pricing bands. You tell yourself that standardization is the only path to operational leverage.
Then reality strikes.
Your star software architect—the one holding your legacy database together—demands to work from a beach in Bali for three months, violating your strict tax-compliance geography policy. Your enterprise sales lead insists on giving a 30% discount and custom SLA terms to a logo that could single-handedly secure your Series B, flying in the face of your "no custom contracts" mandate.
If you say no, you preserve the integrity of your rules but choke your growth and alienate your top talent. If you say yes, you trigger a cascade of ad-hoc exceptions that destroy policy credibility, breed resentment among the rank-and-file, and signal that your corporate governance is a paper tiger.
This is the founder's trap: The false binary between crippling rigidity and chaotic inconsistency.
Most modern management literature tells you to either "stay agile" (which is code for having no discipline) or "trust the process" (which is code for bureaucratic stagnation). Neither approach scales.
To build a high-performance, high-integrity enterprise, you need a third way. You need a framework for principled exceptions—a system that maintains absolute respect for the rule of law while building structured, objective, and role-appropriate safety valves.
This is not a new problem. Over eight hundred years ago, Maimonides codified the laws of Yom Kippur in his Mishneh Torah. Yom Kippur represents the ultimate, uncompromising boundary: a day of absolute self-affliction where basic human drives—eating, drinking, washing, and anointing—are completely shut down.
Yet, within this system of ultimate restriction, Maimonides outlines a highly sophisticated, hyper-logical matrix of exemptions. He details who must maintain the ban, who is permitted to bypass it, to what exact degree they may do so, and why.
By analyzing the mechanics of these sacred restrictions and their accompanying rabbinic commentaries, we can extract an ROI-minded, operationally rigorous playbook for managing exceptions in the high-stakes environment of a scaling startup.
Full Experience in the App
Listen. Chat. Go deeper.
Audio playback, interactive chevruta, Hebrew tools, and every daily learning track — only in Derekh Learning.
Text Snapshot
"It is forbidden to wash on Yom Kippur, whether using hot or cold water... One may not wash one's entire body, nor any individual limb...
A king and a bride may wash their faces: a bride so that she will not appear unattractive to her husband, and a king so that he will appear splendorous, as [Isaiah 33:17] states: 'Your eyes shall behold the king in his splendor.' Until when is a wife considered to be a 'bride'? For thirty days.
When a person is soiled with filth or mud, he may wash off the dirt in an ordinary manner without reservation...
A person who is going to greet his teacher, his father, or someone who surpasses him in knowledge... may pass through water that is neck-high without any reservation. [Moreover, after] he performs the mitzvah that he intended to perform, he may return to his home via the water. For if we did not allow him to return, he would not go...
Similarly, a person who goes to guard his produce may pass through water that is neck-high without any reservation... [but] in this instance, the person is not allowed to return through water on Yom Kippur."
— Mishneh Torah, Rest on the Tenth of Tishrei 3
Analysis
Insight 1: Role-Based Splendor and the Principle of Minimal Deviation
The text presents a striking exemption to the absolute ban on washing: "A king and a bride may wash their faces: a bride so that she will not appear unattractive to her husband, and a king so that he will appear splendorous..." Mishneh Torah, Rest on the Tenth of Tishrei 3:1.
To a modern egalitarian founder, this looks like elitist favoritism. Why does the C-suite (the King) or the fresh recruit/star performer (the Bride) get to bypass the rules of discomfort that everyone else must endure?
The answer lies in the structural function of the role, not the personal privilege of the individual. The King is not granted a loophole because he is "better" than his subjects. He is granted an exemption because his splendor is a critical public asset. If the King appears unkempt and degraded, the authority of the state dissolves, leading to anarchy.
The Bride is granted an exemption because the preservation of her relationship with her husband during the critical window of their first thirty days is vital to the long-term stability of the family unit. The exemption serves a systemic purpose: preserving the core value-generating interfaces of the community.
However, the Seder Mishnah on Mishneh Torah, Rest on the Tenth of Tishrei 3:1:1 immediately constrains this exemption:
"מזה נראה לענ"ד בס"ד דהידים אסורים לרחוץ אפי' המלך והכלה... דאף שהידים ג"כ הם גלויות, אבל הלא אפשר לו לכסותן ללבוש בתי ידים שלא יהיו נראות כלל..."
(From this it appears to my humble opinion... that washing hands is forbidden even for the king and the bride... for even though the hands are also exposed, it is possible to cover them by wearing gloves so that they are not seen at all...)
This is a profound operational constraint: The Principle of Minimal Deviation.
The King and Bride are permitted to wash only their faces. Why? Because the face is the un-coverable, primary interface of communication. The hands, while also visible, can be covered with elegant gloves of silk or gold.
Because an operational workaround exists (gloves), the policy exemption is strictly denied for the hands. The King does not get a blanket hall pass to wash whatever he wants; he is granted the absolute minimum variance required to maintain his functional "splendor."
Business Application
In your startup, you must distinguish between egoic perks and functional splendor.
Your public-facing executives, enterprise sales reps, and developer evangelists are your "Kings." Their "splendor"—their credibility, energy levels, and presentation quality—directly impacts your brand equity, enterprise trust, and capital-raising capacity.
If your VP of Business Development is flying red-eye flights to Europe to close a $2M deal and immediately walking into a board room, granting them an exception to your "coach-only" travel policy to book a business-class seat is not a luxury; it is a functional investment in their "splendor." If they show up sleep-deprived and disheveled, the company loses.
However, applying the Seder Mishnah’s rule of "gloves," you must ask: Is there a non-exempt workaround?
If your VP can fly out a day early and rest at a standard hotel (the "glove"), they do not get the business-class flight exemption. You only grant the policy variance when no alternative workaround can preserve the functional integrity of the role's public interface.
Furthermore, the exemption must be hyper-localized. The sales lead gets the travel upgrade (the face wash), but they do not get a variance on expense-reporting timelines or compliance training (the hands). They must still wear the "gloves" of standard corporate discipline where public splendor is not at stake.
Insight 2: Cleanliness vs. Pleasure — The Boundary of Remedial Intervention
Maimonides writes: "When a person is soiled with filth or mud, he may wash off the dirt in an ordinary manner without reservation" Mishneh Torah, Rest on the Tenth of Tishrei 3:1.
The commentary in the footnote clarifying this rule points to a foundational distinction in Talmudic ethics: "For it is only washing for the sake of pleasure that is forbidden, and not washing for the sake of cleanliness" Yoma 77b.
Sefer HaMenucha on Mishneh Torah, Rest on the Tenth of Tishrei 3:1:1 reinforces this by explaining that when an action is done to remove a negative state rather than to induce a positive, luxurious state, it bypasses the restriction entirely. It is categorized not as a violation of the day's self-affliction, but as a basic act of restoration.
This distinction between cleanliness (remedial maintenance) and pleasure (subjective luxury) is the ultimate diagnostic tool for founder decision-making.
- Cleanliness (Remedial): The removal of an external, negative friction that prevents baseline functioning.
- Pleasure (Luxurious): The addition of a positive, subjective comfort that exceeds baseline requirements.
Under Maimonides’ ruling, if you are covered in mud, you do not need to ask permission, consult a rabbinic authority, or feel guilt. You wash it off "without reservation" and in an "ordinary manner." You do not, however, use scented oils or enjoy a hot bath. You remove the mud, restore yourself to zero, and stop.
Business Application
Your employees will frequently come to you requesting policy variances. To maintain fairness and operational integrity, you must run every request through the Cleanliness vs. Pleasure Diagnostic:
| Category | Definition | Startup Example | Ethical Action |
|---|---|---|---|
| Cleanliness (Remedial) | Removing a structural blocker or toxic friction to restore baseline performance. | A key engineer's laptop is lagging due to heavy local builds; they request an off-policy, high-end workstation. | Grant Immediately. This is "mud." They are not seeking pleasure; they are seeking to execute their job without systemic friction. |
| Pleasure (Luxurious) | Adding subjective comfort or prestige beyond baseline operational needs. | An employee requests a specific brand of premium desk accessories or an upgraded workspace because it "fits their aesthetic." | Deny. This is "pleasure." Granting this breeds favoritism and degrades policy discipline. |
If a team member is burning out due to a severe personal crisis, granting them an un-accrued, paid leave of absence is "washing off the mud." It is restorative. It brings them back to baseline.
Conversely, granting an employee extra vacation days simply because they find the standard policy "constricting" is catering to "pleasure."
When you resolve "mud" issues, do it "without reservation." Do not make the employee feel like they are receiving a special favor. Cleanliness is a right of the functional worker; pleasure is a luxury that must be earned within the bounds of standard policy.
Insight 3: Underwriting the Journey — The Return Path of Strategic Sacrifice
Maimonides presents a fascinating operational asymmetry when dealing with physical barriers on Yom Kippur.
If a person must cross a dangerous, neck-high river to perform a high-value, communal, or relational duty—such as studying Torah, visiting their primary mentor, or honoring their father—they are permitted to wade through the water: "A person who is going to greet his teacher... may pass through water that is neck-high without any reservation" Mishneh Torah, Rest on the Tenth of Tishrei 3:1.
But the real genius of the text lies in the next line:
"[Moreover, after] he performs the mitzvah that he intended to perform, he may return to his home via the water. For if we did not allow him to return, he would not go..."
Mishneh Torah, Rest on the Tenth of Tishrei 3:1.
Now, contrast this with Maimonides’ ruling on commercial asset protection:
"Similarly, a person who goes to guard his produce may pass through water that is neck-high without any reservation... [but] in this instance, the person is not allowed to return through water on Yom Kippur."
Mishneh Torah, Rest on the Tenth of Tishrei 3:1.
Look at the structural difference between these two scenarios:
MISSION-CRITICAL JOURNEY (Mitzvah/Alignment)
[Home] ---> (Neck-High Water) ---> [Strategic Goal]
[Home] <--- (Neck-High Water) <--- [Strategic Goal] <-- RETURN PATH UNDERWRITTEN
TRANSACTIONAL JOURNEY (Asset Protection/Commercial)
[Home] ---> (Neck-High Water) ---> [Guard Produce]
[Home] X (Neck-High Water) X [Guard Produce] <-- NO RETURN PATH ALLOWED
Why does the community-builder get to return through the freezing, restrictive waters of Yom Kippur, while the commercial asset guard is forced to stay stranded in the fields until the holiday ends?
Because Maimonides is a master of human incentive structures.
If you ask a person to make an extraordinary, high-friction sacrifice for a value-aligned, long-term strategic objective (a "mitzvah"), they must be psychologically underwritten. If they know that after they cross the freezing river and complete the grueling task they will be left stranded on the other side, they will refuse to go in the first place.
The "return path" must be guaranteed upfront to unlock the courage required for the outward journey.
However, if the journey is purely transactional and self-interested—such as guarding one's personal financial assets (produce)—the incentive is already baked into the reward. The guard is protecting their own capital. They are willing to cross the river because they stand to gain or preserve direct financial value.
Because the commercial incentive is self-sustaining, the system does not need to underwrite their return path. They can stay in the muddy field. They made their economic calculation; they must bear the operational friction of their choice.
Business Application
This is the ultimate playbook for startup talent management during critical pivots, market expansions, or high-intensity sprints.
When you ask your team to perform a "strategic mitzvah"—such as relocating to a new city to launch a satellite office, working eighty-hour weeks to patch a critical security breach, or stepping down from a comfortable role to lead a highly risky, unproven R&D initiative—you are asking them to wade through "neck-high water."
If you want them to take that leap, you must explicitly, contractually, and culturally underwrite their Return Path.
If the R&D initiative fails, do they have a guaranteed landing spot back in their original department? If the international relocation doesn't work out after twelve months, will the company fund their move back home?
If you do not underwrite the return path, your best people will play defense. They will nod, smile, and quietly decline to take the strategic risks your startup needs to survive.
Conversely, when dealing with purely transactional, upside-driven activities—like a sales rep chasing a massive, high-commission enterprise deal, or an external contractor taking on a high-paying, short-term project—you do not underwrite their return path.
They are crossing the river to "guard their produce." Their incentive is their commission check or their contract fee. If the deal falls through or the project gets messy, they bear the downside of that risk.
Do not waste company capital or distort your policies to underwrite the safety of those who are already being compensated through direct, transactional upside. Save your "return path" underwriting for those making true, values-aligned sacrifices for the long-term equity of the enterprise.
Policy Move
The Principled Exception Protocol (PEP)
To eliminate the "Exception Trap" and establish a culture of high discipline and high agility, you must transition from ad-hoc, founder-dependent decision-making to a structured, audit-ready operational framework.
You will implement the Principled Exception Protocol (PEP). This policy codifies the distinctions Maimonides outlines—Face vs. Hands (Role Splendor), Mud vs. Pleasure (Restoration), and Mitzvah vs. Produce (Strategic Underwriting)—into a concrete, repeatable workflow.
EXCEPTION REQUEST SUBMITTED
│
▼
Is it "Mud" (Remedial)?
(Removing a critical blocker?)
├── YES ──> [GRANT IMMEDIATELY] (Wash off dirt in ordinary manner)
└── NO
│
▼
Is it "Splendor" (Role-Essential)?
(Public-facing interface trust?)
├── YES ──> Is a "Glove" (Workaround) available?
│ ├── YES ──> [DENY EXEMPTION] (Enforce workaround)
│ └── NO ──> [GRANT FACE-ONLY EXEMPTION] (Minimal deviation)
└── NO
│
▼
Is it a "Mitzvah" (Strategic Sacrifice)?
(High-risk, values-aligned task?)
├── YES ──> [UNDERWRITE RETURN PATH] (Contractual safety net)
└── NO ──> [DENY OR TRANSACTIONAL ONLY] (No return path underwritten)
Step 1: Establish the PEP Matrix in your Employee Handbook
Every request for a policy variance (e.g., budget, travel, remote work, compensation, tooling) must be formally submitted through your internal operations portal and categorized under one of three "Maimonidean Gates":
- The Restoration Gate (Mud): Is this request aimed at removing a toxic, non-operational blocker that prevents the employee from performing at baseline?
- Action: If verified, grant immediately and execute in an "ordinary manner" (no luxury, just resolution).
- The Splendor Gate (Face/Gloves): Is this request for a public-facing role where the company’s brand equity is directly tied to the employee's presentation?
- Action: Audit for workarounds ("gloves"). If a standard workaround exists, deny the exemption. If no workaround exists, grant the absolute minimum variance required to preserve the public interface.
- The Sacrifice Gate (Mitzvah/Return): Are we asking this employee to take on extraordinary personal or professional risk for a long-term, strategic company goal?
- Action: If yes, draft a formal "Return Agreement" that guarantees their professional, financial, or geographic landing spot if the venture fails.
Step 2: Establish the "Glove" Audit
Before any department head can approve a policy variance for an executive or top performer under the "Splendor Gate," they must submit a written Glove Audit. This is a simple, one-question form:
"What is the closest non-exempt workaround that allows this employee to maintain their professional efficacy without breaking policy, and why is this workaround insufficient?"
If the department head cannot answer this, the exception is automatically denied. This forces leadership to think creatively about operational workarounds rather than lazily defaulting to policy exceptions.
Step 3: Implement the "Return Agreement" Template
For any employee undertaking a high-risk strategic pivot (e.g., moving to a new country, transitioning to a highly volatile experimental product line), the HR department will attach a legally binding Return Rider to their contract. This rider explicitly outlines:
- The duration of the strategic sprint (the "crossing of the river").
- The definition of success and failure.
- The guaranteed "Return Path" (e.g., return to previous salary band, repatriation costs, guaranteed role reinstatement, or a set severance package if the role is eliminated during the pivot).
Metric/KPI Proxy: The Policy Drift Index (PDI)
To track the health of your operational discipline, your finance and operations teams will track the Policy Drift Index (PDI) on a quarterly basis.
$$\text{PDI} = \left( \frac{\text{Total Dollar Value of Off-Policy Approvals}}{\text{Total Operational Spend}} \right) \times 100$$
- The Target: Maintain a PDI of < 4%.
- The Guardrail: 100% of the off-policy approvals in that 4% bucket must be mapped to a formal PEP Matrix category (Mud, Splendor, or Mitzvah-Return). Any "unmapped" exception triggers an automatic internal audit of the approving manager.
Board-Level Question
The Strategic Alignment Assessment
To bring this level of ethical and operational rigor to your governance, present this question at your next board meeting:
"Are we currently asking our key executives and engineers to wade through 'neck-high water' for our most critical strategic pivots without explicitly underwriting their 'return path'—and are we mistakenly wasting company capital underwriting the return paths of purely transactional, upside-driven activities?"
Contextualizing the Board Discussion
As your startup scales, the board's primary job is capital allocation and risk management. However, boards often suffer from a fundamental misunderstanding of human risk tolerance. They assume that equity packages and cash bonuses are sufficient to motivate employees to take massive, existential risks for the company.
They are wrong.
When you ask an employee to take a highly risky, non-obvious career leap within your company, they look at the downside. They see the "freezing river." If they believe that failure means they will be quietly managed out of the company or left stranded in a dead-end department, they will choose the safe option. They will protect their "produce" and stay put.
By posing this question to your board, you force a critical strategic audit:
- Identify the "Neck-High Rivers": What are the 2-3 most critical, high-risk initiatives currently stalled in your pipeline? Is the delay caused by a lack of capital, or is it because your top internal talent is terrified of taking the lead and getting stranded?
- Audit the Safety Nets: Have we designed explicit "Return Paths" for our true strategic champions? If we are launching a new product line that might cannibalize our core business, have we guaranteed the career paths of the team we put in charge of it, regardless of the outcome?
- Eliminate Transactional Waste: Are we over-compensating or over-protecting sales reps, external consultants, or transactional hires who already have direct, performance-linked upside? Are we spending company capital to insulate people who should be bearing the risk of their own commercial pursuits?
By aligning the board on this distinction, you ensure that your risk-mitigation capital is spent exactly where it generates the highest strategic ROI: underwriting the courageous leaps of your core culture-bearers.
Takeaway
An ethical, high-performance startup is not one with zero exceptions; it is one with a rigorous, objective, and role-based framework for when those exceptions are made.
Maimonides' laws of Yom Kippur teach us that even under the most sacred and uncompromising boundaries, the preservation of systemic integrity requires structured safety valves. The King’s splendor must be maintained, but only to the minimal extent of his public face. The mud of operational friction must be washed away without reservation, but the luxury of subjective pleasure must be denied. The strategic risk-taker must have their return path guaranteed, while the transactional asset-guard must bear the weight of their own choices.
Stop managing your startup by ad-hoc compromises or blind bureaucratic rigidity. Implement the Principled Exception Protocol. Wash off the mud, protect your public-facing splendor, underwrite the return paths of your champions, and build an enterprise that is as disciplined as it is agile.
derekhlearning.com