Menachot 52

Hook

You've just implemented a new company policy, convinced it'll solve a problem. But what if it creates a bigger one? Founders aren't just rule-makers; we're ruthless rule-auditors.

Text Snapshot

The Sages initially held that one is "not liable for misusing consecrated property" if benefiting "from its ashes." But observing "people were treating [them] disrespectfully," they "decreed that it is subject to the halakhot of misuse." Yet, when this led to people "refraining from sprinkling it in cases where there was uncertainty," they "revoked the decree and established it in accordance with the halakha as it is by Torah law."

Analysis

Insight 1: Policies Must Adapt to Behavior

Your rules aren't set in stone. The Sages changed the law because "people were treating [the ashes] disrespectfully." You need to be just as agile. If a policy isn't achieving its intended behavioral outcome or is being gamed, it’s broken. Don't confuse intent with impact.

Insight 2: Beware the Unintended Consequences Loop

Every policy has second-order effects. The decree, meant to instill reverence, resulted in "people... refraining from sprinkling it." This created a larger problem – preventing purification. Track the actual impact, not just the desired one, with brutal honesty.

Insight 3: Prioritize Core Utility

The ultimate purpose of the ashes was purification. When the decree hindered that, it was "revoked." Your core mission and product utility always trump internal process sanctity. Don't let a well-intentioned internal rule kill your external value proposition.

Policy Move

Establish a "Policy ROI Review" process. For any significant new policy, mandate a 90-day review cycle. This review must include a "consequence analysis" that quantifies both intended and unintended behavioral shifts. KPI Proxy: Policy-Related Friction Score (e.g., internal survey score on policy ease-of-use or support ticket volume related to policy confusion).

Board-Level Question

How do we consistently measure and iterate on our internal policies to ensure they're accelerating our mission, not inadvertently creating new bottlenecks or discouraging critical behavior?

Takeaway

Your policies are hypotheses, not commandments. Measure their real-world impact relentlessly, and don't be afraid to revoke or revise if they hinder, rather than help, your core mission.