4 ms·
This is usually it! As developers, we have all worked on features where it was obvious that users wouldn’t want it, but the feature would juice some metric so i
by ryandrake 6y ago
This is usually it! As developers, we have all worked on features where it was obvious that users wouldn’t want it, but the feature would juice some metric so it was prioritized. Some time between that initial meeting about how this will juice the metric and launch, Product convinced themselves that users would actually want it and are not prepared to accept the feature’s failure. Finally, when indeed users don’t want to use it, it would get pushed at them repeatedly, through sales and through dark UI patterns. Tale as old as time...
This is what happens when you plan your product not from user need but from company need.