Arukh HaShulchan, Orach Chaim 253:33-39

Hook

You’ve scaled. You’ve brought in good people. You’ve defined your mission. Yet, that nagging fear persists: the one about the "accidental" screw-up. Not malicious intent, mind you, but the well-meaning, eager-beaver employee who, in their zeal to "hasten the cooking," inadvertently breaks a rule, cuts a corner, or compromises a core value. We're talking about the slip-up that costs you a customer, a compliance fine, or worse – your reputation. This isn't theoretical; it's the daily tightrope walk of every founder. How do you empower your team to innovate and move fast without creating a culture ripe for unintentional ethical breaches? How do you build systems that anticipate human nature, especially that "eagerness to eat" – or in your world, "eagerness to hit the KPI," "eagerness to close the deal," "eagerness to outpace the competition"?

This isn't about micromanagement. It's about designing a resilient organization. You've seen it: the engineer who skips a critical test phase to hit a deadline, convinced it'll be fine. The sales rep who bends the truth just a little to secure a major account, because "everyone else does it." The product manager who pushes out a feature with known privacy vulnerabilities, rationalizing it as "minimal risk" for "maximum impact." These aren't bad people. They're driven people operating within systems that either fail to protect them from themselves or, worse, implicitly encourage these "accelerations."

The Sages, in this week’s text, grapple with an identical founder's dilemma, albeit in a different context: how to allow productive activity before a period of restriction (Shabbat) without inviting transgression during that period. They understood that human nature, when left unchecked, will always seek efficiency, speed, and immediate gratification. Your challenge is the same: how do you design your company's "oven" and "fuel" systems so that "stirring the coals" – making a forbidden "fix" for immediate gain – becomes not just forbidden, but systematically difficult, if not impossible? This isn't about legalistic nitpicking; it's about building an ethical operating system that protects your people, your product, and your profit, precisely because it understands the inherent human tendency towards "eagerness." Fail to account for this, and your "eagerness to eat" will eventually eat your lunch.

Text Snapshot

The Arukh HaShulchan addresses the permissibility of starting a task on Friday that will continue into Shabbat: "a person may place a pot with food on the fire before Shabbat near nightfall, or meat in the oven or on coals, and they will continue cooking during Shabbat." However, it immediately introduces a critical caveat: "the Sages forbade certain practices, due to a decree lest one stir the coals on Shabbat in order to hasten the cooking." The rationale is clear: "in his eagerness to eat he might forget that it is Shabbat and stir the coals, thereby transgressing a Torah prohibition, for by stirring the cooking is accelerated and thus he would be cooking on Shabbat." Therefore, "the Sages established protective measures regarding this." The text then delves into the specific mechanics of ancient ovens and fuels, illustrating the deep analytical approach behind these safeguards.

Analysis

This text isn't a dusty historical footnote; it's a masterclass in proactive risk management and behavioral economics applied to ethics. The Sages aren't just saying "don't stir the coals"; they're dissecting why someone might stir them ("eagerness to eat") and how to prevent it through systemic design ("protective measures"). For founders, this translates directly into building resilient businesses that anticipate human nature and embed ethical guardrails, not as an afterthought, but as a core component of operational excellence. Let's unpack three critical decision rules.

Insight 1: Fairness – Design Systems to Preempt "Eagerness-Driven" Shortcuts that Undermine Equity

The Sages understood that "eagerness to eat" is a powerful motivator. In a business context, this translates to "eagerness to close," "eagerness to launch," or "eagerness to grow." This isn't inherently bad; it drives innovation. However, unchecked, this eagerness can lead to shortcuts that compromise fairness – to customers, employees, or the market. The core prohibition against "stirring the coals" is a preventative measure against gaining an unfair advantage (faster cooking) at a forbidden time.

The text states: "the Sages forbade certain practices, due to a decree lest one stir the coals on Shabbat in order to hasten the cooking." This isn't merely about avoiding a religious transgression; it's about maintaining a level playing field, even against one's own desires. Imagine a sales team operating under immense pressure to hit quarterly targets. An individual, driven by "eagerness to close," might offer a preferential discount not available to others, or misrepresent a product feature to secure a deal. While seemingly a "win" in the short term, this action "hastens the cooking" by bypassing established fair-pricing or truth-in-advertising policies. The immediate benefit (closing the deal) comes at the cost of fairness to other customers and, ultimately, the company’s long-term reputation for integrity. Such actions erode trust, which is the bedrock of sustainable customer relationships.

Consider the startup environment where "growth at all costs" can lead to bypassing standard quality assurance or security protocols. An engineer, in their "eagerness to launch," might push code to production without adequate testing, hoping to fix bugs later. This "stirring the coals" accelerates development but introduces instability and potential vulnerabilities, unfairly burdening end-users with a subpar or insecure product. The initial "acceleration" is a form of unfairness, pushing the risk onto others.

Decision Rule for Fairness: Implement "friction-by-design" mechanisms in critical processes to prevent individuals from unilaterally "stirring the coals" for personal or team gain at the expense of fairness. This means designing processes where shortcuts are not just discouraged, but structurally difficult to execute without proper oversight or explicit authorization. For example, any deviation from standard pricing or terms requires multi-level approval and documented justification. Any code deployment must pass automated tests and peer review before reaching production.

Metric/KPI Proxy: Customer Trust Score (CTS). While subjective, this can be tracked through NPS, sentiment analysis of customer feedback, and churn rates. A decline in CTS or an increase in customer complaints related to perceived unfairness (e.g., inconsistent pricing, product misrepresentation, unaddressed bugs) would indicate that "eagerness-driven" shortcuts are undermining your commitment to fairness. The goal is to identify and mitigate behaviors that compromise fairness, ensuring that growth is achieved through equitable practices, not through "stirring the coals" for short-term gains that erode long-term trust.

Insight 2: Truth & Transparency – Build Guardrails Against Self-Deception and Rationalization

The text highlights the danger of "forgetting" in "eagerness": "in his eagerness to eat he might forget that it is Shabbat and stir the coals." This "forgetting" isn't necessarily malicious; it's a form of self-deception or rationalization born from intense desire. In business, this translates to individuals "forgetting" the full implications of their actions or rationalizing minor deviations from truth or transparency for perceived short-term benefits.

When a founder is under immense pressure to secure funding, there's a temptation to "forget" to disclose certain risks or to "stir the coals" by presenting projections with an overly optimistic spin, knowing they might not be fully achievable. This isn't outright lying in many cases, but it's a subtle bending of the truth, a selective transparency born of "eagerness to close the round." The "forgetting" here is not an oversight but an active suppression of inconvenient truths. This "stirring of coals" creates an accelerated, but ultimately fragile, path forward because it's built on a foundation that isn't entirely truthful.

Similarly, in product development, a team might "forget" to document a known bug or a security vulnerability, prioritizing a rapid release over complete transparency. They rationalize that the bug is minor, or the vulnerability is low-risk, and can be addressed in a future update. This "stirring the coals" accelerates time-to-market but compromises the integrity of the product and the company’s commitment to its users. When issues eventually surface, the lack of prior disclosure erodes trust and can lead to significant reputational damage, not to mention increased regulatory scrutiny.

The Sages' concern about "forgetting" speaks to the human capacity for motivated reasoning, where our desires influence our perception of reality. To counteract this, "protective measures" are essential. These measures aren't just about preventing external deceit, but internal self-deception that leads to a departure from integrity.

Decision Rule for Truth & Transparency: Implement mandatory, independent verification and disclosure protocols for high-stakes information and decisions. This means creating a system where critical claims, projections, or disclosures are reviewed by someone not directly invested in the outcome, specifically to counter the "eagerness-driven" tendency to "forget" or rationalize. For example, all investor decks must undergo a "truth audit" by an internal compliance or finance team member who can challenge assumptions and ensure full disclosure of risks. All public-facing product claims must be validated by a separate technical or legal team.

Metric/KPI Proxy: Disclosure Completeness Score (DCS). This can be quantified by tracking the number of material disclosures made in investor communications, product documentation, and public statements, cross-referenced against potential risks or known issues. A higher DCS indicates greater proactive transparency, while a low score, especially when coupled with later discovered issues, suggests "eagerness-driven" "forgetting" or rationalization. The goal is to ensure that information shared, whether internally or externally, is not just accurate but also complete and balanced, guarding against the human tendency to omit inconvenient truths when driven by powerful incentives.

Insight 3: Sustainable Competition – Prioritize Robust Systems Over Short-Term "Hasting" to Build Lasting Advantage

The text's detailed discussion of oven types (kirah, kupach, tanur) and fuels (straw, gefet, wood) reveals a deep understanding of the mechanics of cooking and heat retention. This isn't just trivia; it's critical to understanding why certain "protective measures" are needed. A tanur, which "retained heat far more than the kupach" and was "stoked...more intensely," would naturally present a greater temptation to "stir the coals" due to its inherent efficiency and intensity. The Sages understood that different systems (or business models) have different inherent risks and require tailored safeguards.

In the competitive landscape, every founder is looking for an edge. The temptation to "hasten the cooking" – to get to market faster, capture more share, or beat a competitor to a feature – is immense. However, the Sages teach that shortcuts born of "eagerness" are unsustainable. "Stirring the coals" for immediate acceleration might yield a temporary lead, but it often comes at the expense of building robust, ethical, and scalable systems. True competitive advantage doesn't come from forbidden "hasting," but from superior, compliant, and sustainable operational design.

Consider a company that cuts corners on data privacy or security to rush a new AI product to market. This is "stirring the coals" – an attempt to "hasten the cooking" of market dominance. While they might gain an initial lead, this approach is fundamentally unsustainable. Regulatory fines, data breaches, and public backlash will inevitably erode that advantage. Their "tanur" (their advanced tech) might be powerful, but without the "protective measures," it becomes a liability. Competitors who invested in robust privacy-by-design from the outset, even if slower to market, build a more resilient and trustworthy product that will ultimately win in the long run.

Another example: a company that engages in aggressive, potentially misleading marketing tactics to quickly acquire customers. This "stirring the coals" might inflate user numbers short-term, but it damages brand equity and customer loyalty. Authentic, value-driven marketing, while slower to "cook," builds a loyal customer base that is far more durable and defensible. The Sages, by focusing on the inherent properties of the cooking methods, highlight that the foundation matters. If your foundation is built on shortcuts, it will eventually crumble.

Decision Rule for Sustainable Competition: Prioritize the development of robust, ethically compliant systems and processes, even if it means a slower "cooking" time. Recognize that true competitive advantage stems from sustainable practices, not from "stirring the coals" for temporary gains. Invest in infrastructure (technical, legal, ethical) that is designed for longevity and resilience, rather than sacrificing it for speed.

Metric/KPI Proxy: Compliance & Integrity Risk Score (CIRS). This can be a composite metric tracking internal audit findings, external regulatory compliance checks, security vulnerability reports, and ethical incident reports. A lower CIRS indicates a more robust and compliant system, even if it means a slightly slower initial time-to-market. The goal is to demonstrate that the company is investing in "protective measures" that ensure its growth is sustainable and defensible, rather than relying on "eagerness-driven" shortcuts that create long-term liabilities. This score directly reflects the health of your foundational systems and their ability to withstand the pressures of competition without resorting to "stirring the coals."

Policy Move

The Arukh HaShulchan's core lesson is about designing "protective measures" to prevent "eagerness-driven" transgressions. The specific details about kirah, kupach, and tanur ovens aren't just historical; they illustrate the Sages' deep understanding of how varying technical configurations (your business systems) influence the likelihood of human error or temptation. They don't just ban "stirring the coals"; they analyze the conditions under which it's most likely to happen and create safeguards tailored to those conditions.

Inspired by this, I propose implementing a "Pre-Mortem Ethical Review for High-Impact Initiatives" (PERHI) policy. This policy is a direct "protective measure" against "eagerness to eat" leading to ethical shortcuts in critical business decisions.

Policy Name: Pre-Mortem Ethical Review for High-Impact Initiatives (PERHI)

Policy Objective: To proactively identify and mitigate potential ethical risks, compliance breaches, or fairness compromises associated with new products, significant features, market entries, or strategic partnerships before significant investment or launch, specifically guarding against "eagerness-driven" rationalizations and shortcuts. This ensures that the company's "cooking" process is robust and ethical, preventing the need to "stir the coals" later.

Process Overview: For any initiative categorized as "High-Impact" (defined as potentially affecting >100,000 users, involving >$1M investment, or having significant regulatory, privacy, or safety implications), a mandatory PERHI session must be conducted. This is not an approval gate but a structured foresight exercise.

1. Mandatory Trigger: Any project lead proposing a High-Impact Initiative must initiate a PERHI request at the 70% planning completion stage. This timing is crucial – early enough to pivot, late enough to have substantive details, preventing "eagerness" from pushing a half-baked plan.
2. Diverse, Independent Panel Formation: A PERHI panel will be assembled, comprising 3-5 individuals not directly involved in the project. This includes representatives from Legal/Compliance, Ethics/HR, a senior leader from an unrelated department, and potentially an external advisor (e.g., a privacy expert). Their independence directly addresses the "eagerness to eat" and "forgetting" concerns, as they have no personal stake in the project's immediate success.
3. "Future Failure" Scenario Brainstorm: The core of the PERHI. The panel and project lead(s) will assume the initiative has catastrophically failed (e.g., massive data breach, regulatory fine, public outcry, discriminatory impact). They then "work backward" to identify why it failed, specifically focusing on ethical missteps, overlooked risks, or instances where "eagerness to hasten the cooking" led to shortcuts. Questions include:
   • "What shortcuts did we take in our 'eagerness to launch' that led to this disaster?"
   • "What information did we 'forget' or rationalize away regarding privacy/fairness/security?"
   • "How did our focus on speed overshadow our commitment to truth or equity?"
   • "Which 'coals' did we 'stir' that led to this catastrophic 'burning'?"
4. Risk Catalog & Mitigation Strategy: All identified failure pathways are cataloged. For each, the team must propose concrete "protective measures" (e.g., additional testing, enhanced disclosure, new compliance checks, independent audits, extended pilot phases). This is the direct equivalent of the Sages establishing "protective measures" to prevent the stirring of coals, tailored to the specific "oven" (your initiative) and its "fuel" (its operational characteristics).
5. Documentation & Accountability: All PERHI findings, identified risks, and proposed mitigation strategies are formally documented and become part of the project plan. The project lead is accountable for integrating these "protective measures" into the execution roadmap. This documentation serves as an explicit record of anticipated ethical challenges, making it harder for future "eagerness" to lead to "forgetting."

Justification & ROI: This policy, while adding a step, is a strategic investment. It directly addresses the "eagerness to eat" by creating a structured pause and forcing a critical, independent ethical lens before problems manifest. It's cheaper to fix a design flaw on paper than to remediate a breach or reputation crisis post-launch. The Sages didn't prohibit placing the pot on the fire; they introduced safeguards around the process. This PERHI is that safeguard.

KPI Proxy: The effectiveness of PERHI can be measured by the "Ethical Risk Reduction Score (ERRS)" for High-Impact Initiatives. This score would track the number of identified ethical risks per PERHI session versus the number of actual ethical incidents (e.g., reported violations, compliance fines, negative press related to ethics) post-launch for those same initiatives. A high number of identified and mitigated risks during PERHI, coupled with a low number of actual incidents, indicates the policy is effectively preventing "eagerness-driven" ethical lapses. This is a direct ROI on proactive ethical design: preventing costly failures by systematically identifying and neutralizing the temptation to "stir the coals."

Board-Level Question

The Sages' deep dive into the mechanics of ovens and fuels (kirah, kupach, tanur) and their specific heat retention properties is a masterclass in understanding the environmental factors that influence human behavior and the likelihood of "eagerness-driven" transgressions. They didn't just issue a blanket prohibition; they analyzed the underlying conditions. A tanur, which "retained heat far more than the kupach," inherently presented a different set of risks and temptations. This granular understanding allowed them to craft nuanced "protective measures."

At the board level, this translates into a critical strategic question: "How are we systematically analyzing the 'heat retention properties' of our organizational systems and processes – our equivalent of the kirah, kupach, and tanur – to proactively identify and mitigate the specific points where 'eagerness to hasten the cooking' is most likely to lead to ethical or compliance shortcuts, and what specific 'protective measures' are we building into those high-risk areas?"

This isn't a simple "do we have an ethics policy?" question. It's about a foundational shift from reactive compliance to proactive ethical engineering. Many companies have a generic ethics code, but few deeply analyze where their specific operational structures, incentive systems, and cultural norms create "hot spots" for ethical compromise. Just as the Sages knew a tanur's intense heat made "stirring the coals" more tempting, your board needs to understand which parts of your business are inherently "hotter" – i.e., where the pressure for speed, profit, or market dominance is so intense that "eagerness" becomes a significant liability.

Consider:

• Sales Incentives (the "Tanur"): If your commission structure aggressively rewards short-term sales at the expense of long-term customer fit, you've created a "tanur" that encourages "stirring the coals" (e.g., aggressive selling, misrepresentation). What "protective measures" (e.g., clawbacks for early churn, multi-year customer value metrics, mandatory ethics training with scenarios) are embedded to counteract this "eagerness"?
• Product Development Cycles (the "Kirah"): Rapid release schedules with insufficient QA or security reviews create a "kirah" where engineers might "forget" to fully test or document vulnerabilities in their "eagerness to launch." What "protective measures" (e.g., mandatory security champions, independent audit gates, "friction-by-design" for critical releases) are in place?
• Data Handling & AI Development (the "Kupach"): The pressure to leverage new data streams or deploy AI models quickly can lead to "stirring the coals" around privacy, bias, or data ethics. What "protective measures" (e.g., privacy-by-design, ethics-by-design principles, independent AI ethics review boards, mandatory data provenance documentation) are preventing this "hasting"?

The board needs to understand that "protective measures" are not one-size-fits-all. A policy effective for a "kirah" might be insufficient for a "tanur." This question challenges leadership to move beyond superficial compliance and engage in deep operational analysis, linking ethical risk directly to business processes and human psychology. It demands that they identify their company's unique "cooking methods" and design bespoke safeguards, not just generic rules. The ROI here is profound: a company that proactively understands its "heat retention properties" and builds intelligent "protective measures" will foster a more resilient, trustworthy, and ultimately more valuable enterprise, precisely because it anticipates and neutralizes the insidious pull of "eagerness."

Takeaway

The Arukh HaShulchan isn't just an ancient legal text; it's a foundational lesson in proactive, systemic ethical design for any founder. The Sages understood that human nature, specifically "eagerness to eat," is a powerful, often subconscious, driver that can lead to "forgetting" boundaries and "stirring the coals" for immediate gain. Your job as a founder isn't just to set rules, but to build an "ethical operating system" that anticipates these tendencies.

This means designing "protective measures" into your core processes – not as an afterthought, but as an integral part of your "oven" and "fuel" system. Implement "friction-by-design" where shortcuts could compromise fairness. Mandate independent review to guard against self-deception and ensure truth. Prioritize robust systems over short-term "hasting" to build sustainable competitive advantage. When you deeply analyze the "heat retention properties" of your specific business functions and craft tailored safeguards, you're not just preventing "accidental" transgressions; you're building a more resilient, trustworthy, and ultimately more profitable enterprise. Ethical design isn't a cost center; it's an ROI multiplier, securing your long-term success by understanding and honoring human nature itself.