Mishneh Torah, Eruvin 4

Hook

The greatest risk to a high-growth startup isn't the competitor across the street; it is the "silo effect" that calcifies within your own org chart. Founders often mistake physical proximity for genuine organizational alignment. They assume that because their engineers, sales team, and product managers sit in the same Slack workspace or physical office, they are working as a "single household." They are wrong.

In Mishneh Torah, Eruvin 4, Maimonides dissects the mechanics of communal living. He argues that the legal definition of a "household" isn't determined by who sleeps under the same roof, but by who eats at the same table. In a startup, your "table" is your shared incentive structure, your common mission, and your unified operational rhythm. When departments have their own separate "eruvin"—their own siloed OKRs, fragmented incentive schemes, and localized definitions of success—the entire organization loses its ability to "carry" the weight of its goals into the public domain of the market. You are effectively locked in your own individual courtyards, unable to collaborate on the collective mission because you have failed to formalize the alignment that turns a collection of individuals into a singular, functioning unit. This text is a masterclass in why "proximity" is a vanity metric, but "alignment" is the only thing that moves the needle.

Text Snapshot

"When the inhabitants of a courtyard eat at the same table—even though they have their own individual dwellings—they are not required to establish an eruv; they are considered to be the inhabitants of a single household."

"Similarly, the inhabitants of a courtyard who established an eruv together are considered to be [the members of] a single household."

"This is the governing principle: When a person who is forbidden to carry in his own domain passes through another domain, his passage causes carrying to be forbidden there."

Analysis

Insight 1: Proximity is Not Alignment

The Rambam notes that physical dwelling is secondary to the functional reality of eating together: "it is the place where a person eats, and not where he sleeps, that is most significant in defining his place of residence." In business, your "sleep" is your desk or your department. Your "eating" is your P&L accountability and your shared KPIs. If your sales team is incentivized for volume and your product team is incentivized for stability, they are not eating at the same table. You can have them in the same open-plan office (the same courtyard), but they remain separate entities. The lesson here is brutal: physical proximity without shared incentives creates friction, not community. As a founder, you must design "tables"—cross-functional squads or shared performance metrics—that force the organization to operate as a single household.

Insight 2: The Cost of Fragmented Ownership

The text warns that if people fail to join in an eruv—the symbolic act of pooling resources—they are forbidden from moving goods into the shared space. In a business context, this is the "silo tax." When team A doesn't "buy in" to the project of team B, they become a legal liability to the collective. The text states: "When a person who is forbidden to carry in his own domain passes through another domain, his passage causes carrying to be forbidden there." If a team is not aligned with the company’s central strategy, their mere presence in a cross-functional project will act as a drag, effectively blocking the flow of resources. You cannot force "carrying" (collaboration) if the underlying "eruv" (shared commitment to the outcome) isn't established first.

Insight 3: The Danger of the "Gatehouse"

Maimonides discusses the "gatehouse"—a structure that is neither fully inside nor outside—where ownership is ambiguous. In startups, these are your "middle-management" zones or "special projects" where accountability is murky. If you place your eruv (your strategic focus) in a gatehouse, you lose the benefits of the alliance. This means if you leave key operational decisions to committees or ill-defined cross-functional groups that lack clear executive sponsorship, you are effectively placing your company's growth strategy in a "gatehouse." The result? You haven't actually established a unified domain, and no one is empowered to move forward. Clarity of ownership is the only way to avoid the "gatehouse" trap.

Policy Move

The "Unified Table" Policy. Stop treating cross-departmental collaboration as an opt-in activity. Implement a "Unified Table" policy where, for any initiative involving more than two departments, success metrics must be aggregated into a single, shared KPI (e.g., a "Customer Lifetime Value" metric that holds both Product and Sales accountable, rather than two separate metrics for "Feature Velocity" and "Total Units Sold").

To formalize this, mandate that departments "contribute their loaf"—a specific, non-negotiable set of resources (personnel hours, budget, or data access)—to the joint initiative before work begins. If a department refuses to contribute to the shared KPI, they are effectively "outside the eruv" and lose the right to influence the project's direction. This creates a hard boundary: you are either at the table, eating from the same bowl, or you are not part of the household.

Metric Proxy: Cross-Functional Dependency Velocity. Measure the time it takes for two teams to reach consensus on a shared objective. If it takes more than 72 hours, your "eruv" is broken.

Board-Level Question

"Looking at our current organizational structure, are we operating as a single 'household' with a shared objective, or are we a collection of 'individual dwellings' that happen to share a courtyard, where every cross-departmental project requires a separate, fragile, and often failed negotiation of resources? Which of our current strategic initiatives are currently sitting in a 'gatehouse'—where multiple teams have access, but no single team holds the primary responsibility for the outcome?"

Takeaway

Alignment is not a cultural vibe; it is a structural mandate. As Mishneh Torah, Eruvin 4 teaches, you are only as strong as your ability to unify your domains. If you don't force the "eating at the same table" (shared incentives), you will perpetually face the "carrying" restriction (organizational gridlock). Build the table, demand the contribution, and stop letting silos masquerade as collaboration.