Arukh HaShulchan, Orach Chaim 282:7-12

Hook

Founders are obsessed with optimization. You trim the stack, you shrink the CAC, and you relentlessly kill features that don’t move the needle. You have a "less is more" mentality toward product, but you often have a "more is more" mentality toward culture and stakeholder management. You think that adding—more meetings, more perks, more "inclusive" decision-making, more stakeholders in the room—is always a move toward "sanctity" or better outcomes. You believe that if you don't give every stakeholder a voice, you’re failing the mission.

But here is the brutal reality: Every time you add a stakeholder to a process, you aren’t just adding a perspective; you are adding potential "purposeless blessings"—noise that dilutes the core objective. You are facing the classic founder dilemma: When does the pursuit of inclusivity become an anchor on efficiency? When does the desire to keep your "laity" (your employees, investors, or early adopters) happy actually undermine the integrity of the work you’re doing?

The Arukh HaShulchan deals with the ritual of reading from the Torah, but it is effectively a manual on organizational scope creep. You have the "Levush" camp, which argues that more is always better ("We ascend in sanctity"). Then you have the pragmatists who realize that every addition is a potential liability, a risk of introducing something that wasn't instituted for the original purpose. The text hits the nail on the head: sometimes you have to look at a process—whether it’s a weekly All-Hands, a product roadmap, or a cap table—and realize that while you can add more, the overhead of managing those additions is a tax on the system.

The genius of this text isn't in the ritual; it’s in the resignation. The authorities realize that even when a process has drifted from its original, lean intent, if the "people will not listen" and there is no explicit prohibition, it is "not worthwhile to stand in argument." This is the founder’s ultimate test: distinguishing between a hill worth dying on and a cultural drift you must manage, not combat. If you fight every battle, you lose the war. If you let every stakeholder in, you lose the product.

Text Snapshot

"The Levush seemed to say that it is good to add to the number of people called to the Torah [a.k.a. 'hosafot']; he wrote regarding addition, 'We ascend in sanctity.' ... Some say that ... adding ascendants adds blessings, and is close to introducing purposeless blessings. These blessings were never instituted. ... The people will not listen to us, saying that they must add ascendants due to complaints by the laity... Since there is no prohibition involved, it is not worthwhile to stand in argument against it and to protest."

Analysis

Insight 1: The "Purposeless Blessing" Risk (Efficiency Thresholds)

The text notes that adding ascendants creates "purposeless blessings" (berachot l'vatala). In your business, this is the "meeting-about-a-meeting" phenomenon. Every time you add a layer to an approval process or invite a non-essential stakeholder to a decision-making forum, you are incurring a cost. You are creating a "blessing"—a formal ritual of validation—that wasn't part of the original, high-performance intent of that process.

Decision Rule: Before adding a stakeholder or a step to any workflow, ask: "Is this a necessary functional contribution, or is this just 'sanctity' signaling?" If the latter, you are introducing noise that will eventually paralyze your velocity. Your KPI for this is Cycle Time per Decision. If your cycle time increases without a corresponding increase in the quality of the outcome, you have introduced a "purposeless blessing."

Insight 2: The Fallacy of "We Ascend in Sanctity" (Scaling Culture)

The Levush argues that adding more people to the Torah reading increases holiness. This is the startup equivalent of thinking that "more communication" is always "better culture." Many founders fall into the trap of believing that radical transparency and universal inclusion in decisions equal a better, more ethical company. The Arukh HaShulchan pushes back, noting that "most authorities did not agree" with the idea that addition is an inherent good.

Decision Rule: Scale through clarity, not through consensus. Consensus is a low-latency killer. Sanctity—or in your case, company mission and excellence—is achieved through the rigor of the people involved, not the quantity of them. When you are deciding who gets a "seat at the table," prioritize competence and alignment over the desire to make everyone feel included. You aren't running a social club; you are running an engine.

Insight 3: The Pragmatic Pivot (Picking Your Battles)

The most profound insight is the realization that "the people will not listen to us." The authorities recognize that they have lost the cultural argument regarding the number of ascendants, and they choose to concede rather than protest because "there is no prohibition involved."

Decision Rule: Categorize your friction into "Prohibited" (Ethical/Legal/Core-Values Violations) and "Customary" (Workflow/Process/Preferences). If a team process is merely inefficient but not unethical, do not waste your political capital fighting it. Instead, manage it. If it isn't a hill worth dying on, don't build a bunker there. Save your "no" for the things that actually threaten the company’s integrity.

Policy Move

The "Sunset Clause" on Meetings and Governance.

To combat the tendency toward "purposeless blessings," implement a 60-Day Sunset Policy on all recurring cross-functional meetings and non-statutory governance committees.

Every 60 days, the meeting or committee is automatically deleted from the calendar. To reinstate it, the "owner" must submit a one-page "Value-Add Memo" to leadership answering:

1. What specific, high-stakes decision was made in this forum in the last 60 days?
2. What would be the measurable loss to the company if this forum disappeared?
3. Which "essential" stakeholders can be removed without affecting the output?

This policy enforces the Arukh HaShulchan’s logic: it forces a re-evaluation of whether the "addition" (the meeting or the stakeholder list) is actually serving the mission or if it’s just the "people wanting to ascend."

KPI Proxy: Meeting-to-Output Ratio. Track the total hours spent in recurring meetings vs. the number of shipping milestones or revenue-generating decisions documented. If the ratio climbs, you are experiencing "process bloat," and your sunset clause is the scalpel to trim the fat. This protects your most valuable asset: the focus of your A-players.

Board-Level Question

When you are reporting to your Board, don't talk about how many people you’ve hired or how many committees you’ve formed to "ensure alignment." That is the "Levush" mistake of thinking more is more.

Instead, ask this: "Which of our current organizational processes are we maintaining solely because the 'laity' expects them, even though they distract from our primary competitive advantage?"

This question shifts the conversation from operational vanity (we have 15 committees!) to strategic discipline. It forces the Board to confront whether they are encouraging you to build a bloated, "sanctified" organization that moves slowly, or a lean, lethal machine that hits its targets. If the Board pushes back, tell them you are optimizing for "purposeless blessing reduction." A Board that wants to win will respect that kind of focus. A Board that wants "sanctity" (read: comfort and slow, safe decisions) is a Board that doesn't understand the market you are in.

Takeaway

Founder-friendliness is not about being nice; it’s about being effective. The Arukh HaShulchan teaches us that there is a tension between the desire for expansion and the necessity of efficiency. Recognize when your stakeholders are asking for additions that aren't necessary for the mission. Don't fight the tide of "custom" unless it violates your core principles. But for the love of your company, stop adding "blessings" that nobody asked for. Keep the ritual lean, keep the mission heavy, and don't let the "laity" dictate the pace of your innovation.