Arukh HaShulchan, Orach Chaim 282:13-283:3

Hook

Every founder faces the "Feature Creep" trap. You start with a core product—lean, intentional, and focused on a singular value proposition. Then, the stakeholders arrive. Your early adopters, your board members, your loudest power users—they all want their "alaliyah," their moment on the stage, their specific feature request integrated into the core flow.

The Arukh HaShulchan hits on the exact psychological tension of the scaling phase: do you adhere to the original, lean architecture of your mission, or do you sacrifice structural integrity to appease the vanity of the crowd? The text deals with the practice of "adding" to the number of people called to the Torah, a seemingly minor liturgical adjustment that exposes the massive friction between tradition (core product) and stakeholder demands (market pressure). As a founder, you are constantly deciding whether to hold the line on your "sanctity"—the core value that makes your company unique—or to dilute it to keep the peace. The Arukh HaShulchan doesn’t just tell you to stick to your guns; it provides a masterclass in reading the room. It acknowledges that when the pressure from your "laity" becomes a systemic demand, fighting it is often a waste of capital. The question is no longer "Is this perfect?" but "Is this a hill worth dying on?"

Text Snapshot

"The Levush seemed to say that it is good to add to the number of people called to the Torah; he wrote regarding addition, 'We ascend in sanctity.' It does not appear so, though, from all of the authorities; it seems that they only permitted addition [and did not encourage it]."

"Some say that... adding ascendants adds blessings, and is close to introducing purposeless blessings... This argument is correct, but this opinion has never been accepted."

"However, what can we do? The people will not listen to us, saying that they must add ascendants due to complaints by the laity who wish to ascend to the Torah. Since there is no prohibition involved, it is not worthwhile to stand in argument against it and to protest."

Analysis

Insight 1: The Danger of "Purposeless Blessings" (Value Dilution)

The text raises a brilliant concern: "adding ascendants adds blessings, and is close to introducing purposeless blessings." In business terms, this is feature bloat. Every time you add a new "ascendant" (a feature, a service, a meeting, an extra layer of bureaucracy), you are invoking a "blessing"—you are making a promise to the user that this addition has value. If you add too many, you risk the bracha l'vatala (the blessing in vain).

When you dilute your product, you dilute the user's focus. The Arukh HaShulchan notes that while the logic against adding is "correct," the market reality often overrides the technical perfection. As a founder, you must distinguish between "feature bloat" that serves the product's growth and "vanity bloat" that serves the stakeholder's ego. If a feature doesn't drive your core KPI—your "sanctity"—it is a liability, not an asset.

Insight 2: The ROI of Conflict (Choosing Your Battles)

The most striking admission in the text is: "Since there is no prohibition involved, it is not worthwhile to stand in argument against it and to protest." This is a high-level strategic decision rule. Many founders waste their limited social capital fighting battles over minor features or office culture norms that do not violate their core ethics.

If a request from your team or investors does not violate your fundamental values (the issur), learn to let go. Protest should be reserved for integrity-breaking events. If you spend your authority protesting every minor deviation from your original roadmap, you will have zero leverage when you actually need to stop a catastrophic pivot. Measure your pushback against the impact on your bottom line. If the protest costs more in team morale or investor friction than the feature costs in "sanctity," let the "laity" have their moment.

Insight 3: The Custom That Spreads (The "Default" Trap)

The text observes that "this is the custom which has spread." In business, your "custom" becomes your culture. If you allow a small deviation today because it's "not worth the fight," you are setting a precedent for tomorrow. The Arukh HaShulchan is warning us that once the behavior becomes the "custom," it is almost impossible to roll back.

You must be intentional about what you allow to become standard practice. If you are going to concede to stakeholders, do so with clear boundaries. Frame it as an "exception" rather than a "new policy." If you don't track these concessions, you will wake up in two years with a product that is unrecognizable from the one you founded, and a culture that prioritizes stakeholder happiness over mission-critical performance.

Policy Move

The "Feature Sunset" Protocol. To combat the "adding ascendants" drift, implement a formal sunset policy for any non-core stakeholder request. Every time you concede to a stakeholder’s "vanity" request (like an extra meeting, a niche reporting requirement, or a low-value feature), attach a "sunset clause" to it.

The policy: "We will integrate this request to satisfy the current stakeholder demand, but it will be reviewed for ROI against our core sanctity metrics every 90 days." If it fails to move the needle on your primary KPI (e.g., Net Revenue Retention or Churn Rate), it is automatically sunsetted. This prevents "customs" from hardening into permanent, bloated infrastructure. It turns the "laity's complaints" into a data-driven experiment rather than a permanent drain on your resources. It respects the stakeholder's desire to be heard while protecting the "sanctity" of the firm.

Board-Level Question

"We are currently facing pressure to [add feature/make an exception/pivot slightly] to satisfy [Stakeholder Group]. While this does not violate our core ethical principles, it does dilute our focus. If we concede to this, what is the specific metric—the 'sanctity KPI'—that we will track to determine if this addition is creating value or simply creating noise, and are we prepared to sunset this if the data shows it's purely vanity?"

Takeaway

You are a founder, not a concierge. The Arukh HaShulchan teaches us that while you cannot fight every battle, you must be ruthlessly aware of when you are conceding to vanity. Don't let the "customs" of your stakeholders replace the "sanctity" of your mission. When you do concede, do it with an expiration date. Keep your product lean, your ethics firm, and your ego out of the way of your growth.