When to ship it, when to kill it
Read OriginalThe article presents a product development framework for deciding whether to ship or kill a feature. It advocates for testing with alpha/beta users, then removing the feature to gauge genuine user demand. If there's no significant outcry or 'pitchforks' from users after removal, the feature likely isn't valuable enough to ship and should be reworked or killed. It warns against relying solely on usage metrics, which can be misleading.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
Using Browser Apis In React Practical Guide
Jivbcoop
•
2 votes
2
Better react-hook-form Smart Form Components
Maarten Hus
•
2 votes
3
Top picks — 2026 January
Paweł Grzybek
•
1 votes
4
In Praise of –dry-run
Henrik Warne
•
1 votes
5
Deep Learning is Powerful Because It Makes Hard Things Easy - Reflections 10 Years On
Ferenc Huszár
•
1 votes
6
Vibe coding your first iOS app
William Denniss
•
1 votes
7
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook
•
1 votes
8
Quoting Thariq Shihipar
Simon Willison
•
1 votes
9
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft
•
1 votes