Mishnah Kelim 5:5-6

Hook

Founders often obsess over "feature creep"—adding layers to a product to make it more versatile. But is your "value-add" actually a liability? In the Mishnah, we learn that the "crown" or extension of an oven is only treated as part of the core vessel if it’s functional. If it’s just ornamental or unused, it’s legally irrelevant.

Text Snapshot

"The additional piece of a householder's oven is clean, but that of bakers is unclean because he rests the roasting spit on it. Rabbi Yohanan Hasandlar said: because one bakes on it when pressed [for space]." (Mishnah Kelim 5:5)

Analysis: 3 Decision Rules

1. Utility Defines Entity: If a feature isn't being used for the core mission (baking), it isn't part of the "vessel." In business, if a feature is rarely used, it’s not a product feature; it’s technical debt.
2. The "Baker's" Standard: The Mishnah distinguishes between a "householder" (casual user) and a "baker" (pro). If your power users are relying on a hack to solve a problem (like resting a spit on an oven rim), that hack is now a core part of your infrastructure. Own it or fix it.
3. Intent vs. Reality: An oven is "unclean" (susceptible to impurity) only when it’s fully operational. If you’ve built a feature that doesn't actually help the user achieve their goal, you’ve built a vanity project.

Policy Move: The "Feature Sunset" Audit

Implement a quarterly "Usage-to-Utility" Audit. If a feature is used by less than 5% of your active users, it is officially "clean" (non-essential/discardable). Sunset it. If it’s used by 20%+ of power users, document it as a core requirement and bring it into the standard codebase.

Board-Level Question

"Which of our current 'value-add' features are actually just 'roasting spits'—hacks we’re forced to support because our core product wasn’t designed to handle our users' actual workflow?"

Takeaway

Stop inflating your product with features that don't earn their keep. If it isn't essential to the "baking," it's just extra surface area for bugs. Complexity is a tax; only pay it for features that scale.

KPI Proxy: Feature-to-User Ratio (Active users per developed feature).