Mishneh Torah, Fasts 1

Hook

Founders are addicted to "the grind." We treat every market shift, competitive threat, or churn spike as a technical problem to be solved with more code, more sales, or more capital. We are masters of the "natural phenomenon" narrative: The market slowed down? That’s just macroeconomic cyclicality. Competitor X copied our feature set? That’s just the nature of the industry. We intellectualize our struggles to avoid looking at the mirror.

But what if your startup’s "difficulty" isn’t just a market condition? What if it’s a feedback loop? The Rambam, in Mishneh Torah, Fasts 1:2, delivers a stinging critique of this detached, hyper-rationalized mindset: "Should the people fail to cry out [to God]... and instead say, 'What has happened to us is merely a natural phenomenon and this difficulty is merely a chance occurrence,' this is a cruel conception of things."

This is the ultimate founder dilemma: Do you view your company’s distress as a series of random, external variables to be managed, or as a diagnostic signal requiring a pivot in your own leadership and culture? When you view a crisis as "merely a natural phenomenon," you rob yourself of the agency to change it. You become a passenger to your own company's decline. The Rambam argues that by refusing to see the "Divinely structured plan" (or, in modern parlance, the causal link between your internal culture and your external results), you guarantee that the current distress will simply lead to "further distresses."

If you are currently facing a Q3 revenue miss or a toxic team dynamic, stop blaming the external environment. This text is your permission slip to stop "grinding" for a moment and start "inspecting." The most effective founders don't just optimize their funnels; they optimize their character. If your metrics are failing, you aren't just facing a technical bug—you are facing a spiritual and organizational debt. Are you ready to stop treating your problems as "chance occurrences" and start treating them as the most important data points you've ever received?

Analysis

Insight 1: The Principle of "Distress as Diagnostic"

The Rambam states: "Whenever you are distressed by difficulties... cry out [to God]... for when a difficulty arises... everyone will realize that [the difficulty] occurred because of their evil conduct."

In business, we often separate "Operations" from "Ethics," assuming that a bad quarter is purely an operational failure. Rambam rejects this duality. He posits a direct correlation between the health of the organization and the "conduct" of its leadership. If your customer success team is failing, it’s not just a training issue; it’s a symptom of a culture that likely devalues the user. If your dev team is burnt out, it’s not just a hiring issue; it’s a symptom of a founder who has prioritized velocity over human sustainability.

Decision Rule: When a KPI dips (Churn, CAC, eNPS), never treat it as an external anomaly. Treat it as a diagnostic signal of an internal cultural "sin"—a misalignment of values or a failure in leadership integrity.

Insight 2: The "Cruel Conception" of Randomness

The text warns that attributing failure to "chance" is a "cruel conception of things." Why? Because if failure is random, you have no power. You are a victim of the market. If failure is causal—if it is a result of your own choices—then it is within your power to fix.

This is the most ROI-positive mindset shift a founder can make. If you tell your team, "The market is just tough right now," you foster helplessness. If you tell your team, "Our current market position is a result of the product choices we made six months ago," you empower them to make better choices today.

Decision Rule: Eliminate the word "unlucky" from your leadership vocabulary. In every post-mortem, mandate a search for the internal variable that allowed the external threat to succeed. If you cannot find a link between your actions and your result, you haven't looked deep enough.

Insight 3: The Necessity of Communal Alignment

Rambam emphasizes that the "sounding of the trumpets" is a communal act: "This rite should not be observed when an individual... is in distress, but only when a 'community' is affected."

Founders often try to "solve" company-wide crises in a vacuum, holding the weight of the company in their own office. But Rambam insists that for a difficulty to be resolved, the entire entity must participate in the "crying out." This isn't about group therapy; it's about transparency. When the company is in distress, the leadership must bring the reality of that distress to the community. You cannot pivot a culture if the culture doesn't know there is a problem.

Decision Rule: In times of crisis, move from "command and control" to "communal audit." If you are failing, show the metrics to your team. Let them see the "difficulty." When the entire team recognizes the gap between their output and the required standard, the "sounding of the trumpets" creates a collective urgency that no top-down directive can replicate.

Policy Move: The "Quarterly Integrity Audit"

To operationalize this, every founder should implement a Quarterly Integrity Audit (QIA). This is not a financial audit; it is a cultural and ethical post-mortem.

The Policy: On the first Monday of every quarter, the entire leadership team gathers for a "Day of Inspection." The objective is to identify the three biggest "distresses" the company faced in the previous quarter—not in terms of revenue, but in terms of organizational friction.

The Process:

1. Metric Mapping: For each distress (e.g., "Engineering missed the sprint deadline"), map it to a specific leadership failure (e.g., "We prioritized feature count over technical debt").
2. The "Trumpet" Session: Share the findings with the wider team. This is your "sounding of the trumpets." Admit where the strategy was flawed. This kills the "cruel conception" of randomness and replaces it with a "culture of accountability."
3. The Repentance/Pivot: Define one concrete policy change that addresses the internal cause of the distress. If the issue was "lack of quality," the policy isn't "work harder"; it is "we will delay the release of [X] to ensure [Y] standard."

Metric Proxy: Measure the "Internal Causal Attribution Rate"—a survey of employees asking: "To what extent do you feel our current challenges are within our control vs. external market conditions?" A high-performing, mensch-like culture will consistently score "Internal Control" higher.

Board-Level Question

When you present to your board, they will inevitably ask about the external environment: "How are you responding to the new competitor?" or "How are you handling the cooling VC market?"

Your strategic counter-question to the board: "We have analyzed the external threat, but I want to discuss the internal 'distress' that made us vulnerable to it. Based on our QIA, we identified that our decision-making speed was hampered by [X] internal process. What specific governance changes can we make to ensure that we are not just reacting to the market, but correcting the internal habits that made this threat so dangerous in the first place?"

This shifts the conversation from you being a victim of the board’s market concerns to you being a master of the company’s internal growth.

Takeaway

The Rambam’s Fasts teach us that failure is not a bug; it’s a feature of the system designed to wake you up. If you ignore the signal, you suffer the consequences. If you listen to the signal, you gain the clarity required to build something that lasts. You are not a victim of the market; you are the architect of your company’s reality. Stop sounding the alarm for the market, and start sounding it for your own integrity.