Mishneh Torah, Tefillin, Mezuzah and the Torah Scroll 9

Hook

Founders are obsessed with "scaling." We talk about it in terms of headcount, MRR, and market penetration, but we rarely talk about the structural integrity of our scaling. We assume that if the product is good, the organizational shape will take care of itself. We build fast, we add "columns" of employees and departments, and we hope the whole thing holds together when we roll it out to the market.

The Torah scroll—the most critical "product" in Jewish life—is a masterclass in constraints-based engineering. Maimonides doesn’t just tell the scribe to write the Torah; he mandates that the scroll’s dimensions must be perfectly balanced: "A Torah scroll should not be written in a way which causes its length to exceed its circumference, or its circumference to exceed its length."

In business, we often violate this. We have massive, bloated teams (circumference) trying to deliver a tiny, focused value proposition (length), or we have high-velocity, thin-margin projects (length) that have no structural support (circumference) to keep them from tearing. When the proportions are off, the scroll—your company—cracks. This text teaches us that scaling isn't just about growth; it is about maintaining a precise, calculated ratio between your internal capacity and your external output. If you don't do the math, you’re not scaling; you’re just stretching.

Text Snapshot

"A Torah scroll should not be written in a way which causes its length to exceed its circumference, or its circumference to exceed its length... After one writes the experimental column as one desires, one should measure the column with the rod... Once one knows the number of columns [for which there is space in the coil], one should calculate according to the scroll from which one is writing whether the entire Torah will be able to be contained in the number of columns there are in the coil." (Mishneh Torah, Hilchot Tefillin, Mezuzah and Torah Scroll 9:1, 9:5)

Analysis

Insight 1: The Principle of Proportionality (Constraint as Quality)

Maimonides insists that the scroll’s length and circumference must be equal. In a startup, this is your "Unit Economics of Operations." If your headcount (the coil/circumference) grows faster than your revenue-generating output (the length of the scroll), you have a structural failure. Most founders treat growth as an additive process—"we need more hands, so let’s hire." Maimonides argues for a calculated process. Before you write a single letter, you must know exactly how many columns fit on the parchment. If you don't know your capacity limits, you are not a manager; you are a gambler. Scaling requires ensuring that your internal infrastructure (the coil) is perfectly sized to support the amount of "content" (work/value) you intend to deliver.

Insight 2: The "Experimental Column" (Prototyping before Production)

The text demands a rigorous feedback loop: "One should take two or three other parchments [as an experiment] to check the size of one's writing." We often move to full-scale production based on a hunch. Maimonides mandates an MVP approach to the most sacred task. He forces the scribe to test the "size of the writing" (the density of the work) and recalculate before committing to the full scroll. If your current "column" (process) is too wide or too narrow for your goals, you adjust the script—the culture and the tactics—until the math reconciles. You don't just "go for it"; you iterate on the experimental column until the model holds. If the math doesn't work, don't start the scroll.

Insight 3: The Integrity of the Seam (Integration and Cohesion)

The text is granular about the physical construction: "When one sews the parchments together, one should use only sinews from a kosher species... space should be left between the staves and the columns... so that the parchment will not tear in the middle when the Torah is rolled." In business, the "seams" are your handoffs, your API integrations, and your cross-departmental communication. When these are weak or use the wrong materials (e.g., poor communication protocols, misaligned incentives), the organization tears under the stress of being "rolled" (distributed). You can have perfect content, but if your integration strategy (the sinews) is substandard, the product fails. Optimization is not just about the content; it is about the durability of the connections between your disparate units.

Policy Move

Implement the "Column-to-Coil Ratio" Audit.

Every quarter, leadership must perform a "Scroll Audit." You are prohibited from adding new hires (circumference) unless you can mathematically prove the "length" (output/value) of the new column justifies the physical space it occupies in the current scroll.

1. Define the Column: Identify your core output unit (e.g., tickets closed, features shipped, sales calls completed).
2. Measure the Density: Determine the current "font size" (efficiency). If you are adding columns (hiring) but the total length of the scroll (output) isn't increasing proportionally, you are forced to re-evaluate the "script"—your processes.
3. The "Sinew" Check: Audit the "staves"—the leadership and infrastructure holding the scroll. Are the connections between departments (the seams) designed for flexibility, or are they brittle? If your internal communication is failing, you are prohibited from scaling the "length" of your product until the integration (the stitching) is reinforced.

KPI Proxy: Revenue-per-Head-per-Process-Step. If this number drops, your scroll’s circumference is outstripping your length. Stop adding columns and re-calculate your script.

Board-Level Question

"If we were to map our current organizational chart against our core value-delivery pipeline, where are the 'tears'—the areas where our internal 'circumference' (overhead, meetings, management layers) has become disconnected from our 'length' (actual value delivered to the customer)? Are we prepared to cut back on the 'parchment' (excess resources) to ensure that when we roll this product out to the market, it doesn't snap under the weight of its own inefficiency?"

Takeaway

Scaling isn't about getting bigger; it’s about maintaining the perfect ratio between your capacity and your output. If you aren't calculating your "columns" before you start writing, you aren't building a company—you're just creating an expensive, unrollable mess. Balance your dimensions, test your columns, and ensure your seams are built to last.