Menachot 71

Hook

Every founder faces the "first-mover dilemma": Do you wait for the perfect signal—a signed contract, a validated product-market fit, a clear regulatory green light—or do you start reaping the harvest because the market won't wait?

In Menachot 71, we find the Sages debating the exact timing of when it becomes permissible to harvest grain. The text centers on the Omer offering, a ritual that acts as the "go-live" gate for the entire agricultural economy. You can’t consume the new crop until the offering is made. But what if your field is in a valley, or you need fodder for your livestock, or you have a social crisis—like a funeral or a need for study space—that demands immediate action?

The tension here is pure startup DNA: The conflict between strict adherence to the "launch protocol" and the pragmatic necessity of local survival. Some residents of Jericho decided they couldn't wait for the centralized Sages' approval to pile their grain. They moved, they acted, and they forced the Sages to reckon with their reality. As a founder, you are constantly balancing the "sanctity" of your roadmap with the messy, urgent needs of your team and your runway. This text teaches us that while protocols exist to maintain order, the Mensch knows when the protocol fails to account for the reality on the ground.

Text Snapshot

"The residents of Jericho... reaped the crops with the approval of the Sages and arranged the crops in a pile without the approval of the Sages, but the Sages did not reprimand them."

"One may reap crops in any field for fodder and feed it to an animal... And one may reap crops prior to the omer due to potential damage to saplings... and due to the place of mourning... and due to the need to create room for students to study."

Analysis

Insight 1: The Principle of "Local Exception" (Fairness)

The text notes that in Jericho, the residents operated under unique conditions: "The residents of Jericho, whose fields were categorized as irrigated fields in a valley, reaped the crops." They had a specific context that made the standard "wait for the Omer" rule economically destructive for them.

Decision Rule: Fairness is not about applying the same rule to every business unit; it is about recognizing when a specific team’s "micro-climate" renders a corporate policy obsolete. If your policy is forcing a high-performing team to watch their "crop" rot in the field, the policy is broken. You aren't being "fair" by holding them to the same standard as everyone else; you are being negligent.

Insight 2: Permission is a Lagging Indicator (Truth)

The Gemara highlights that the Sages "did not reprimand" the residents of Jericho even when they acted without explicit approval. Why? Because the residents were acting out of necessity. They were "truth-seekers" in the marketplace. They understood that the intent of the law was to ensure a sacred harvest, not to prevent the grain from being collected.

Decision Rule: Truth in business is found in outcomes, not in compliance. If your team violates a process but achieves the intended spirit of the company mission—and the company is objectively better off for it—do not reprimand them for the sake of your ego or the "integrity of the process." Process is a tool; it is not the product. If the tool is dull, replace it. Don't punish the worker for using their hands.

Insight 3: The "Fodder" Threshold (Competition)

The Sages argue over whether reaping fodder for animals counts as "reaping" the field. Rabbi Yehuda suggests a threshold: if the crop hasn't reached one-third of its growth, it’s not really "the harvest" yet. It’s just maintenance.

Decision Rule: Identify your "fodder" activities—the low-level, non-revenue-generating tasks that don't constitute "going to market." You can safely experiment, pivot, or adjust these without triggering the "official launch" constraints of your core product. You don't need a board resolution to change your internal workflow or test a small, non-critical feature. Only when you hit that "one-third" growth threshold—when the work becomes significant and competitive—do the strict institutional controls need to tighten.

Policy Move

The "Jericho Exception" Protocol

Stop treating every process deviation as a disciplinary event. Implement a "Jericho Exception" policy: If a team lead determines that a company-wide policy is actively causing loss (e.g., missed revenue, talent attrition, or operational waste), they are authorized to bypass the policy if and only if they document the "necessity" (the reason for the move) and the "outcome" (how the spirit of the goal was maintained).

• KPI Proxy: "Process-Deviation Ratio" (PDR). Track the number of exceptions taken vs. the success rate of those projects. If the PDR is high and the outcomes are positive, it is a signal that your core policies are outdated and need to be rewritten to reflect the new market reality.
• Process Change: Create a "Retrospective Review" for any team that acts without approval. If the outcome justifies the departure, the policy is immediately flagged for review by leadership. This keeps your operating manual living and breathing, rather than a fossilized document that traps your best talent.

Board-Level Question

"We have a set of protocols designed to protect the integrity of our 'harvest' (our core product/market position). However, are we currently sacrificing our 'fodder' (our ability to pivot, experiment, and maintain morale) because we are afraid to let our teams act without a 'Sages' approval'? Which of our current operating procedures is simply a 'pile of sheaves' that we are guarding, even though the grain has already rotted because we refused to allow the team to move when the timing was right?"

Takeaway

The Sages didn't reprimand the residents of Jericho because they recognized that when people act with integrity to solve a real-world problem, the "law" must bend. As a founder, your job is to build a system that encourages, rather than punishes, the intuition of your team. If your people are waiting for you to tell them when to harvest, you've already lost the season. Build the guardrails, but let them run.