Mishnah Kelim 15:4-5

Hook

Founders often obsess over "scale" at the expense of "utility." You build feature bloat, hoping it makes you indispensable, but you end up creating a "vessel" that’s harder to maintain and prone to "impurity"—a messy, high-friction product.

Text Snapshot

Mishnah Kelim 15:4-5 defines which tools are susceptible to impurity based on their function: "This is the general rule: [a hanger] that is intended to aid when the instrument is in use is susceptible to impurity and one intended to serve only as a hanger is clean... This is the general rule: [a shovel] that is intended to hold anything is susceptible to impurity but one intended only to heap stuff together is clean."

Analysis

Insight 1: Function Defines Identity

The Mishnah teaches that an object's status isn't about what it is made of, but how it is intended to be used. If your tool is "intended to hold," it carries the burden of use. If it’s just for "heaping," it’s clean.

Insight 2: Accessory Friction

Tools that "aid when the instrument is in use" are high-touch. If your feature is a "hanger"—a dependency that integrates directly into the workflow—it becomes part of the "impurity" of the system.

Insight 3: The Professional Standard

The text distinguishes between professional (baker) and household tools. Professional tools are held to higher standards of "impurity" because they are actively engaged in the work. Don't mistake "convenience" for "utility."

Policy Move

Implement a "Feature Purity Audit." Any tool or feature that serves only as a "hanger" (administrative overhead) rather than active utility should be pruned. If it doesn’t directly contribute to the core output, it is likely just adding technical debt.

Board-Level Question

"Are we building features that make the product 'heavier' and more prone to maintenance failure, or are we building tools that simplify the core user flow?"

Takeaway

Stop building "containers" that require constant maintenance. Build tools that perform a singular, clean function. If the user doesn't need it to hold the value, cut it.

KPI Proxy: Feature Usage Density (Total active users using a specific feature divided by total features available). Low density = high "impurity."