Journal · 09 Jan 2026
When to retire a feature that never crossed the adoption floor
Set the floor before you look. Miss it once, and you may have a confounder: a store outage, a holiday, a bad translation. Miss it twice, with confounders named in advance, and you usually have a surface that should not keep consuming design time.
Devtracebase does not teach you to enjoy retirement. We teach you to make it discussable. The Stewardship one-pager has a line for salvage cost because measurement alone will not win against a founder who “likes the animation.”
Exceptions we accept in class
Regulatory features can miss a consumer-style habit floor and still be mandatory. So can features that exist only to satisfy a partner contract. In those cases, change the metric: completeness, error rate, time-to-complete — not uptake. Pretending they are adoption problems wastes the floor’s reputation.
Exceptions we do not accept
“The influencer campaign has not started” is not a reason to delay the second window if exposure already reached the planned eligible base. “We need more events” is not a reason if the three core events are already trustworthy. “Sales promised it on a slide” is politics; write it down as politics, not as a measurement gap.
When the Bangkok social app in our reviews page retired Moments, the useful artefact was not the 2.8% number. It was the pre-agreed 6% floor sitting on the same page. Without that, the meeting would have become a taste discussion. With it, retirement was a scheduled decision.
If your company cannot pre-agree a floor, you are not ready to measure adoption. You are ready to argue. Come back when someone with budget will sign the floor in week zero.