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
The Beautiful Web
Jens Oliver Meiert
•
2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane
•
1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg
•
1 votes
4
Wagon’s algorithm in Python
John D. Cook
•
1 votes
5
An example conversation with Claude Code
Dumm Zeuch
•
1 votes