Mishnah Kelim 2:5-6

Hook

In startups, we obsess over "Product-Market Fit." But we often fail to define the actual utility of our features. We build "vessels"—features, modules, or services—and assume they are valuable just because they exist. The Mishnah reminds us: A tool is defined by its capacity to contain, not its material. If it doesn't hold anything, it’s just debris.

Text Snapshot

"A funnel for home use is not susceptible to impurity, but that of merchants is susceptible because it also serves as a measure... The following is a general rule: any among earthen vessels that has no inner part is not susceptible to impurity on its outer sides." (Mishnah Kelim 2:5-6)

Analysis

1. Intent Defines Reality

The Mishnah distinguishes between a home funnel (utility) and a merchant’s funnel (measurement). A tool’s status changes based on its function in the ecosystem. If you build a feature that serves as a measurement or a standard, it carries higher responsibility (and "impurity" risk) than a tool built for private utility. Decision Rule: Don't confuse "utility" with "metric." If your feature is being used as a benchmark for customers, it is no longer a peripheral tool; it is core infrastructure.

2. The "Inner Part" Test

The text notes that vessels without an "inner part" (a receptacle) are effectively invisible to the laws of impurity. In product terms, if a feature has no "internal storage" or "holding capacity"—if it doesn't solve a state-retention problem for the user—it’s a flat surface. Decision Rule: If a feature doesn't hold or change user state, kill it. Flat, non-receptacle features are just noise.

3. Purpose-Built vs. Repurposed

The text discusses pot covers that become functional tools (like a drainer). When a secondary component starts doing the job of a primary tool, it becomes "susceptible." Decision Rule: Beware of "feature creep" where a support module starts acting like a primary engine. Once a sub-feature becomes a primary workflow, you must treat it with the rigor of a core product.

Policy Move

The "Receptacle Audit": Review your product roadmap. For every feature, ask: "Does this hold user data, or is it just a cover?" Any feature that doesn't hold state or provide a measurable transformation of value should be deprecated or moved to a "utility" status to reduce technical debt.

Board-Level Question

"Are we building tools that solve a core problem (the vessel), or are we just decorating the outside of our existing product (the exterior)?"

Takeaway

Stop building "covers." Build "vessels." If it doesn't have an inner capacity to solve a user’s specific state-change problem, it’s not a feature—it’s just clutter.