Daily Mishnah · Startup Mensch · Bite-Sized
Mishnah Kelim 13:2-3
Hook
You’re burning cash on a feature set that no longer performs. Do you kill the whole product, or pivot the remaining "teeth" to keep the engine running?
Full Experience in the App
Listen. Chat. Go deeper.
Audio playback, interactive chevruta, Hebrew tools, and every daily learning track — only in Derekh Learning.
Text Snapshot
Mishnah Kelim 13:2-3: "A stylus whose writing point is missing is still susceptible to impurity on account of its eraser... A hatchet whose cutting edge is lost remains susceptible to impurity on account of its splitting edge... The minimum size for all these instruments: so that they can perform their usual work."
Analysis
The Sages define "utility" not by the original intent of the tool, but by its remaining functional capacity.
Insight 1: Functional Redundancy
A multi-tool remains a tool as long as one of its core functions survives. If your product loses its "writing point" (primary feature), it’s not dead if the "eraser" (secondary utility) still solves a user problem. Don’t trash the code base until all functional edges are dull.
Insight 2: The "Minimum Viable" Threshold
The text dictates that susceptibility to impurity—the definition of a functional object—depends on whether the item can "perform its usual work." If your MVP is stripped down, it must still perform at a baseline that justifies its existence. If it can’t, it’s just scrap metal.
Insight 3: Contextual Value
The Mishnah notes that if a component is broken in a way that renders it unusable (e.g., a handle too short to hold), it loses its status. Innovation is useless if the UX makes the tool impossible to wield.
Policy Move
Implement a "Feature Sunset Audit": Quarterly, rank all sub-features by "Utility Persistence." If a feature loses its primary edge, map its secondary utility. If it has neither, kill it immediately to reduce technical debt.
Board-Level Question
"Which part of our current product stack is only 'susceptible' (alive) because of a secondary utility, and how do we lean into that secondary value to drive the next growth phase?"
Takeaway
Stop mourning the features you lost. Audit what remains. If it can still perform its "usual work," it’s not a broken product—it’s a pivot waiting to happen.
derekhlearning.com