7 ms·
I think one of the main problems is that a surface-level argument can easily be made that user engagement represents the quality of the user experience (i.e. "u
by nvrspyx 4y ago
I think one of the main problems is that a surface-level argument can easily be made that user engagement represents the quality of the user experience (i.e. "users that spend a lot of time in the app clearly like it"), despite falling apart if you dig deeper than the surface. The allure of short-term profits makes such an argument attractive to upper leadership. It also makes it more difficult for a lower-level employee, like a designer, to convince them against it without direct evidence that optimizing for user productivity is better than optimizing for user engagement.
Combine the ease of making that argument with potential financial incentives to the designers to optimize for that, then you get relatively easy conformity to that goal. I'm sure there's plenty of designers that will happily accept it, so as a company, you can easily replace any designers that push back.
- pdntspa 4y agoI suspect a lot of that is because designers aren't often technology lifers, rather seemingly entering this field smelling profit and riding the wave as it were. I don't know what the solution is here other than firing them all and replacing them with engineers and passionate tech nerds who remember their history. Which won't ever happen, and the situation is hopeless. The world we could have had...
- warning26 4y agoNonsense; plenty of people in UX, myself included, have tech backgrounds. Software engineers aren't immune from the "higher metrics == uSeRs lOvE iT" trap. Consider early Google, when they infamously A/B tested 50 shades of blue for a button. Did that actually improve anything? Of course not.