CntrldChaos

CntrldChaos t1_jbxgslr wrote

>If a company ever has to "bring back" a feature that customers wanted and used, it screwed up. Period. Looking at you, Apple.

He said in no questionable terms that a company screwed up if they don’t release a feature that existed in a previous version of a product, and bring it back. I’m saying this happens for very good reasons. The team knows some users use it but they don’t feel it’s necessary for launch because the product they rebuilt is better than it was and is worth a “beta” launch as is. They throw the feature on the backlog and prioritize it accordingly. This happens on any project where you are rebuilding from the ground up.

Users of products don’t always equate to dollars. For that software to exist they need customers who spend money and will focus on features for those customers first. They will then launch when the features that will keep the customers who matter happy are done. Most people think of software as free overall and think of what they will do to said company, but in reality software from companies is built to make someone money in some manner. A user who pays nothing is entitled to nothing. Many companies bend over backwards for free loaders. That can work out but it can also drive your product down a road that prevents it from surviving as long as it should.

No one person can definitively say what is right or wrong for a team and what they are building. Even the people who ultimately make the calls are guessing a bit which path to take. I am pointing out very specifically that in some paths a team can build an existing feature later and it’s not a screw up of any kind. It was a well thought out choice of value to their overarching users and not the people who use the feature in a silo.

1

CntrldChaos t1_jbuuwq6 wrote

This entire chain of messages stemmed from a dude saying all software added later to a product was a failure. His assessment is that it’s never ok to release a product missing a feature and add it back in a later release. It’s flat out wrong. Companies have limited cycles to do work and they release it when it makes sense. Sometimes features that exist shouldn’t exist right away because it’s limited benefit. I’m literally saying it’s not one size fits all. Downvotes are people feeling like big company bad and I know what’s best.

−3

CntrldChaos t1_jbusl8z wrote

A product owner and company does. As a developer or any of those roles you will understand what it means to hit MVP where you then build out what your users want. Building out all features to 100% is actually the exact model that failed day in and day out before the MVP and priority based model. You’d know that if you delivered software for a living

−2

CntrldChaos t1_jbus7nm wrote

Understanding why a company does not have a feature at release is completely understandable if you work in the industry. If you are doing it day in and day out you will see what it takes and where you have to make sacrifices. While one feature is super important to you, it may be one of the least requested features by the majority of your users. Being a developer you absolutely 100% know the sacrifice you will make to get software out. Some software works well and is beneficial to many people without features and you then build out what the majority want.

0

CntrldChaos t1_jbtmwkt wrote

I’d bet every product you have purchased has followed this flow and likely has some feature someone wanted they didn’t have right away. Most software is free and many people upgraded windows for free or with their new computer. Microsoft prioritizes the most important feature for a release then enhances it constantly. They even have a forum where the more noise you make the higher up the priority list it can go.

−33

CntrldChaos t1_jbtm6rd wrote

You know, rather than assume you could just ask how it’s possible.

There are times you rebuild something from scratch and old versions of code in that case don’t make sense. In some cases you can copy it over but in many cases it just wouldn’t make sense with the new structure of the project. You basically are rebuilding your product from scratch and prioritizing the most important features to recreate first. You then have to make it worth it for the customer so you build new features too. On the backlog you keep a list of things you likely want to bring back but are less pressing.

1