Mishneh Torah, Sacrificial Procedure 10-12

Hook

Founders often treat "process" as an afterthought or an administrative burden. They optimize for speed, forgetting that the way you execute a task defines the culture of the entire organization. The Rambam shows us that in the Temple, the "how" was as sacred as the "what."

Text Snapshot

"The priests eat the sacrifices and the owners receive atonement. This also applies to other sacrifices... partaking of them is a mitzvah." Mishneh Torah, Sacrificial Procedure 10:1. "If there was only a small amount [of sacrificial meat], ordinary food... should be eaten with it so that it will be eaten in a satisfying manner. If there is a large amount... ordinary food... should not be eaten with it so that one will not have overeaten." Mishneh Torah, Sacrificial Procedure 10:11.

Analysis

Insight 1: Efficiency isn’t just speed

Efficiency is appropriateness. The text mandates that one should not overeat or under-consume, but rather consume in a "satisfying manner" Mishneh Torah, Sacrificial Procedure 10:11. In business, this means your processes should be calibrated to the scale of the task. Over-engineering a small project is as wasteful as under-resourcing a critical one.

Insight 2: Contextual Integrity

You cannot cook different types of sacrifices together if doing so "restricts the type of people able to partake of them" Mishneh Torah, Sacrificial Procedure 10:12. Don't mix initiatives with conflicting stakeholder requirements. If a project requires specific governance, don't force it into a "one-size-fits-all" workflow that dilutes its integrity.

Insight 3: The Burden of Professionalism

Priests had to be "fit" to partake—ritual purity was the barrier to entry Mishneh Torah, Sacrificial Procedure 10:7. Your team’s ability to execute a process is tied to their state of mind and preparation. If your "priests" (key leaders) aren't prepared, the output is disqualified.

Policy Move

Implement a "Complexity Check" on all internal SOPs. If a process restricts access or creates bottlenecks that don’t align with the intent of the work (like mixing sacred and ordinary workflows), strip it back. If it’s not "satisfying" for the team—meaning it doesn’t produce quality output—it’s not a process; it’s a roadblock.

Board-Level Question

"Are we forcing disparate initiatives into the same workflow, and if so, how is that ‘mixing’ degrading the specific value each initiative is meant to deliver?"

Takeaway

Don't just do the work. Respect the conditions of the work. If you ignore the context of your processes, you aren't just inefficient—you're disqualified.