Mishneh Torah, Blessings 11

Hook

The founder’s dilemma is rarely a lack of vision; it is a lack of alignment. You spend your days building the "how"—the product, the cap table, the GTM strategy—but you often ignore the "why." In the startup world, we treat every action as a standalone transaction. We raise a round, we hire a VP, we launch a feature. We treat these as discrete, disconnected events. But the Rambam (Maimonides) in Hilchot Berachot (Laws of Blessings) suggests a more sophisticated operating system for life and business: the concept of succession.

When the text notes that certain blessings come "in succession to each other" (berachot hasumuchot lachaverta), it isn’t just discussing liturgical syntax. It is teaching a lesson on operational continuity. Founders frequently suffer from "Context Switching Fatigue." They view the morning stand-up, the board deck, and the customer discovery call as isolated islands of effort. They waste energy "starting" every conversation from zero, re-establishing their identity and intent. They fail to build a "succession" of purpose.

When you treat your business actions as isolated, you lose the compounding interest of your mission. You become a collection of disparate tasks rather than a coherent movement. The Rambam’s framework forces us to ask: Is my current action an independent event, or is it a continuation of the core commitment I made when I signed my incorporation papers?

If your work isn't "in succession" to your foundational values, you aren't scaling a company; you’re just performing a series of disconnected, high-stress chores. This text is your permission to stop reinventing your intent every hour. It teaches that once you set the "Blessed" (the intention) at the start of your day, that frame carries over. You don’t need to rewrite the mission statement every time you ship a line of code. You just need to ensure the sequence remains unbroken. If the sequence breaks, you’re just making noise. If the sequence holds, you’re building an institution.

Text Snapshot

"All blessings begin with 'Blessed [are You, God...]' and conclude with 'Blessed [are You, God...],' with the exception of the blessings that come in succession to each other... In this instance, the phrase 'Blessed...' which begins the first blessing in the succession, applies to the blessings that follow as well."

"A blessing should be recited before fulfilling all positive commandments... 'who has sanctified us with Your commandments and commanded us….' Where has He commanded us? In the Torah, which states: 'Act according to the judgment they relate to you.'"

"A person should always take care not to recite blessings that are not necessary, and should recite many blessings that are required."

Analysis

Insight 1: Operational Continuity (The Power of Succession)

The Rambam’s rule that "the phrase 'Blessed...' which begins the first blessing in the succession applies to the blessings that follow" is a masterclass in executive focus. In scaling a startup, the greatest "waste" is the lack of context retention. When a team loses sight of the original "blessing"—the mission, the vision, the initial reason for the existence of the company—they start treating every quarter as a restart.

Decision Rule: Define the "Primary Blessing" (The Mission) once. In every subsequent tactical meeting or product sprint, do not re-litigate your fundamental values. Treat the current action as an extension of the initial "blessing." If you have to re-justify your entire ethos in every board meeting, your culture is fundamentally broken. A high-performing organization is one where the "Blessed" (the intent) is established at the top, and every downstream task acts as a frictionless continuation of that initial commitment.

Insight 2: The Authority of Delegation (The "Act According to the Judgment" Rule)

The text asks: "Where has He commanded us [to fulfill Rabbinic mitzvot]?" The answer, "Act according to the judgment they relate to you," is the ultimate justification for a robust management layer. Founders often fall into the trap of "founder-dependency," feeling they must personally sign off on every pixel and every line of copy.

Decision Rule: Build a chain of legitimate authority. The Rambam argues that when you empower your Sages (or in your case, your VPs and managers) to make judgments, their commands become the organization's "blessings." If you have not empowered your team to make decisions that carry the weight of your "command," you are not a founder; you are a bottleneck. True leadership is creating a structure where the team’s judgment is as valid as the founder's original vision.

Insight 3: The Danger of "Blessings in Vain" (Resource Allocation)

"A person should always take care not to recite blessings that are not necessary." In a startup, a "blessing in vain" is the expenditure of high-value resources on low-value, non-obligatory "customs" or "vanity metrics." Founders love to chase features or marketing trends that are essentially "customs established by the Sages"—things we do because "everyone else does them," not because they are core to our obligation.

Decision Rule: Apply a "Blessing Test" to every initiative. If it’s not an obligation (not core to your product-market fit or your long-term value prop), stop "blessing" it with your time and capital. If you are unsure whether an initiative requires your attention, the Rambam’s rule is clear: "it should be performed without reciting a blessing." In business terms: execute it silently if you must, but don't waste your "sanctification" (your best talent and focus) on it.

Policy Move

The "Succession Protocol" for Product Sprints

Most startups suffer from "Sprint Drift"—where the daily work loses the connection to the original product vision. To implement the Rambam’s principle of berachot hasumuchot (succession), you will replace your current "Sprint Planning" with a "Succession Ceremony."

1. The Primary Blessing (The Setup): Every sprint cycle, the CEO/Founder must open the planning meeting by anchoring the current tasks to the "Primary Blessing"—the core mission/vision established at the founding. This establishes the "Blessed" header for the entire 2-week block.
2. The Succession Rule: Once the "Primary Blessing" is set, the team is prohibited from re-litigating the "Why" for every Jira ticket. The intent is carried forward. If a task does not naturally flow from the Primary Blessing, it is by definition a "blessing in vain."
3. Metric/KPI Proxy: "Context-to-Execution Ratio." Track the time spent in meetings discussing "What are we actually trying to do here?" vs. "How do we execute the next step?" A healthy company has a declining ratio. If your team is constantly re-justifying the mission, your "succession" is broken. Your goal is to move the team into a state of flow, where the blessings (the tasks) are linked to the initial commitment.
4. The "Blessing in Vain" Audit: At the end of each quarter, hold an "Audit of Customs." Identify three initiatives that were treated as "obligations" but were actually just "customs" (vanity features, unnecessary meetings, legacy processes). Kill them immediately. This frees up your "Blessing" capacity for things that actually matter.

Board-Level Question

"If our company's mission is the 'Primary Blessing' that anchors our work, which of our current strategic initiatives are simply 'customs' we are performing without a mandate, and which are true 'obligations' that deserve our full, focused, and sanctified effort? Are we currently wasting our 'blessings' on things that don't move the needle, and how much of our leadership energy is being spent on re-explaining the mission rather than executing within the succession of that mission?"

Takeaway

The Rambam teaches that you don't need to reinvent your purpose every day. You build it once, you "bless" it with intent, and then you ensure that every subsequent action is a continuation of that first, sacred commitment. Stop being a series of disconnected events. Start being a sequence. When you stop "blessing" the irrelevant, you finally have the bandwidth to build something that lasts.