6 ms·
I hope there's some UI/UX designers that can explain this to me. It often appears that design changes are changed just to change. Doing things like changing the
by godelski 5y ago
I hope there's some UI/UX designers that can explain this to me. It often appears that design changes are changed just to change. Doing things like changing the clock from right to left (Android). Moving a bar that's existed to another location (Spotify). Removing color hints (Signal). And so many other things. Things that basically your users have been trained to look at and then need to be retrained. Removing hintings that people have been relied on.
So, the big question is: why? Good design is hard and often underappreciated. I don't want to convey that idea. But why do things like this happen so often? Changes that don't actually provide any more utility. Changes that remove utility. It is just so common that there has to be some reason for it. Often backend people say that it is just done to justify their existence but I don't buy this because there are plenty of good design features that can be constantly worked on and improved. Is there some psychological effect this has on users because it is once again novel? So often we don't see good design improvements but things that just come off as "change because change." Why? Help me understand.
- mikelward 5y agoI think the clock moved to balance out icons on either side of the big center notch. Then next year they moved to a left-side holepunch notch, but didn't move it back. Or even offer the option. :(
- deleted 5y ago[deleted]
- jay_kyburz 5y agoFashion. Also, in my industry, if you're software is not visibly changing, people assume its dead and no longer supported, not going anywhere. People want to feel like they are part of something that is going somewhere. Software is not a tool, its a journey into the future!
- deleted 5y ago[deleted]
- siproprio 5y agoWhat's your industry?
- jay_kyburz 5y agoI'm in Games.
- eloisant 5y agoWell software in your industry is definitely not a tool...
- fendy3002 5y agoMost of the time it's for inner achievements for the product manager or designers part. Another is they just changing their ui/ux lead and they have different views. It can also redesigned to match style updates, useful for fashion, travel or wedding sites. Sometimes the menu increases that a list of buttons can't accommodate anymore so it's changed to it's own page or drop-down. Sometimes they want people to be confused and ask the changes in more general forums, generating free publications.
- godelski 5y agoMost of these sound pretty insane tbh (though some completely sane). > Another is they just changing their ui/ux lead and they have different views. This one specifically irritates me. Even under the assumption that that new lead is correct and the new interface is cleaner and more usable, it still needs to be weighed against the time it takes to retrain users to the new format. You have to deal with what you were given. You can't just burn Rome to the ground, rebuild it in a day, and expect everything to be fine. For the love of god, at least do testing to show that this the cost doesn't outweigh the benefits.
- danjac 5y agoIt's not something that's confined to design/UX though. Bring in a new CTO/tech lead and they'll tell you the current architecture is outdated or the code is spaghetti and needs a rewrite in [insert architecture/language doing the rounds on HN]. Bring in a new project manager and they'll want to introduce [insert Agile framework du jour]. Someone has been hired for presumably a lot of money, and if they just go "meh, it's fine, we just need to tidy things up a bit here and there" people might question why they were hired for a lot of money.
- stingraycharles 5y agoOf course, but the difference is that there’s a much higher impact for the users if the design keeps changing. Technical infrastructure is pretty much entirely hidden from the users.
- g_p 5y agoI do wonder if to some extent the inherently subjective nature of UX/UI design is what keeps it forever going? Designers want to stay employed and not just become a "bring in one-time at the start" contractor, so they justify changes through continual enhancement or similar, assuming the current solution may be one of a few local optima rather than the global optimum. Lacking objective numerical comparison, perhaps designers and product teams attempt to do metrics-based comparison from telemetry (we raised metric X by changing the design). That leads to an ever changing design that tries to optimise for business objectives, rather than what the user wants. Backend code can be optimised and honed and improved with objective measurements (CPU cycles used, latency, perceived performance, download time for user), but design doesn't give these. In saying that though, rewrites in new languages and frameworks do seem to be becoming the problem for backend - optimisation isn't seem as exciting or career advancing, I guess... Few are optimising code for performance these days though, I'd wager - everyone just assumes your user won't mind your software using 15% of their CPU when sitting idle. Maybe it is just as simple as that metrics individuals are measured on for job performance?
- willhinsa 5y agoThere are objective measurements that can be done, but they’re difficult/expensive to do effectively. Like, “How many interactions/seconds does it take our users to find X?” It’s difficult because you have to know what “X” a user was looking for, which requires some varying degree of asking lots of users and reading those responses to be accurate. Measuring “engagement” is far easier to orchestrate practically and organizationally, even though it produces awful software.
- godelski 5y ago> Measuring “engagement” is far easier to orchestrate practically and organizationally, even though it produces awful software. Engagement is such a terrible metric. I'm not saying it should be thrown out, but it is classic example of Goodhart's Law[0]. Rage is engagement. Too much reliance on engagement is what got social media into a race to the bottom. That's not the mark of a quality product. Measuring is hard, you're right. But if you're going to use bad measurements (which often is our only choice) they shouldn't be targets. We should understand where they fail and use the information accounting for that, not ignoring it. [0] https://en.wikipedia.org/wiki/Goodhart%27s_law https://en.wikipedia.org/wiki/Goodhart%27s_law
- smichel17 5y agoHere's a short case study. I am the maintainer of Red Moon, a FLOSS screen filter app for Android. Over a period of several years, the location of the toggle has moved from a switch at the top, to a switch and a floating action button (FAB), back to just a switch, and will soon move to just a FAB. I can provide more detail later if someone would like, but the short of it is: 1) As other features changed (permission prompts and moving the growing number of settings to their own screen), one location or the other made more sense. 2) I thought I would like the single top switch better than a single FAB, but after using it for a while, I think the switch feels more confusing than fresh (the action bar is a nonstandard location for a switch). Overall, I would say it's because design is really hard. But not like that! It's hard because when you spend so much time close to a system, you start to overthink things, and then second-guess yourself. So you can't trust your intuition, you need to listen to users with fresh eyes. But they're also telling you 5 different, conflicting things, and if you listen to everyone you'll have a settings section 9 miles long. You can try to rely on data, but that's mostly good for reaching a local maximum, not staying cohesive. The best designers are able to keep their "fresh eyes" even after working with the system for a long time.
- godelski 5y ago> I thought I would like the single top switch better than a single FAB, but after using it for a while, I think the switch feels more confusing than fresh (the action bar is a nonstandard location for a switch). This seems to be addressed by one of my complaints. Was this feature not tested before pushed out to users? I get that design is difficult. Anyone saying otherwise is biased. But it seems like a big problem is just trying something out first. Design can take months of use to realize something is bad. It seems like what should be done is: create new UI; use internally and push to everyone's version, use for a few weeks to a month; push to beta and get user feedback and pay attention to web traffic like HN and Reddit complaints about the new design; then decide if it should be pushed or not. I've seen apps that seem to follow this but just push despite bad user feedback and bad internal feedback. Going through the motions isn't enough, it has to be used as iterations. > So you can't trust your intuition, you need to listen to users with fresh eyes. But they're also telling you 5 different, conflicting things, and if you listen to everyone you'll have a settings section 9 miles long. A good piece of advice I heard was "listen to users for problems. Don't listen to users for solutions." Because people are actually really good at identifying problems. But most people are really terrible at solving problems (I mean if they were good at it we wouldn't have 90% of the problems we do). The addendum is to only take solution advice from experts that understand more of the nuance of what you're doing, but then to still be careful.
- mch82 5y agoProduct Management and/or Sales & Marketing are likely to own the decision.
- Casperin 5y agoIn every company I have worked in on the frontend, this is the answer. "We need to increase x" comes down from somewhere, and then everyone attempts to find a good way to measure increase/decrease of x and then come up with a design that increases x. I have never been in a company where a UX or UI designer had leverage to redesign anything just for the hell of it.
- jjav 5y ago> It is just so common that there has to be some reason for it. One reason is that UI is a fashion-driven space so as the fashion changes there is increasing pressure to rewrite everything to look like all recent apps look, even if it breaks functionality. Another reason is that if an application has a well-polished UI that all users love.. what's the UI team going to do? How does that newly hired UI PM get to make a big impact so they get a promotion? So there's also a lot of resume-driven UI change for the sake of change. For the second problem, a partial solution is to have shared UI teams so they can keep busy improving the products which need the most improvement and leave alone the ones that are already good. Of course, hard to do in a smaller company that might only have one product. For the fashion problem, no good solution. Ignoring fashion entirely works for software that targets technical people but for mass-market applications, no good solution.
- Griffinsauce 5y agoThere is one simple reason that enables all the shit mentioned in other replies: as much as we like to pretend, the impact of design is very hard to measure. A product experience is nuanced, part of a journey, with learning curves, preferences and problems. Much of this is completely ignored in the measurement of the success of design changes. There are lots of reasons people tend to screw with things that are fine, but the root cause is that they get away with it. Hell, they even get rewarded for it.
- franga2000 5y agoThis seems like a solved problem as well. Don't people use focus groups anymore? Or have an open feedback forum where people can submit feedback and use user ratings to see which issues are the most important to the most users. Many companies already do have forums like this and they're filled with UI complaints having sometimes thousands of upvotes, but it's all for nothing because almost none of them actually use that feedback. My bet is still on "UI design isn't a full-time job, it's project work, so UI designers have to keep moving things around to stay relevant in one company". As much as I don't like outsourcing, having a bunch of designers on your payroll with nothing to do most days but still needing to pass all the employee rating crap is bound to result in an unstable and never good enough UI.
- watwut 5y ago> This seems like a solved problem as well. Don't people use focus groups anymore? No they generally dont. And generally, they never used focus groups, unless we are talking about something super big.
- Griffinsauce 5y agoFocus groups tell you about the effectiveness of design changes, not the impact on business metrics.
- MrDresden 5y agoHaving worked in the mobile space for the last decade, it is my experience that these UI/X changes usually are a side effect of new management (after a purge) or from way on high (the c-suite). Neither one of these groups know much about UI/X but hold strong personal opinions which they automatically believe must hold true for all users. I am currently in a tug of war over such UI/X change for a feature in a banking application, making the case that we have plenty of older users who will have massive issues with the current redesign. My suggestions on performing user testing on the new design to validate them has not received much support over the last weeks. And so, I have started looking around for other opportunities on the market (this is also why places with bad UI/X continue doing so, they select for the people who are ok with making it).
- krono 5y agoMy pet theory is that Spotify doesn't want you to choose your own music but steer you towards specific songs instead. Either to increase your level or length of engagement with the service, or because some songs earn them more cash than others.
- benrbray 5y agoHey me too. I'm pretty sure when you shuffle, it's not actually random, but weighted by some combination of licensing fees / paid promotion.
- MrDresden 5y agoI am 100% certain that they employ plenty of dark patterns in hopes of steering customer behaviour for Spotify's maximum financial benefit.
- Sander_Marechal 5y agoAh, the Netflix model
- megablast 5y agoI mean, they are employees. If they aren’t working, they will get fired. There work is measured in updates to the apps. They have to keep changing.
- lupire 5y agoThis is quite obviously the answer, and UI design isn't a skill like software where your boss can say "If you've finish your work, start a new project." We don't need more UI designs like we need more useful/efficient software. Imagine If software engineers could get paid to constantly refactor the code and change APIs -- oh, wait, API devs do, for the same reason.
- gampleman 5y agoI think this goes to the fact that the people designing, implementing and signing off on development are looking at the UIs constantly - close to 8 hours a day, every day. This is usually (at least) an order of magnitude more than your users (well unless you're Facebook I guess). I think many people just get bored looking at the same old screen all the time; and so when a designer inevitably proposes something different everyone on the team thinks it looks great and so much better than the old design. It's hard for them to realise that it's not better, but merely alleviates the boredom they feel.
- HeavyStorm 5y agoThat's actually a good explanation.
- thevagrant 5y agoThat or some designers are opinionated and more interested in making their mark on a design, compared with understanding and advocating for their userbase. Honestly I've heard this line more from designers than any other field: "We can't add that feature/button because it's too confusing" Usually the above statement is conflicting with reality and the request to add the feature/button is to give the UI clarity (or worse, provide the feature the customer asked for!)
- deleted 5y ago[deleted]
- Causality1 5y agoPurely the justification of their own job. Open up any settings window in Windows 10. The title bar and the window contents are the exact same color, making it impossible to tell where exactly you need to click to drag the window. In a sane world the programmer responsible for that would be out on their ass.
- ProZsolt 5y ago> Doing things like changing the clock from right to left (Android). I'm not a designer, but I know this. They needed less stuff on the right, so the can have a notch in the center. This made the UI worse for everybody else.
- Sophistifunk 5y agoIt's to steer you to cheaper (for them) content, I imagine, with enough randomness to make it sticky and obscure the real goal.