Mishneh Torah, Eruvin 3

Hook

You think you’re running a "unified" company, but your teams are operating in silos. You have the windows, the doors, and the proximity—but without a formal eruv (a legal framework for shared space), you’re effectively locked out of your own organization’s synergy.

Text Snapshot

"If they desire to join in a single eruv, they may. This causes [the entire area] to be considered a single courtyard... If they desire, they may make two eruvim... [It is then forbidden] to carry from one [courtyard] to the other." Mishneh Torah, Eruvin 3:1

Analysis

1. Proximity is Not Integration

Just because two teams occupy the same office or Slack instance doesn't mean they are a single domain. Rambam teaches that physical access (a window) only grants the option to unify. Without a deliberate decision to "join in a single eruv," the default remains separation. Do not mistake shared space for shared operations.

2. The Logic of "Threshold"

The law distinguishes between a window (an opening) and a breach (a structural change). Mishneh Torah, Eruvin 3:10 suggests that once a breach exceeds a certain size (ten cubits), it’s no longer a wall—the boundary is nullified. In business, if your "walls" (processes, departments) are too porous, you lose the ability to manage distinct units. You either have a wall or an open floor plan; don't live in the middle, where you have the overhead of both but the benefits of neither.

3. The Power of Intent

Rambam notes that filling a trench with earth is seen as "permanent" because the intention is clear, whereas filling it with loose straw is not. Mishneh Torah, Eruvin 3:12 If your cross-functional initiatives are "straw"—temporary, easily moved, and lacking commitment—don't expect your teams to act like they are one company.

Policy Move

The "Alignment Eruv" Audit: Conduct a quarterly review of every cross-departmental "window." If two departments share data or personnel, force a "Single Eruv" agreement: define shared KPIs and joint accountability. If you aren't willing to merge the goals, treat them as separate domains and stop the friction of half-baked collaboration.

Board-Level Question

"Are our current organizational 'walls' actually barriers to efficiency, or are they providing the necessary structure to keep our teams focused? If we removed the barriers tomorrow, would we become a single, high-functioning entity, or just a disorganized mess?"

Takeaway

Integration is a legal and cultural act, not a physical byproduct. If you want your teams to carry value across the organization, you must formally establish the shared space in which they operate.

KPI Proxy: Cross-Departmental Velocity (Time taken to complete a project requiring >2 departments).