Mishnah Oholot 7:5-6 · Startup voice, On-ramp

Hook

You are scaling a startup, and you hit a "dead body" problem. It isn’t a literal corpse, but it functions like one: a failed product line, a toxic legacy integration, or a key hire that turned out to be a career-ender. The dilemma isn't just about the failure; it’s about containment. How do you ensure the rot doesn't spread to the healthy parts of your organization?

In Mishnah Oholot 7:5, the Sages discuss the mechanics of "uncleanness" moving through space. If a corpse is in a house with ten doors, and one is opened, the contamination is localized. If you don't manage the flow, you lose the whole structure. Founders often fail here because they lack the "architectural" courage to seal off the dead weight. They keep the doors open, hoping the contagion will magically evaporate, only to find that the entire house—their culture, their runway, their reputation—has been rendered unclean. To be a Mensch in business is to know exactly where the wall is, how to seal the hatch, and when to prioritize the living over the dead. This is the art of strategic separation.

Analysis

Insight 1: Containment is an Architectural Responsibility

The text notes: "If there was a single upper story [built] over two houses, that one becomes unclean but all upper stories above it remain clean" Mishnah Oholot 7:5. This is a masterclass in modularity. In business, you must build your systems to be firewalled. If your billing system is the "corpse"—the source of technical debt or regulatory non-compliance—it shouldn’t be structurally connected to your core user experience.

Decision Rule: Never allow a single "upper story" (an initiative or a department) to be anchored to multiple "houses" (separate business units or customer segments) if one of those units is prone to failure. If you haven't built the walls to contain the risk, you are effectively choosing to let the whole building fall when the first unit fails.

Insight 2: Intention Alters the Scope of Risk

"If he intended to carry out the corpse through one of them or through a window... he protects all the other doors" Mishnah Oholot 7:6. The Sages here argue that your pre-existing plan for how you exit a failing project dictates the spread of the damage. If you have an "exit strategy"—a clear, documented way to dispose of a failing asset—the rest of your operation remains functional. If you have no plan, the chaos spreads to every "door" (every communication channel, every stakeholder relationship).

Decision Rule: Do not wait for the crisis to decide how to handle the disposal. The "intention must have been formed" Mishnah Oholot 7:6 before the crisis peaks. Your SOP for "sunseting a feature" or "terminating a partnership" is the only thing standing between a localized problem and a company-wide infection.

Insight 3: The Priority of the Living

The text reaches a brutal, binary conclusion: "If a woman is having trouble giving birth, they cut up the child in her womb... because her life comes before the life of [the child]" Mishnah Oholot 7:6. This is the ultimate founder’s trade-off. There are times when a project (the child) is so compromised that continuing to sustain it will kill the company (the mother).

Decision Rule: When the "greater part" of the entity has not yet emerged (the project is not yet fully viable in the market), the health of the parent company must be the absolute priority. You do not sacrifice the entity for the sake of an unviable limb. Sentimentality in business is a luxury that costs lives.

Policy Move

The "Isolation Protocol" (IP) Implement a mandatory "Failure Firewall" policy for every project with a budget exceeding 15% of ARR.

1. Modular Architecture: Any high-risk project must be isolated in the tech stack and the P&L as if it were a separate legal entity.
2. The Kill-Switch Trigger: Every project must have a pre-defined "Exit Hatch"—a specific set of KPIs that, if not met, trigger a 48-hour mandatory shutdown process.
3. Documentation of Intent: Before the project starts, the leadership team must sign a "Departure Document" outlining how the project will be excised without affecting core services.

Metric/KPI Proxy: Time-to-Isolation. If a project begins to show symptoms of failure (e.g., negative ROAS for three consecutive weeks), how long does it take for leadership to fully sever its connection to the main revenue-generating stream? Your goal should be under 72 hours.

Board-Level Question

"Looking at our current portfolio of initiatives, which one of our projects is effectively 'unclean,' and if we were to 'open the door' today to remove it, have we already built the firewalls necessary to ensure the rest of our operations remain 'clean'?"

This question forces the board to confront the reality that they are currently holding onto a failing asset that is potentially leaking toxicity into the healthy parts of the firm. It shifts the conversation from if we should cut it to how we have protected the rest of the business from the inevitable fallout.

Takeaway

On this day of Shmini Atzeret, we are reminded of the gathering of the community and the completion of cycles. In business, cycles must end so the community can flourish. Do not let the "uncleanness" of a failed idea, a poor hire, or a bad market bet linger in your halls. Build your walls, define your exits, and prioritize the survival of the whole over the sentimentality of the parts. A Mensch knows that sometimes, the most ethical thing you can do is execute a surgical, clean separation to save the living.