Mishneh Torah, Blessings 11

Hook

Founders are addicted to "the grind." We view our daily operations—hiring, product shipping, compliance, and even mundane administrative tasks—as purely functional. We treat them as necessary evils to get to the "real" work. But here is the silent killer of startup culture: The "Doer" Trap. When you view your work as a series of disconnected, utilitarian chores, you lose the narrative arc of your company. You stop seeing the why and start drowning in the how.

Maimonides (Rambam) in Mishneh Torah, Blessings 11, forces a radical reframe. He demands that we acknowledge the intent behind every action before the action is performed. He distinguishes between tasks that are mandatory "obligations" and those that are "voluntary activities." In the startup world, this is the difference between building a product because you are legally bound by a contract, and building a culture because you choose to define the standard. If you are operating without a "blessing"—a conscious, articulated intention that links your daily labor to a higher organizational purpose—you aren't building a company; you are just performing labor. You are performing "mitzvot" (meaningful actions) without the context of the mission. This chapter isn't about liturgy; it’s about aligning your daily execution with your long-term strategic vision. If you don't define the why before you commit the resources, you have already failed.

Text Snapshot

"There are positive commandments that a person is obligated to make an effort to pursue [their fulfillment] until he performs them... There are other mitzvot that are not obligations, but resemble voluntary activities... A blessing should be recited before fulfilling all positive commandments that are between man and God... A person should always take care not to recite blessings that are not necessary, and should recite many blessings that are required." (Mishneh Torah, Blessings 11)

Analysis

Insight 1: The Principle of Pre-Commitment (Intentionality)

Rambam is clear: "A blessing should be recited before fulfilling all positive commandments." In business, this is the Rule of Pre-Mortem Alignment. Most founders wait until after a feature is shipped or a pivot is made to reflect on why they did it. That is too late. The "blessing" is the act of aligning your team’s intent with the organizational mission before the energy is spent.

If you don't articulate the why (the "blessing") before the what (the "mitzvah"), the action lacks legitimacy. This is why so many startups suffer from "feature creep"—they are building things without a prior blessing of strategic necessity. If you cannot explicitly state why a project serves the core mission, you shouldn't be building it.

Decision Rule: Every major initiative must have a "Pre-Blessing" document. If it cannot be linked to the core "commandment" (your mission statement), it is an unnecessary expenditure of resources.

Insight 2: Obligation vs. Voluntary Activity

Rambam distinguishes between what we must do (tefillin) and what we choose to do (building a guardrail). He notes: "A person is not obligated to dwell in a house that requires a mezuzah... instead, if he desires, he can dwell in a tent."

Founders often confuse "nice-to-haves" with "must-haves." You are not obligated to build a perfect office culture if you don't care about retention; you are not obligated to build a specific security feature if you don't care about enterprise compliance. But the moment you choose to enter that house, the obligation to perform the mitzvah (the work) follows.

Decision Rule: Stop calling everything "critical." Categorize your roadmap into "Core Obligations" (the non-negotiables of your business model) and "Strategic Options" (voluntary activities). If you adopt a voluntary activity, you must commit to its full execution; otherwise, don't enter the house at all.

Insight 3: The Danger of "In Vain" (Efficiency)

Rambam warns, "A person should always take care not to recite blessings that are not necessary." In the startup world, this is the Cost of Context Switching. Every time you "bless" a new initiative—every time you announce a new company-wide focus, a new OKR, or a new team structure—you are spending a finite amount of organizational trust.

If you "bless" everything, you bless nothing. If you pivot too often, your team stops believing in the sanctity of the mission. You are taking God's name in vain—you are taking your mission in vain.

KPI Proxy: Mission-to-Initiative Ratio. Track how many company-wide initiatives you launch per quarter versus how many you successfully complete. If the number of "blessings" (launches) exceeds the number of "mitzvot" (completed, high-impact executions), you are diluting your culture.

Policy Move: The "Blessing" Review

Implement a Pre-Execution Gate for every project exceeding $50k in burn or 4 weeks of engineering time.

The policy is simple: Before the project is greenlit, the project lead must present a one-page "Blessing Statement" to the leadership team. This document must answer three questions:

1. The Mandate: Which core company value or strategic pillar does this action fulfill?
2. The Scope: Is this an "Obligatory" action (essential to the product/business) or a "Voluntary" action (optional expansion)?
3. The Commitment: If we proceed, what are we committing to completing in full, and why is this the right time to "bless" this work?

If a project cannot satisfy these criteria, the "blessing" is denied. No resources are committed. This forces leadership to stop performing "empty" work and ensures that every ounce of the company’s energy is anchored in a defined intent.

Board-Level Question

"We are currently tracking 14 'strategic initiatives' across the organization. Maimonides teaches us that blessings should not be recited in vain, and that we must distinguish between the foundational obligations of the house and the optional add-ons. Looking at this list, which of these are our true 'obligations' to our core stakeholders, and which are 'voluntary' distractions that we are currently over-investing in? If we were to stop 'blessing'—to stop providing executive air cover and resources to—half of these initiatives today, would our core business model suffer, or would we simply gain the focus required to actually finish the work that matters?"

Takeaway

You are not just a manager of resources; you are a sanctifier of effort. Your job is to ensure that the work your team does is not just "work," but an expression of the company's core purpose. By demanding intentionality (the "blessing") before action, and by fiercely distinguishing between necessary obligations and voluntary noise, you preserve your team's energy and ensure that every action you take leaves the company stronger than you found it. Build with intent, or don't build at all.