Mishneh Torah, Leavened and Unleavened Bread 8-9

Hook

Founders are addicted to "the grind." We treat growth like a Seder plate: everything has a pre-ordained spot, every KPI is a ritual, and we assume that if we just follow the "best practices" manual, the outcome—success, scale, exit—is guaranteed. But look at the Mishneh Torah text. It isn’t just a dry list of instructions; it is a masterclass in intentional friction.

The Seder is designed to be inefficient. You pour wine but don't drink it. You bring the table in, then you take it away. You ask questions that, in many cases, you already know the answers to. Why? To pique curiosity. To stop the "autopilot" mode of the organization. As a founder, your greatest risk isn't a competitor; it’s the institutional blindness that sets in when your team stops questioning the "why" behind the "what." If your Q3 operations look exactly like your Q2 operations, you aren't scaling; you’re stagnating. The Rambam’s Seder is a system built to force a "reset" on the human psyche. The real founder dilemma is this: Are you building a company that functions, or a company that thinks? If you aren't introducing intentional, structural disruptions to your own "table," your team will eventually stop tasting the matzah and start just checking the boxes.

Analysis

Insight 1: The Principle of "Inconvenient Curiosity"

The Rambam notes: "The table is taken away from the person reciting the Haggadah alone... to arouse the children's curiosity" (Leavened and Unleavened Bread 8:1). In business, we optimize for friction-less UX and seamless workflows. We want everything to be "intuitive." But deep learning and high-level strategy require the exact opposite. If your internal meetings feel too comfortable, you are failing to lead. You need to "take the table away"—disrupt the status quo—to force your leadership team to articulate the "why" of your current strategy. If they can’t explain the mission without the slide deck, they don't actually own the vision.

• Decision Rule: Periodically reorganize your reporting structure or meeting formats. If a process has become "invisible" because it’s so habitual, it is no longer an asset; it is a liability.

Insight 2: Essential vs. Secondary Hierarchy

The text spends significant space distinguishing between the Paschal sacrifice (the "essential") and the Chagigah (the "secondary"), noting that "the blessing for the Paschal sacrifice does not free one of the obligation of the blessing for the offering" (Leavened and Unleavened Bread 8:9). Founders often treat every task—from Slack etiquette to product roadmaps—as equally weighted. This is a death sentence. You must categorize your company’s "mitzvot" (obligations) into those that define your soul (the core product, the customer promise) and those that are merely supportive.

• Decision Rule: If you are spending as much time on "secondary" administrative processes as you are on your "essential" value proposition, you are violating the hierarchy of growth. Audit your calendar: are your blessings (your attention) going toward the sacrifice or the garnish?

Insight 3: The "Memory" Metric (The KPI of Continuity)

The Rambam emphasizes: "Anyone who has not said these three things... has not fulfilled his obligation" (Leavened and Unleavened Bread 8:11). There are specific, non-negotiable milestones that define your company’s identity. If you cannot articulate your core "Passover" story—why you exist, what you survived, and where you are going—in a way that every employee can recite, you have lost the culture.

• Decision Rule: Your "NPS" of internal culture is whether your team can articulate the "Why" of your current pivot. If the story changes every time it passes through a new hire, your culture is leaking.

Policy Move: The "Seder Audit"

Implement a quarterly "Table Reset" policy. Take your most established, "this is how we do it here" process—the one that everyone is on autopilot about—and force a formal "Why" review.

The Process:

1. Stop: For one week, suspend the standard operating procedure (SOP) for that process.
2. Ask: Force the team responsible for it to present the "four questions": Why are we doing this? What does it commemorate (the original problem we solved)? What happens if we don't do it? And how is this different from how we did it last year?
3. Replace: If the answer is "because we always have," it is not a mitzvah; it is "chametz" (bloated process). Eliminate it or re-engineer it.

KPI Proxy: "Process Latency" – The time it takes for a new hire to explain the "why" of their workflow without referring to a manual. If the latency > 5 minutes, your documentation is too mechanical and not mission-driven.

Board-Level Question

"If we were to lose our primary competitive advantage tomorrow, which of our current ritualized processes would we be forced to abandon, and why are we still clinging to them today?"

This question forces leadership to distinguish between institutional memory (the core values that keep the company alive) and institutional baggage (the processes that were only relevant for the version of the company we were two years ago). If they can’t answer, they are "leavened"—puffed up with pride and process, but lacking the substance of the matzah.

Takeaway

Stop optimizing for comfort. The Rambam’s Seder is a reminder that leadership is the art of keeping the "story" alive through deliberate, uncomfortable, and highly intentional actions. If your company isn't periodically forced to reconcile its current actions with its founding purpose, you aren't leading; you’re just managing the drift. Be a Mensch, not a manager.