Mishneh Torah, Shofar, Sukkah and Lulav 6-8

Hook

You are running a startup, which means you are running a perpetual "first night of Sukkot." You are in a state of high-stakes, high-intensity construction where the "Sukkah"—your product, your culture, your vision—is supposed to be a permanent reality, yet it feels like a temporary shelter. The dilemma most founders face is the tension between obligation and sustainability.

Maimonides writes in Mishneh Torah, Sukkah 6:10: "During these seven days, he must consider his house as a temporary dwelling and the sukkah as his permanent home." This is the ultimate founder pivot. Most leaders live in a state of "uncomfortable dwelling." They are building, but they are distracted by the "wind," the "flies," the "smell"—the minor irritations that threaten to drive them back into the safety of their old, established ways (the "house").

The Torah is not asking you to ignore your discomfort; it is asking you to redefine your "home." The real founder dilemma is the "Rainy Day Syndrome." When the pressure mounts—the term sheet is pulled, the key hire quits, the growth plateaus—the instinct is to retreat to the familiar. Maimonides notes: "If rain descends, a person may enter his home." But when does the rain stop? When do you stop being a "startup" and start being a "stable company"?

This text teaches that there is a profound difference between a legitimate exemption (you are legitimately sick, or the environment is truly hazardous) and avoidance. The founder who stays in the Sukkah when it’s merely inconvenient, or even slightly unpleasant, builds a business that lasts. The founder who retreats at the first sign of a leak destroys the culture of endurance. You need to decide: Is your business a Sukkah—a fragile, intentional, high-growth structure—or is it a house that you are just camping in until something better comes along? Let’s look at the mechanics of this building process.

Text Snapshot

"A person who is uncomfortable [when dwelling in the sukkah] is freed from the obligation... A person who cannot sleep in the sukkah because of the wind or because of the flies, mites, or the like, or because of the smell... A mourner is obligated [to fulfill the mitzvah] of sukkah... A groom, his attendants, and all the members of the wedding party are freed... Emissaries charged with a mission involving a mitzvah are freed... A person should not take apart his sukkah after he finishes eating on the seventh day." (Mishneh Torah, Sukkah 6:2-3, 6:6, 6:11)

Analysis

Insight 1: The Principle of "Tashvu Ke’ein Tadur," or Scalability of Environment

Maimonides anchors the Sukkah in the principle Tashvu Ke’ein Tadur—dwelling in the sukkah must be comparable to living in one’s own home. In business, this is the rule of Cultural Scalability.

If you expect your team to work in a "Sukkah" (an agile, high-intensity, lean startup environment), you cannot force them into conditions that are objectively dysfunctional. Maimonides permits leaving if there are "flies, mites, or the smell." In your company, "flies" are toxic communication loops, and "smell" is a lack of transparency. If your "Sukkah" is fundamentally broken, you cannot demand loyalty to it. However, if the environment is merely different from their comfortable corporate "house," you must demand that they treat the startup as their permanent home.

• Decision Rule: If the dysfunction is systemic (the "flies"), fix the infrastructure before demanding performance. If the dysfunction is merely a lack of comfort (the "inconvenience"), enforce the standard.
• KPI: "Employee Sentiment of Structural Stability"—If your high-performers are complaining about the structure rather than the workload, you have a "Sukkah maintenance" issue, not a performance issue.

Insight 2: The Emissary Exception vs. The Mourner Obligation

Maimonides distinguishes between those on a mission ("Emissaries charged with a mission involving a mitzvah") and those in emotional distress ("A mourner is obligated").

In business, an emissary is a salesperson or a founder on the road closing a deal. They are exempt from the standard operational norms because their mission is the priority. But a mourner? They are still obligated. This is a brutal but necessary rule for leadership. Personal grief or internal crisis does not exempt a leader from their fundamental duty to the business. You must "compose yourself and concentrate your attention on the mitzvah."

• Decision Rule: Strategic mission-critical tasks (business development, fundraising) allow for operational flexibility. Internal emotional or cultural crises do not allow for a departure from core business duties.
• KPI: "Operational Continuity During Crisis"—Measure how many "core processes" (e.g., daily stand-ups, reporting) continue during high-stress periods. If they drop, you are failing the "Mourner" test.

Insight 3: The "Table" Rule—Integration of Assets

Maimonides states: "It is forbidden for a person to sit and eat with his head and the majority of his body inside a sukkah while his table is in his home." The table must be in the Sukkah.

This is the Alignment Rule. You cannot have your "Head" (Vision/Leadership) in the startup while your "Table" (Resources/Capital/Assets) is held back in your legacy or "safe" projects. If you are building a new product, it must have your full resources. If you are keeping your "table" in the "house," you are not actually in the Sukkah. You are effectively not performing the mitzvah at all.

• Decision Rule: Never split your resources. If you are pivoting, move the "table" (the budget and the talent) entirely into the new project.
• KPI: "Resource Allocation Concentration"—Calculate the % of total R&D and operating budget currently sitting in "experimental" vs. "legacy" structures. If it’s not 100% aligned, you are failing the "Table Rule."

Policy Move

The "Sukkah Integrity Check" (Quarterly Audit)

Every quarter, implement a mandatory policy called the "Sukkah Integrity Check." Unlike a standard performance review, this audit focuses strictly on the structural environment of your team.

The Process:

1. Identify the "Flies": Ask your team, "What is currently making this workplace 'uncomfortable' in a way that prevents you from doing your best work?" (Exclude salary/perks; focus on process, bureaucracy, and tools).
2. The "Table Alignment": As a founder, you must list your top 3 strategic priorities and then list exactly where the "table" (the budget/time/top talent) is located for each. If a priority is in the Sukkah (new project) but the budget is in the "house" (legacy), you must move the budget within 14 days or admit you aren't actually committed to that priority.
3. The "Mourner’s Protocol": Establish a clear policy for high-stress periods. Define which roles are "Emissaries" (permitted to skip standard meetings during high-stakes deals) and which roles are "Mourners" (expected to maintain full operational discipline despite internal team or personal stress).

This policy forces you to confront the reality that you cannot demand high-growth performance in a environment that is structurally misaligned. If your team is in a Sukkah (a lean, fast-paced environment), you must ensure the "Table" is there with them.

Board-Level Question

"We are currently running a high-intensity growth strategy, yet we continue to operate with legacy resource allocation—our 'table' is still in the 'house.' At what point does our refusal to fully transition our resources into our core growth initiatives constitute a failure of the 'Sukkah Integrity'—meaning, are we just camping in a new idea, or are we actually committed to building it?"

Takeaway

The Sukkah is the ultimate test of a founder’s conviction. It is not meant to be comfortable; it is meant to be intentional. Do not confuse the "wind and rain" of a startup—the inevitable market volatility—with a reason to abandon your structure. If your strategy is solid, protect the Sukkah. If your resources aren't in the Sukkah, you aren't actually in business. Be the leader who stays, eats at the table inside the structure, and treats the temporary as the permanent. That is how you build a legacy.