Menachot 32

Hook

Founders, ever felt like you're stuck doing something "because that's how we've always done it," even when logic suggests otherwise? Or conversely, tried to innovate only to hit a wall of ingrained habit? This Gemara cuts through that tension.

Text Snapshot

The Gemara discusses the proper way to write a mezuza. Initially, a scribe makes them "open" because "the passages are not adjacent to one another in the Torah." However, the text later states, "Rav is of the opinion that an established custom must be observed, and nowadays the general custom is to write the passages of the mezuza in the closed manner." The most striking line: "If Elijah comes and says that one may not perform ḥalitza with a sandal, they do not listen to him, as the people are already accustomed to performing ḥalitza with a sandal."

Analysis

Insight 1: Custom Trumps Logic (Sometimes)

"If Elijah comes... they do not listen to him, as the people are already accustomed." Established custom creates its own reality. In business, "how our customers expect it" or "how our market operates" can be more powerful than a theoretically "better" approach. Don't fight deeply ingrained user behavior or industry norms without a massive value proposition.

Insight 2: Principle Informs Practice

Initially, the "open" style was based on "the passages are not adjacent." Even when custom dictates "closed," the original rationale reveals a logical underpinning. Understand the "why" behind your processes. Knowing the principle helps you adapt intelligently when custom isn't the driving force.

Insight 3: Optimal vs. Permissible

"It is a mitzva ab initio to prepare... in the closed manner, but if one prepared them in the open manner, it is permitted to use the mezuza." There's a "best practice" and a "good enough to ship." Don't let perfect be the enemy of good, especially when market custom allows variation. Prioritize fit-for-purpose over ideal.

Policy Move

Formalize "Custom Audits": For any process or product feature, identify if it's based on an explicit "best practice" (mitzva ab initio) or an "established custom." Document the rationale behind each. KPI Proxy: Track user adoption rates of features where custom was intentionally integrated vs. ignored.

Board-Level Question

How do we balance internal "best practice" initiatives with market or customer "customs" to maximize adoption and minimize friction?

Takeaway

Custom isn't just inertia; it's a powerful force that shapes user behavior and market expectations. Respect it, understand its roots, and know when to innovate within its bounds versus when to disrupt entirely. Your ROI depends on it.