| ▲ | anonymars 3 hours ago | |||||||||||||||||||||||||||||||||||||||||||
Simple example: feature X is rarely used (thus we should get rid of it) Hold on, why is it rarely used? Is it hard to use? Is it hard to find? Was it poorly named? Does it work right? Does it get me 80% of the way there? Does it get me 20% of the way there? Do I rarely need it but when I do need it it's a huge time saver? Am I hesitant to depend on it because I fear it will be taken away in a future update? | ||||||||||||||||||||||||||||||||||||||||||||
| ▲ | mjr00 3 hours ago | parent | next [-] | |||||||||||||||||||||||||||||||||||||||||||
> Simple example: feature X is rarely used (thus we should get rid of it) Oh man, I remember a very specific example of this: many years ago now, Google Chrome pushed an update that got rid of the option on the menu bar for "Close Tabs to the Right". I remember looking into the Google issue tracker where people were complaining, and some PM provided a "data-driven" justification: when people opened the context menu, they only clicked on the "Close Tabs to the Right" option 1-2% of the time. It's a great example of why data without context can give you the wrong answer. Of course the option is used relatively very rarely; you only need to clear out your tabs every once in a while, compared to creating new ones or managing tab groups! But it's still an essential task. It's like saying filing your taxes isn't important because you only need to do it 0.2% days of the year. | ||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||
| ▲ | Terr_ 2 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||
Conversely: Feature X is often used... Because to drive adoption someone made it mandatory for a certain workflow and it nags everyone else so they "engage" with it just enough to make it go away. (Looking at you, "AI" buttons...) | ||||||||||||||||||||||||||||||||||||||||||||
| ▲ | cosmic_cheese 3 hours ago | parent | prev [-] | |||||||||||||||||||||||||||||||||||||||||||
And following this, I'm sure we've all seen the pattern of manufacturing the data required to justify the removal of features. Bury feature → usage numbers tank → oh hey look nobody uses this any more, guess we can safely cut it! | ||||||||||||||||||||||||||||||||||||||||||||