Mishneh Torah, Sabbath 16

Hook

You’ve spent millions on a massive office or a high-end platform, but your users aren't engaging. You’ve built the "space," but you haven't built the "habitation." The real founder dilemma: Is your infrastructure serving your mission, or are you just managing empty square footage?

Text Snapshot

"If the walls surrounding it are ten handbreadths or more high, it is considered to be a private domain... [but] we are not allowed to carry within it, unless its area is equivalent to that necessary to sow two seah [of grain] or less... If its area is larger than the space necessary to sow two seah, we may not carry more than four cubits within it." Mishneh Torah, Sabbath 16:1

Analysis

Insight 1: Scale Without Purpose is Liability

The Rabbis set a limit (the seah measurement) on how much space you can "carry" in. If an area is large but lacks the intent of "habitation," it’s treated as a public space where your personal influence doesn't apply. Decision Rule: If you can’t map your product's features to specific user outcomes, you are managing a "large area" that will eventually drain your resources.

Insight 2: Intention Defines Jurisdiction

Rambam emphasizes that tearing down a wall and rebuilding it for "habitation" changes the legal status of the space Mishneh Torah, Sabbath 16:16. Decision Rule: You can’t fix a broken product culture by just adding features. You must redefine the intent of the space—re-enclose the problem with a clear, user-centric purpose.

Insight 3: The "L’vud" Principle of Influence

The principle of l’vud (a gap of less than three handbreadths is treated as solid) Mishneh Torah, Sabbath 16:18 teaches that small, consistent actions near a boundary consolidate your influence. Decision Rule: Don't chase massive pivots; focus on tightening the gaps in your existing core offering.

Policy Move

The "Utility Audit": Every quarter, audit your platform/office space. If a feature or area is not being used for its stated "habitation" (the core KPI), it is not an asset—it is a carmelit (a gray area). Either re-purpose it to fit your core mission or decommission it to prevent feature bloat.

Board-Level Question

"Are we building a larger 'enclosure' to satisfy vanity metrics, or is every square inch of our current product contributing directly to user-intent and habitation?"

Takeaway

Don't scale for the sake of size. Scale for the sake of utility. If your users aren't living in your platform, your walls are just fences.