What if you didn't ship any new features for a year?

#2・
35

subscribers

11

issues

What if you didn't ship any new features for a year?
By Duncan Mackenzie • Issue #2 • View online
Features, as in new functionality. What if all you did was continue to refine and improve on your core functionality? As a user of a system, like Spotify or Netflix, what if they didn’t add any features, just focused on improving the speed and reliability of the existing functionality? There is an unhealthy obsession with shipping new features, instead of focusing on what is already in use and represents the core of your platform. In this issue, I’ll link to a few discussions related to this problem, but hopefully (if you work on, own, or even use a software product) you can also reflect on what your team focuses on, what they celebrate, and what is considered less important. Send some of these links or this whole newsletter around to provoke some discussion.

The inevitable result of focusing only on shipping features
12 Signs You’re Working in a Feature Factory
Adam Kinney
This and the following comments. Stop starting new things, start finishing works in progress. https://t.co/yTpOeSyYjK
Adam, a member of the Microsoft Docs team, posting about one impact of being focused on new work over shipping what we have already started, or enhancing what is already in production.
One-shot Project
Build Less (from Getting Real)
Confetti Moments from ZenHub
Did you enjoy this issue?
Duncan Mackenzie

In each newsletter, I'll share a set of links related to web development and software engineering. As the editor, my opinions are going to influence the topics and tone of this material, so expect to see lots of information on web performance and general topics around working in a software engineering team! Check it out and let me know what you think at https://twitter.com/duncanma

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue