Shulchan Arukh, Orach Chayim 134:2-135:2

Hook

Founders, you're building something. You're scaling, you're hiring, you're chasing that next round. And then it hits: a conflict. A team member feels a process is unfair, a partner is pushing a shady deal, a competitor is playing dirty. Suddenly, your brilliant business strategy is staring down a messy ethical dilemma. You know you need to do the right thing, but what is the right thing when the stakes are this high? This isn't about being "nice"; it's about building a company that lasts, one that doesn't crumble under its own weight or from external pressure. The Shulchan Arukh, in its ancient wisdom, grapples with the precise mechanics of community order, responsibility, and fairness. It’s not just about ritual; it's about the operational DNA of a group. Today, we're looking at the seemingly simple act of handling a Torah scroll and the intricate rules around who reads from it. This isn't about theology; it's a masterclass in how to structure hierarchy, manage access, ensure competence, and maintain integrity within a shared endeavor. Think of the Torah scroll as your company's core IP, its mission statement, its very essence. Who gets to "present" it? Who gets to "interpret" it? How do you ensure the process is both respected and functional? This is where the rubber meets the road for founder ethics.

Text Snapshot

"One shows the writing of the Torah scroll to the people standing to one's right and to one's left, and then turns it to those in front of one and those behind one, for it is a mitzvah for all the men and women to see the writing and to bow and to say 'V'zot Hatorah...'"

"A Kohen reads first from the Torah, and after him, a Levite, and after him, an Israelite."

"The widespread custom is that even a Kohen who is unlearned reads before a great [Torah] scholar that is a Israelite [i.e., someone not a Kohen or Levite], as long as the Kohen knows how to read. For if he doesn't know how to read, how will he bless over the Torah [reading]?"

"If there was a Kohen and a Levi in the synagogue and the Kohen read [an aliyah], and [then] thinking that there is no Levi there and started blessing the Torah blessing a second time, we do not stop [the Kohen]."

"If there is no Levi in the synagogue, the Kohen that was called first blesses a second time and reads in place of a Levi, but not a different Kohen, so that [people] shouldn't say that the first one was invalid."

Analysis

These passages, seemingly focused on synagogue protocol, offer potent decision rules for navigating business challenges, particularly around hierarchy, expertise, and fair process. The core principle is balancing established order with functional competence, all while maintaining the integrity of the shared "asset" – in this case, the Torah, but for us, the company's mission and operations.

Insight 1: Fairness and Meritocracy – The "Kohen vs. Scholar" Dilemma

The text states: "The widespread custom is that even a Kohen who is unlearned reads before a great [Torah] scholar that is a Israelite [i.e., someone not a Kohen or Levite], as long as the Kohen knows how to read. For if he doesn't know how to read, how will he bless over the Torah [reading]?"

This is a direct confrontation with pure meritocracy. The "Kohen" represents a designated role, a position of inherent honor or authority by birthright (analogous to a founder or early employee with established seniority). The "great scholar" is the epitome of learned expertise, someone who has earned their standing through sheer competence. The rule here is counterintuitive: the designated role often trumps raw, unearned expertise if the designated person meets a basic threshold of competence.

Decision Rule: Designated Roles Trump Unproven Expertise, Provided Basic Competence is Met.

In a startup, this means that a founder, even if they aren't the most technically proficient engineer on a specific problem, might still hold decision-making authority over that area, provided they understand the fundamentals and can articulate the vision. It’s not about blind deference; it’s about respecting the inherent structure and ownership that was established early on. However, the crucial caveat is "as long as the Kohen knows how to read." This translates to: anyone in a position of authority must possess the foundational skills to execute or oversee their responsibilities effectively. If a founder can't grasp the basics of their core product or market, their "Kohen" status becomes irrelevant.

Metric Proxy: Time to Decision in Cross-Functional Projects. If a designated leader (e.g., Head of Product) is consistently bypassed or overruled by a more technically expert individual (e.g., a senior engineer) who lacks the formal authority, it indicates a potential breakdown in this principle, leading to slower, more conflicted decision-making. A longer time-to-decision could signal this issue.

Insight 2: Truth and Transparency – The "Showing the Scroll" Imperative

The text commands: "One shows the writing of the Torah scroll to the people standing to one's right and to one's left, and then turns it to those in front of one and those behind one, for it is a mitzvah for all the men and women to see the writing and to bow and to say 'V'zot Hatorah...'"

This is about radical transparency and shared ownership of the core "truth" – the Torah. It's not just about having the Torah; it's about showing it, making its content accessible to everyone. The physical act of turning the scroll ensures visibility across the entire assembly.

Decision Rule: Core Information Must Be Accessible and Visible to All Stakeholders.

This translates directly to how you communicate your company's vision, strategy, financials (appropriately anonymized, of course), and critical updates. Hiding information, even with good intentions, breeds distrust and disengagement. Founders must actively ensure that the "writing" of their business plan, their strategic pivots, and their core values are not just stored away but are actively presented and made understandable to the entire team. The "bowing and saying 'V'zot Hatorah'" is the collective affirmation of shared purpose.

Metric Proxy: Employee Engagement Scores related to understanding company direction and values. A decline in these scores could indicate that the "writing of the Torah" is not being adequately shown or understood by the congregation (employees).

Insight 3: Competition and Process Integrity – The "Who Reads Next" Rules

The intricate rules about who reads after a Kohen or Levi, and the specific scenarios for when a Kohen reads twice or a Levi is replaced, are about maintaining the integrity of the process and avoiding suspicion or perceived unfairness. For example, "If there is no Levi in the synagogue, the Kohen that was called first blesses a second time and reads in place of a Levi, but not a different Kohen, so that [people] shouldn't say that the first one was invalid."

This is a sophisticated approach to managing situations where the ideal process is disrupted. Instead of creating new ambiguities, the system prioritizes continuity and avoids raising questions about individual validity. It’s about protecting the reputation of individuals and the system itself.

Decision Rule: When a Process is Disrupted, Prioritize Continuity and Avoid Creating Suspicion of Individual Failure.

In business, this means if a key person leaves or is unavailable, the replacement process should be designed to avoid implying that the departing individual was "invalid" or incompetent. If a crucial deal falls through, the post-mortem should focus on systemic improvements, not finger-pointing that could damage individual careers and team morale. The goal is to reinforce the overall strength of the "Torah" (the company's operating principles) rather than singling out individuals for failure. This preserves the team's ability to function effectively in the future.

Metric Proxy: Rate of Voluntary Turnover in Key Roles. A high rate of turnover, especially if individuals leave under vaguely negative circumstances, could indicate that the "process of replacement" is creating an environment where people feel their "validity" is questioned, leading them to seek opportunities elsewhere.

Policy Move

Policy Name: "Core Mission Visibility Protocol"

Policy Description: To operationalize the principle of making core information accessible, we will implement a structured quarterly "Mission Deep Dive" session. This replaces ad-hoc company updates.

Process:

1. Quarterly "Torah Unveiling": The executive leadership team will dedicate one hour each quarter to a live, interactive session with the entire company.
2. Content Focus: This session will cover:
   • The "Writing": A clear articulation of the company's current strategic priorities and OKRs, directly linked to the overarching company mission. This is where we show the "writing."
   • The "Turning": A transparent overview of key performance indicators (KPIs) – both successes and challenges – that directly impact these priorities. This demonstrates the "turning" of the scroll to all parts of the congregation.
   • The "Bow and Say": A Q&A segment where employees can directly ask clarifying questions about the mission, strategy, and performance. This is the communal affirmation and engagement with the "Torah."
3. Accessibility: Recordings of these sessions will be made available on the company's internal knowledge base. Key takeaways and updated OKRs will be published in a central, easily accessible location.
4. Role of Leadership: Founders and executive leaders will be expected to present and participate actively, demonstrating a commitment to transparency and shared understanding. Failure to demonstrate basic competence in articulating these points (the "Kohen knows how to read" principle) will be a matter for executive coaching and development.

Rationale: This policy directly addresses the "Truth and Transparency" insight. By formalizing the presentation of core company information, we ensure that the "writing of the Torah" (mission, strategy, performance) is consistently and visibly shared with all stakeholders, fostering alignment and trust. It moves beyond passive communication to active engagement, mirroring the communal obligation to see and affirm the Torah.

Board-Level Question

"Given our current organizational structure and growth trajectory, how are we ensuring that individuals in designated leadership roles are demonstrably competent in their core responsibilities, and what mechanisms are in place to prevent situations where unproven expertise from outside these roles consistently overrides established decision-making authority, thereby risking operational paralysis and undermining the integrity of our defined roles, akin to the principle of a Kohen needing to know how to read before being called for an Aliyah?"

Rationale: This question probes the "Fairness and Meritocracy" insight. It forces leadership to articulate their strategy for balancing positional authority with functional competence. It’s about preventing a situation where a highly skilled individual, while valuable, destabilizes the established order by consistently bypassing or undermining those officially designated to lead. The analogy to the Kohen needing to read highlights that formal status is insufficient without basic capability, and that uncontrolled disruption of hierarchy can lead to confusion and inefficiency. It's a strategic question about organizational design and the practical application of authority.

Takeaway

Your company’s ethical framework isn't a separate department; it’s the operating system. The ancient wisdom of how to handle the Torah, a sacred text, reveals profound truths about how to manage your business. Prioritize transparently sharing your core mission and strategy ("showing the writing"). Respect established roles, but demand basic competence from those who hold them ("the Kohen knows how to read"). And when disruptions occur, design processes that preserve integrity and avoid creating suspicion. These aren't just good deeds; they are fundamental building blocks for a resilient, trustworthy, and ultimately, more profitable enterprise.