If you're spurning customers away, very few will come back and tell you they are leaving. This is often the reason why developers seldom get it and embrace tha

If you're spurning customers away, very few will come back and tell you they are leaving. This is often the reason why developers seldom get it and embrace that signal. More features do not necessarily translate to better outcomes. Features will often be measured at a point in time. It has to be good enough for people to use a product and not inconvenient enough for people to run away. More development does not mean more usage. Imagine someone in utilities connected your home to a power supply and then decided to periodically change it just because they need to show that they work - and not to be useful to you. Would you like that? That sort of active development thing is found seldom outside the subscription based SaaS business. Case in point: AWS, you have dozens of services launched every quarter and maybe its developers there get bored and launch new services, yet most people use those few key services a lot and are happy to stick around as long as things don't break terribly. The issue is that we've come to liken features and bloat with usage. Then we assume our customers want that bloat and can afford to do so. Mostly at that point, companies are optimizing for their own development over customers needs. Over a period of time we get disillusioned that our bloated software is often what our customers need. Then when that doesn't work well, try explosive methods such as platform obsolescence. Thus leading to loss of sustainability.