Mishneh Torah, Forbidden Intercourse 1-2

Hook

The primary dilemma for any founder scaling a company is the transition from "we’re just getting started" (where culture is implicit and informal) to "we have a system" (where culture must be codified and enforceable). You likely started with a "do-it-all" team where trust was assumed. But as you scale, you face the "Founder’s Proximity Trap": assuming that your top performers, or those closest to the mission, don’t need the guardrails that apply to the rest of the organization.

In Mishneh Torah, Forbidden Intercourse 1:1, Maimonides (Rambam) addresses a startlingly similar structural issue: the necessity of the warning (hatra’ah). He notes: "Even if a transgressor was a Torah scholar neither execution or lashes is administered unless a warning was given." Why? To distinguish between the inadvertent mistake and the intentional rebellion. For a founder, this is the ultimate management KPI. You cannot fire for cause or pivot your strategy based on "feeling" that someone knows better. You must institutionalize the warning. Without a clear, documented warning process, your culture isn't a culture—it’s a guessing game. When you treat your inner circle as exempt from the documentation required for the rank-and-file, you aren't being "founder-friendly"; you are inviting existential rot.

Analysis

Insight 1: The Warning as a Scalability Protocol

Rambam’s insistence that even a Torah scholar requires a warning is a masterclass in risk management. The logic is that even the most knowledgeable person may not realize a specific rule applies to a specific situation. In business, this translates to the "Assumption of Intent." Founders often assume that because a VP of Sales "knows the values," they don't need a formal warning when they cross an ethical line. Rambam argues that the warning is the instrument that turns a gray area into a black-and-white liability. If you don't warn, you cannot judge. If you cannot judge, you cannot scale. Your policy must be: no disciplinary action is valid without a recorded, specific warning that the act violates an explicit policy.

Insight 2: Fairness in the Face of Presumption

Rambam writes: "When an established presumption... has been established, we judge accordingly even though there is no clear proof." This is the "Reputation Metric." If your organization has an established, 30-day "presumption" of professional conduct, you must defend it. If a high-performer is "presumed" to be a toxic influence because of their consistent behavior, you don't need a smoking gun for every single interaction to justify a move. You operate on the "weight of evidence" to protect the ecosystem. However, this is a dangerous power—it must be balanced by the requirement for process. You can act on presumption to protect the culture, but you must be able to articulate the pattern that led to that presumption.

Insight 3: The Danger of "Casual" Transgression

Rambam notes that even when a transgression is "casual" (without intent), the actor is still liable. In a startup, "I didn't mean to ignore the compliance checklist" or "I just didn't think about the conflict of interest" is a common defense. Rambam shuts this down: the impact of the act creates liability regardless of the intent. Founders must stop grading on a curve for "well-intentioned" mistakes that cause systemic damage. If your CFO "accidentally" ignores a financial control, the act is the failure, not the mindset. Your goal as a leader is to create a system where "casual" negligence is structurally impossible, because the cost of that negligence is high.

Policy Move

The "Warning-Record-Review" (WRR) Cycle.

You will replace all ad-hoc disciplinary conversations with a standardized WRR process.

1. The Warning: Any violation of company values (e.g., integrity, transparency, safety) requires a formal, written "Notice of Violation." This notice must state the specific rule broken and the expected standard.
2. The Record: This notice must be signed by the employee and stored in a central "Culture Log" accessible to the board or HR.
3. The Review: If the same or similar violation occurs after the warning, the "Rebellion" threshold is met. This triggers an automatic "Board-Level Review."

By forcing this documentation, you remove the "he said, she said" of founder-led management. It forces you to define what is actually a "capital offense" in your culture. It turns your subjective frustration into objective policy. If you find yourself unwilling to issue the warning, you have your answer: the policy is either too vague, or you are too afraid to lead.

Board-Level Question

"If we were audited by an external committee today, could we show that every single person who violated our core operating principles—from the newest intern to our highest-performing executive—received the exact same, documented warning process, or are we operating on a 'trust-based' system that is currently creating a liability black hole in our culture?"

Takeaway

You are not the exception to your own rules; you are the primary guarantor of them. Rambam’s framework shows that even the highest-level actors are subject to the same procedural justice as the lowest. If you allow a "scholar" or a "star performer" to bypass the warning process, you aren't being merciful—you are dismantling the moral architecture of your startup. Scale requires the cold, hard, and consistent application of the law. Document the warning, or accept the rebellion.