Mishnah Kelim 13:4-5

Hook

Founders often obsess over the "whole" product—if the UI breaks, the company is dead. But in product-led growth, you’re often shipping modular components. The real dilemma: When does a product cease to be a "solution" and become just a pile of useless parts?

Text Snapshot

"The minimum size for all these instruments: so that they can perform their usual work. [...] A saw whose teeth are missing one in every two is clean. But if a hasit length of consecutive teeth remained it is susceptible to impurity." Mishnah Kelim 13:4

Analysis

The Mishnah treats utility as the threshold for an object’s identity. If it can’t do the job, it’s effectively "dead."

1. Functional Integrity over Cosmetic Completeness

The text argues that an object’s status depends on whether it can still perform its "usual work." In SaaS, you might have a half-broken dashboard, but if the core API call still executes, the product is still "alive." Don't deprecate features based on aesthetics; deprecate based on utility.

2. The Threshold of "Consecutive" Value

For a saw, missing teeth are fine, provided a "hasit length" (a functional segment) remains. This is a lesson in MVP sustainability: you don’t need 100% of the feature set to be functional, but you do need contiguous value. If your features are too fragmented, the user experience is "clean"—in this context, meaning it has lost its capacity to engage.

3. Repurposing as Pivot Strategy

The text notes that a broken tool (like tweezers made from comb teeth) can gain new utility. If a core feature fails, don't just scrap it; ask if that component has a new, secondary utility for a different user segment.

Policy Move

The "Functional Audit": Implement a quarterly review where features are measured not by "do we have this," but by "does it still perform the intended action?" If a component loses its "hasit length" (contiguous functional value), it is either patched or deleted immediately to clear technical debt.

Board-Level Question

"Are we maintaining legacy features because they represent 'the whole product,' or because they are still demonstrably functional for our power users?"

Takeaway

Don't be a perfectionist about the "whole." Be a realist about the function. If it cuts, keep it. If it doesn't, pivot it or kill it.