Mishneh Torah, Eruvin 4

Hook: The "Silo" Trap

As a founder, you know the frustration of "siloed" teams. You have brilliant engineers and sharp sales reps, but when they stop sharing a "table"—the metaphorical space where objectives align—the entire organization begins to fracture. You can’t build a unified culture if your departments are effectively living in separate, unlinked courtyards.

Text Snapshot

"When the inhabitants of a courtyard eat at the same table... they are considered to be the inhabitants of a single household." Mishneh Torah, Eruvin 4:1 "The rationale... is that all these dwellings are considered to be a single dwelling." Mishneh Torah, Eruvin 4:1 "This highlights the principle that it is the place where a person eats, and not where he sleeps, that is most significant in defining his place of residence." Mishneh Torah, Eruvin 4:1

Analysis: Decision Rules

1. Proximity is Not Unity

The text clarifies that physical proximity (sleeping in the same courtyard) is irrelevant to functioning as a unit. Only the act of "eating at the same table"—sharing resources and intent—creates a single household. In business, sitting in the same office isn't enough; you must define the "table" (the shared KPI or vision) that binds disparate teams.

2. The Power of Intentional Contribution

The law dictates that when people join an eruv (a legal mechanism for unity), they cease to be separate entities. By "collecting an eruv," individuals shift from competitors for space to partners in a domain Mishneh Torah, Eruvin 4:1. If your teams aren't collaborating, it’s because they haven't been asked to "contribute a loaf" to a shared, cross-departmental project.

3. Permission to Move

When unity is established, the friction of "carrying" (the restrictions on movement) disappears. When your teams are aligned on a shared mission, you no longer need to micromanage the boundaries between them. They become authorized to operate within the broader organizational domain.

Policy Move

Implement a "Shared Table" OKR: For any cross-functional project, forbid the use of department-specific metrics. Require a single, joint KPI that both teams own equally. If they don't have a shared "loaf" to bring, the project is not a unified effort and should be restructured.

Board-Level Question

"Are our teams effectively 'eating at the same table' by being incentivized by the same outcome, or are they merely 'sleeping' in the same office while operating under conflicting goals?"

Takeaway

Unity is an active, ongoing choice to share resources and goals. If your teams feel like they are in separate courtyards, don't blame the office layout—blame the lack of a shared table.