4 ms·
If you are in product development, the lesson is that any change has a cost and impact to your users, so you need to make sure that the benefits outweigh the co
by cornholio 9y ago
If you are in product development, the lesson is that any change has a cost and impact to your users, so you need to make sure that the benefits outweigh the cost and plan for resistance.
That's entirely different from "they will complain no mater what you do so you should ignore them".
- AJRF 9y agoSo much this. I don't think you should be given free reign to just accept outrage because that's the way you think things need to be. You ultimately need to continually make improvements, not change for change sake.
- nerfhammer 9y agoIs there any indication that hadn't happened here? Is Snap really that stupid? Did they not test this at all? If so, that's the big story. Unspecified numbers of users complaining isn't a terribly sufficient story. I recall lots of facebook "boycotts" over the years ago over various UI changes, totally forgotten after a day or two. I suspect they actually a/b tested each change in small markets or test audiences and found usage increased after people got used to it. If Snap isn't doing that then that should be big news.
- daxorid 9y agoAnother option that product development ought to consider is choice. Determine the ongoing cost of maintaining two different user interfaces versus the benefit of permitting users to choose their preferred interface. If properly engineered, with low impedance mismatch between API and UI, the cost could be kept reasonably low for most applications.