Mishnah Kelim 15:2-3

Hook

You’re building a product, but are you building a tool or just clutter? Founders often conflate "features" with "value." In Mishnah Kelim 15:2, the Sages distinguish between objects based on their specific utility and intent. If you can’t define exactly how your feature serves the user’s core workflow, it’s not an asset—it’s just noise that adds technical debt.

Text Snapshot

"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." Mishnah Kelim 15:2

Analysis

1. Intent Defines Impact

The Mishnah teaches that an object's status (its "susceptibility") depends on its function. If a device is auxiliary—just a "hanger"—it lacks the functional weight of a primary tool. In business, if a feature doesn't directly solve the core user problem, it is "clean" (non-essential). Don't build for the sake of checking boxes.

2. Market Context Matters

The text differentiates between a "baker’s" tool and a "householder’s" tool. A professional baker’s shelf is critical; a casual user’s is not. You must segment your features by user persona. A "pro" feature is a liability (or necessity) that a "lite" user doesn't need.

3. The "Decoration" Trap

The text notes that even a basic board becomes "susceptible" if "he dyed them red or saffron." When you over-engineer or "pretty up" a useless feature, you trick yourself into thinking it has utility. Don't mistake design polish for product-market fit.

Policy Move

The "Utility Audit": Every quarter, review your product roadmap. Any feature that doesn't track to a core user outcome—or is merely "decorating" an existing process—is moved to the "Deprecation Queue." If it doesn't hold value (the "receptacle" principle), it gets cut.

Board-Level Question

"Which 20% of our current feature set would remain if we had to cut our infrastructure costs by half, and why are we keeping the other 80%?"

Takeaway

On this day of Tzom Tammuz, we reflect on the breaking of the tablets and the loss of focus. Don’t build "flat boards" and call them tools. If a feature isn't serving a specific, active purpose in the user's workflow, delete it. Lean is holy.