Mishnah Kelim 2:3-4

Hook

You think your product is "done" when it launches. You’re wrong. The market defines the utility of your tool, not your PR deck. If your internal definition of "product" doesn't align with the user’s "receptacle," you’re building for a ghost.

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... Any among earthen vessels that has no inner part is not susceptible to impurity on its outer sides." (Mishnah Kelim 2:4)

Analysis

1. Intent vs. Interface

The Mishnah notes that a funnel’s status changes based on its use: simple tool vs. a standard of measurement. In business, a feature’s "impurity"—or its risk profile—is determined by how it’s actually used in the field, not your design spec. If your platform is used for data storage, it’s a vault. If it’s used for distribution, it’s a pipe. You must govern based on actual user behavior.

2. The Power of "Receptacles"

The text distinguishes between items that hold things (susceptible) and items that are merely flat or open (not susceptible). In your stack, what actually contains value for the customer? If you’re building "edges" (flat surfaces) that don't hold value, you’re cluttering your roadmap. Focus on the core "receptacles"—the features that capture and retain user output.

3. Contextual Legitimacy

Rabbi Akiva argues a merchant’s funnel is different because the merchant "puts it on its side to let the buyer smell it." Context dictates classification. Your product’s value proposition is not static; it shifts based on the user's intent. Don’t build monolithic features; build adaptable ones that respect the user’s workflow.

Policy Move

Implement "Feature Utility Mapping": Quarterly, audit your top 5 features. Label each as a "Measure" (infrastructure/standard), a "Receptacle" (value-capture), or a "Flat Surface" (utility/no-hold). Deprioritize any feature that is just a "flat surface" but is being treated by users as a "receptacle" without proper safeguards.

Board-Level Question

"Are we building features based on our original product vision, or are we governing the way our customers have actually repurposed our tools to capture value?"

Takeaway

Your product is not what you designed; it is what the user fills. Stop auditing your intentions and start auditing your user’s reality.

KPI Proxy: Feature-to-Value Ratio (Total User-Stored Data / Total Feature Surface Area).