Mishneh Torah, Blessings 5

Hook

You’re scaling your team. You have high-performers and junior hires. The temptation is to treat everyone as a generic unit of labor. But if you don't map your team’s actual obligations, you end up with "hollow accountability"—where people go through the motions, but no one is truly responsible for the outcome.

Text Snapshot

"A person can only recite a blessing on behalf of another person if he shares an equal obligation himself... [but] the Sages placed the obligation on the child himself... in order to educate them to perform mitzvot." (Mishneh Torah, Blessings 5)

Analysis

1. The Principle of Equal Standing

Rambam establishes a hard rule: You cannot outsource your core responsibilities to someone who isn't equally accountable. In a startup, this is your "Founder-Level" rule. If you ask a junior hire to own a high-stakes decision they aren't equipped to bear, you aren't empowering them; you’re setting them up for a failure of execution. Decision Rule: Don't delegate "authority" without ensuring the "obligation" is matched.

2. Education vs. Obligation

The text distinguishes between "obligated by Torah" and "obligated by Rabbinic decree for education." You treat your senior partners differently than your interns. The intern is in "training mode"—they are performing the action to learn, not to satisfy the company's core mission. Decision Rule: Never mistake a "training exercise" for a "mission-critical KPI."

3. The Modesty of Scope

The text notes that when people are in doubt of their obligation, they shouldn't lead others. There is a strategic danger in over-extending a person’s role before they are ready. Decision Rule: If a team member’s "obligation" (role scope) is uncertain, do not place them in a position where they carry the accountability for the whole team.

Policy Move

Implement a "Responsibility Audit": Audit your recurring meetings. If you have "junior" staff leading "senior" initiatives without the requisite authority to actually deliver, stop it. Shift them to a "participation/observation" model until they demonstrate they can own the outcome.

Board-Level Question

"Are we delegating authority to people who are currently only in a training phase of their growth, and does this explain our recent drop in execution consistency?"

Takeaway

Accountability is binary. You cannot have someone "mostly" responsible. If they aren't obligated to the result, they cannot lead the team to it. Match the role to the obligation, not just the aspiration.