Citation absolutely needed. In my experience people are frequently idiots, and work gets done for no reason after someone with authority is convinced that it's a good idea by someone aching to do that sort of work.
If it happens in so many other cases, it does happen in UI/UX as well.
It's really hard to get people together to make good software. I think that's something everyone can agree on.
Sometimes that is a business need, but the rest of the business doesn't recognize it (or won't until it's too late). Yes, having your website running on coldfusion 5 isn't actually a problem - data comes in, data goes out, orders are filled (ecommerce, for example). If the actual business needs didn't change ever... there would not be a need to ever refactor/rebuild.
And yes, I've seen "needless" refactoring, without regard for business needs. But there are folks who do understand some of the needs of the business before the other business units may realize it themselves.
This. I work for a big payment system company. They had to buy another Exadata, reaching the maximum plan offered by Oracle. The refactor was delayed so much that now we have little more than one year to rewrite everything. If we don't make it in due time no more transactions will be processed. Some devs who pointed the need for a refactor left the company in the last two years and said it feels like a time bomb ticking with every git commit.
Meanwhile the UI/UX guys are trying to create a design system whilst redesigning the internet banking system and app, backed by the CPO and CTO (!?). I mean, I'm not the one calling the shots, but neither a deisgn system nor redesign should be a priority for a least two years.
What has bugged me in the past (and why I don't like being just a 'coder') is that... hey - people in my position have a perspective few others have. Sometimes we can see things that others can't, and generally we're smart enough to understand the business impact. If you're being asked to implement 'business logic' all day, for months or years, at some point, whether you want it or not, you can see how a business is being impacted by things that you can see. Raising a flag like "hey, xyz should probably be a priority..." and being dismissed because you're just a coder and don't understand the business - besides being insulting, sort of doesn't really jive with reality. In many cases, the software team are the only people that actually have a strong understanding of 'the business' - how many of the pieces fit together, etc.
Strongly agree. The biggest barrier between devs and refactors with zero interface impact is AGILE mentality of always aiming to deliver value to the end user with every deploy. Business people just don't understand how much of an impact crappy implementations and error handling does have on the end user. We see 5~6% error rate, which represents hundreds of thousand of people daily, but shipping a new "feature" (that within months will be used by a few hundred people with a very high bounce rate) is always the top priority.
From time to time there is a meeting with the following subject: "why are users not using the basic features", and the business people's answer is always "the ui is outdated" or "the menu is confusing the user". Those answers are gathered by talking to some random users on the streets close to the company building (I'm not making this up).
seems to get back to "what gets measured" mantra. And, reminds me cell phone company churn. There's loads of things that could be done to improve service for existing customers, but companies spend budget chasing 'new' customers to 'switch' with low rates for X months, then jack up the price. "Loyal" customers get ignored.
UI / UX redesigns should be tested with small amounts of users, with all key metrics measured, and see what happens to those metrics and user retention after a few months. Otherwise, UI redesigns has a chance of causing a lot of destruction both by loss of users and bugs. Fortunately for software this isn’t that difficult to do. Other tasks, less so or impossible.
Some of these redesigns that don’t work out well could have been worked on by brilliant people that were very cautious about what kind of work they take on. But you don’t always hit it out of the park.
But yes, you're right, happens all the time. Less so with most of the large scale more popular redesigns people tend to think of when writing articles like this about tools they actually use; the team at Atlassian, for example, is not made of idiots, neither at Slack, Google, Twitter, or other large companies with mostly significant design experience.
Smaller operations where we all likely work—yep, hit or miss.
It's my understanding the use of the word "idiot" in this context implies someone who is primarily responsible for a significant amount of rework on anything that bears no real fruit, ui redesigns being one potential example. Pretty sure big companies make those mistakes just as much as small. Though I don't think its fair to call someone an idiot for this reason--I think its very challenging to do well.
Also, they are relatively responsive to developer demands, at least as far as the dashboard is concerned. Not that long ago, if you wanted to export a few seconds of logs, you had to setup a Cloud SQL sink that could suck in gigabytes of logs. Not too helpful if you want to analyze just a few hundred lines. People complained, and now you can export the current view to excel/csv. They've also speeded up load times significantly (it's still not snappy though).
But on the notion that large companies specifically don't have hit or miss design or redesigns: I'd argue there's more than enough evidence to the contrary. And, personally, I find Atlassian products to be a very good example of that.
Note: In this regard, I focus mainly on Don Norman's view on "design", which is largely orthogonal to aesthetics. It's cool for software to look nice. But if it's laid out in a non-intuitive way or doesn't prevent (or even provokes) user errors, it's not good design, period.
Proper (re)design initiatives need to born out of the intersection of "viability, (user) desirability, and feasibility."
Usability is only scratching the surface of how to quantify the impact of a redesign and the author doesn't acknowledge the convoluted nature of how design decisions actually get made in non design-led tech organizations. The best companies (i.e. FAANG) have data and are measuring the outcomes of design decisions before developers even get assigned the work.
From the author's vantage point and how they get assigned work, they are missing the forest for the trees.
Thoughts?
You're contradicting yourself here. If someone with authority is convinced that something is a good idea, then they have a reason for doing it. It might be a misguided reason, but it's not just randomness.
Did you read the article? The author specifically says, "Before all of the UI designers that read this go out and riot and champion against me for saying UI redesigns are a waste of time, let me say that I do value design. I think at the bare minimum, a product or website needs to be usable, and if you possess a good eye and steady hand, you should feel compelled to create something that looks pleasing."
He then goes on to say, "Just stop redesigning the UI all the time. UI redesigns, in my opinion, are a waste of time 95% of the time. Let me explain further."
That's not so contentious IMO. Redesigns can be too frequent and the purported purpose of redesigns is typically nebulous, and can be driven more by politics than any of the objective metrics that you describe.
> People aren't idiots. They don't do this work for no reason. Try to understand and respect the work outside your own department and specialty.
Of course they have reasons. That doesn't make those reasons objectively correct. Maybe you should try to understand and respect the point the article is trying to convey, that perhaps the pendulum on UI redesign has swung a little too far one way.
You don't even need to appeal to some 'objective correct' standard. You can just look more basically at "what is the purpose?" Usually, it's "increase sales". So... determine baseline metrics, perhaps implement some testing to see what changes have what effect, and then push forward a larger redesign effort if the tests moved towards the goal/purpose.
Perhaps the goal is 'reduce number of clicks'. Is that really important? Or is it 'reduce user frustration'? How will you measure that?
"Reduce page load time" - should be pretty easy to measure, but will it have an impact on other things (sales, support, etc)?
People may have 'good reasons' for a redesign. Without a measurable goal, they're a waste of time, imo, and I've often seen them do more harm than good (measurable harm, like reduced sales, customer drop off, etc). But hey - those front page pictures looked really nice in the photoshop mockups sent over...
Please don’t do this.
> Maybe you should try to understand
Or this. Reminder: be civil, don’t be snarky.
> Please don't insinuate that someone hasn't read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that."
Your first paragraph is just as strong with its opening sentence (“Did you read the article?”) removed.
The guidelines also say:
> Don't say things you wouldn't say face-to-face.
The final sentence of your last paragraph could have been phrased: “The point the article is trying to convey is that perhaps the pendulum on UI redesign has swung a little too far one way.”
I get that you were mocking the “try to understand” from the parent comment, but your comment would have been stronger by not doing so.
> holding up a mirror on a bad comment isn't an uncivil or snarky reply.
The bulk of your comment is polite and civil, but the opening and concluding sentences are attacking the the commenter, not the comment.
($0.02. Just trying to keep things polite around here.)
HN's guidelines also suggest avoiding unrelated tangents, so this will be my last post debating rhetoric and HN guidelines.
Remember, their goals aren’t the same as your goals. Your goal is to get the best email tool possible. Google’s goal is to extract as much money as possible from you and your data...while still being the best alternative to competitors.
Those goals are very very different. Most of these comments are so naive. It’s almost as if most people have never seen the amount of actionable data the average digital product throws off.
A smart default assumption, especially when it comes to the big guys like google/Facebook; the UI changed because it makes the company more money.
It's very rare that a redesign had me saying, "Oh wow, that's so much better!"
So many UI fads have set usability back but get repeated with most redesigns... hamburger menus, login forms that hide password fields until you've entered the username, ultra minimal forms that leave the user guessing what is interactive, text fields with labels only approximated by gray text within that field, and on and on.
Many old UIs were uglier but more usable.
Could write a whole blog post on designing for UX change. I think I’ll do that...
OTOH, this also means that for a user who has used your product for ten years, the fact that your search bar is, in fact, not in the top right, doesn't matter -- because they have learned where it is. If you move it, they will be upset, even if the new design might objectively be more intuitive (as in: new users have less trouble with it).
This effect can make it rather hard at times to judge if a redesign of a product you've used for a long time is in fact as bad as you believe it to be.
I've been lead to believe that this is for websites that support authentication by multiple methods. If you submit your email address first they can look it up and see that you auth with SAML, or log you in through Google, or if you login with a password they can then render that form for you.
The hamburger menu _replaced_ the style of menu we used to have, where all the options were under their own menus with titles ("File", and so on). That was lost. The only reason they were left behind was to make it work well on tiny screens. If you don't have a tiny screen, you just lost functionality that you were familiar with and that worked, for no reason.
At my previous company, we did a minor visual design refresh of our ancient software because our sales data showed that one of the top objections cited by prospects was that the software looked old.
Although the visual design refresh did nothing for usability, it completely eliminated that objection and enabled our sales team to focus on how our software could improve our customers’ businesses and why it was better than our competitors’. The redesign improved conversion rates.
The redesign caused a bit of consternation among existing customers, but they got over it quickly. It had no observable effect on retention/churn.
If you were a PM on my team unable to substantiate why the work you’re scheduling helps the business (by making life better for customers or by reducing purchasing friction), you wouldn’t be on my team for long. These pointless redesigns are amateur-hour stuff.
Of course, there are other legitimate reasons to do a redesign, like maintainability and developer retention/happiness, but those are much riskier and even more difficult to justify.
I believe in making products aesthetically pleasing. I spend a lot of time ensuring my products look good because I know that this is the first impression of any product. I'm constantly improving the design of my products in subtle (and sometimes not subtle) ways.
Full redesigns are the design equivalent of full software rewrites. They suffer from all the same issues: second system affect, loss of functionality, loss of knowledge, etc. And like software re-writes, sometimes they are necessary but often they are not.
The MS ribbon was a classic redesign. It broke the standard menu metaphor and crashed productivity for no good reason.
Flat design was in a similar league, but not quite as bad. Is that a button or a text element? How can anyone tell?
Refinement is a much harder challenge. Improving the aesthetics of something while making it subtly easier to use is a really difficult thing to do.
I loved it, it's do much easier to find stuff if you already don't know where it is.
Great design for the casual Wordster.
1) You can absolutely botch it. A good example of that is Sibelius: Their Ribbon does not make any sense at all (and is in multiple instances literally a waste of space). Personally, I find the ribbon design on MS Office to be much better, though; MS has clearly put much thought and experimentation (i.e. many studies) into the concept.
2) What I find to be extremely interesting: For MS Office, the ribbon introduced better shortcuts. Since Office products are totally overloaded with functionality, the parts you don't use often were usually left behind in terms of useful shortcuts. With the Ribbon, these functionalities are usually accessible via a Spacemacs-Style mnemonic keypresses. If you use a specific functionality over and over, it's now much easier to remember a not-so-bad way to trigger it from the keyboard.
On another note:
I also find the "new" formatting context menu that pops up in MS Word whenever you select some text to be a very clever idea. It remembers me much of an old Xerox demo[1][2] that was done with a mouse and a trackball simultaneously (featuring a palette you could place around where you were currently making changes with the mouse). I'm convinced that to this day, there's a lot of ignored potential in that concept.
[1]: https://www.youtube.com/watch?v=VpTFcItyE9w [2]: https://www.billbuxton.com/TGtaxonomy.html
It doesn't mean you can't add new features (or code), but doing so leads to trade-offs.
The real difference with the ribbon is that computing shifted from professionals and workers to everyone. The audience that cares about old style windows menus is vocal and tiny. Users struggled to discover, locate and remember items in the old menus. Many users struggled to find the menu.
That said, the Mac menu system is the best implementation of that type of menu delivery.
I thought I'd eventually get used to it. Nope. It's still significantly less productive than a standard menu.
If you think menu's promote discovery better, you haven't looked at the Visual Studio menus in a while.
That aside, your post mostly fails to address the critiques in the OP. Yes, a pleasing UI tends to feel better to use, but most of these pretty redesigns throw away important other traits an old design had, or just simply lack them. It's hard to positively compare (for example) New Gmail with Old Gmail when they managed to make it slower and break the reply button, for example.
It uses like a mb of ram and loads instantly.
https://mail.google.com/mail/u/0/h/1pq68r75kzvdr/
You should see a banner with an option to 'set basic HTML as default view' across the top.
It's great. You see all the information - nothing hidden behind icons, and page loads between screens actually take less time than with a SPA.
Well that explains a few things. Many a time have I experienced a UI remake looking great but being absolutely horrible to use.
Take for example Google+, where they tried a last ditch effort to make it more popular by doing a UI update. They made it look really slick, but in the process made it much, much worse to actually use. I used to be an active G+ user (yeah, I know) but after they forced me to use the new UI I stopped using it, it was that bad.
Another example is Acronis TrueImage, which completely redid their UI, making it much more visually pleasing and up-to-date. Initially I thought it was great, but then I noticed that certain processes were a lot more tedious to do, and they'd also removed a lot of functionally in the process.
So really, the important point is that you can gain affordances for usability sins if you have a design that is appealing to people as modern or otherwise trendy.
By the same process: if you have a design that was 100% usable, then redesign and end up making usability mistakes, there's a good chance you'll see net-zero or negative from the prettier UI in your testing.
For the majority of companies that do not have focus groups, usability labs, and a design staff that can spend cycles on R&D, it seems you may be better off doing little more than reskinning existing UI controls to maintain trendiness than full-scale re-wires of your existing product at any time to maximize the aesthetic-usability effect for minimal design work. Examples you cite in a sibling comment have cash to burn on exactly this, however I think that is the exception rather than the norm for businesses at large.
Visual (aesthetic) design change buys goodwill, reinforces and differentiates brand image, but IMO is mostly a marketing tool at the end of the day. I see product design and visual design as sister disciplines that must communicate, similar to two people running a three-legged race, but it is easy to improve one or the other separately from the other in most iterative scenarios. Large-scale redesigns are usually risky, and Snapchat's a great high-profile example of a company that was able to hire talent and let that process go off the rails.
I wouldn't frame it this way, but there are many confounding things in measuring a change in the UI design.
I jumped from web consumer to operations, and the mindset is so different: in web, you have shallow actions that you want things to be easier and look aesthetically pleasing. In operations you want deep actions that require reliability or learning, and that require every or many users to do it, changing the UI is a nightmare for them. It has to be vastly better to compensate the change. And not only that, you need your operations to be more efficient than your competition: a bad ui can cause issues in an entire company.
In consumer-web, pages like reddit changes their entire UI to have posts read in the same page and its use-it or lose-it. Consumer web cruises along the monopolistic positions they have to spend resources without visible consequence. Who cares if reddit's ui is 10% snazzier or 10% snappier? It's not like the reddit user will stop using it because of it. That redesign happened in a company that raised half a billion dollars.
The most visible feature of many of the sites I visit are the attempts to get me to do something other than what I went to the site for.
It's possible you may need to redo UI for new search. If I add faceted search or geo search, for example in my search update, I may well need to redo the UI in a way much more fundamental than aesthetics.
UI design doesn't involve BE design in any way. So?
I wish there were better resources for non UX people like me to learn how to tell the difference.
You could just start learning about UX. It’ll make you a better engineer!
But I generally agree with your sentiment; you can absolutely find "just trust me" in software development. You can also probably smell it out better by learning about it more.
You’ll find a lot more about empirically driven methods to evaluate your UI, mostly from a productivity perspective. I personally find it fascinating!
You would think so, but the amount of 'developer superstition' and and 'gut feeling' I've faced in development is quite high.
Visual changes are irrelevant at best, and actively harmful at worst.
By all means, improve the website and the design, but actually improve it.
A negative one, based on what you quote:
"This aesthetic-usability effect can mask UI problems and can prevent issue discovery during usability testing."
Which seems to be saying that the uglier you make your UI, the better your chances of having actual usability issues surface.
After the fundamentals are solid it’s then important to apply appropriate aesthetic and interactive elements to polish the experience.
Simply jumping to visual design after skipping the fundamentals is nearly assuring a failure. It would be akin to worrying about performance and scaling of product’s database and API without first considering if the data schemas and underlying technology stack even meet the operational needs.
Addendum: “Evolutionary design” instead of “revolutionary design” is typically preferred if one would like to keep a connection between how something was done before and the (hopefully) improved version.
On the other side, it will be less usable while i have to relearn how to use it. This is not an issue if it happens from time to time, you pay upfront a decrease of productivity and will be rewarded greatly later on. But in the era of SaaS we are constantly subject to a stream of redesigns, sometimes small, other times global. You cannot finish adapting to a change that another comes.
I don't know about others, but for me is deeply frustrating.
For example, just a few months ago, Google used square rectangles for the search bar, and advocated "cards" with sharp corners in their material design standards. However, just recently, they updated gmail and google search to use rounded rectangles in the search bar instead of rectangles. Are rectangles better or worse than rounded rectangles? Yes? No? The answer is, it doesn't matter for usability. But because Google is so big and has such influence, now, if your site uses a rectangular search bar with sharp corners users will perceive it as "dated".
There are many similar examples of this. Microsoft's metro UI was cool and popular for maybe a full 6 months. Clean Helvetica font was everyone's aspiration, then Google pushed Lato, and now it's Robato, until they change their mind again. Small 11pt font used to be the norm, then very large readable 14pt font was the norm, and now we're back to something like 12pt. Single page applications a while ago were avoided, then became so popular they were effectively a pre-requisite, and now they should only be used "where appropriate".
I think Google make these changes not to make their site look good and refreshing, but to make everyone else's look old and dated.
They did? Their iPhones went from rounded corners, to sharp corners, back to rounded corners again. Apple design is impressive, but I don't see any timeless consistency.
Find another human interface that consists of sharp edged shapes. That design aesthetic is like brutalist UI. Pretty for the architect, but few others are moved.
Sharp edges convey precision, rounded edges convey approximation. Many mechanical knobs and buttons have clear notches and clicks to make clear to the user they are in control of the machine.
Thank you for explaining these concepts to me, I have not heard of the aesthetic usability effect. I will read into this as I am curious what it is now.
To be clear, I do value design. I think design is important and I write that out in the article that I value design. What I struggle to value are redesigns, that is, complete redesigns of a UI - instead preferring incremental updates of the UX that is necessary to use the product or application.
Thank you for the work that you've done, as I'm sure you have had a great impact on the customers you've directly and indirectly served. Continue to do design, because if it were up to me, nothing would look good at all.
Cheers.
Of course perception and reality are different things. And I imagine that effect is only really true for, at best, some slight statistical majority. Certainly I know a lot of people who've stuck with older versions of software because it looks and works like they've come to expect, and I myself tend to judge the usability of new software by how much it looks like a Win95 application.
The thing I love most about only developing software for in-house use (because my company doesn't sell software) is that nobody really cares what it looks like.
You can see a large fraction of the users have taken the time to optout, perhaps as much as a third (!) of those who can. Considering how passive most users are, this tells me that the new & expensive Reddit design is indeed loathed.
Necessary for what (or for whom)?
Usually that means redesign on the quick which always equals missed features. The classic example is when everyone jumped on responsive web design. Many applications and sites ended up including 80% of the elements of the desktop page and dropping other elements. Like my bank, who eliminated the ability to see your routing number and account number.
UI developers are getting marched out the door at a well known publisher right now, their services no longer needed. UX is a different story with this mystery publisher, they now get to call a lot of the shots.
There is a bigger discussion to be had regarding the whole visual design process. In 2006 when you could have your navigation in any corner of the screen with any design for the search icon it made sense to have UI designers add their special flourishes. Now we know where the navigation goes and what the icon is for search, that has all been settled. User experience still needs some people to take care of it as we can't leave that up to the programmers, can we?
As an example, as contractors, we fill up timesheets very often. Our company decided to move to another 'aesthetically pleasing' platform which to me as a user is same as a redesign. Now the click - tab - 8 - tab - space - cmd+w ritual is taken away. It now goes like this : load page - login - click link - click a drop down - wait for it to timeout (dont even ask me why) - click again and wait for the dropdown to populate and close itself - click again - select - click - 8 - click save - find the mini'x' - click - select another dropdown - click submit (no, space no longer works on this form).
This new platform has more options, more whitespace, more corporate colors. Agreed. No colors, whitespace your redesign could add will soothe the agony of poor usability.
Cool, cool. To preface this comment, I'm a guy who owns a computer and uses software.
Most GUI redesigns I've seen in the past 10 years make the interface prettier, but LESS usable. The new design usually incoroporates three categories of changes:
1. Lists of items are rendered in a larger font with more spacing between items, leading to lower information density, thus requiring more scrolling. (For bonus points, often a window that has a scrollable area isn't resizable, so you're stuck with whatever arbitrary viewport size the designer decided was large enough.)
2. Controls that used to always be visible are now hidden until you hover or click the right spot. This is done to reduce "clutter", as though controls are somehow graffiti.
3. A bunch of convenient shortcuts enjoyed by long-time power users weren't reimplimented in the new design, because the designer didn't know about them, or simply didn't think they mattered.
I have a WordPress blog. WordPress recently overhauled their entire editing UI, and I hate it. When I started the blog several years ago, I was able to figure out how to use WordPress by exploring the UI. The new UI is an extreme example of #2; when you go to write a new post, the page is entirely blank. You have to click somewhere to get a text cursor, and there isn't even a visually delineated text area before you do so. There are a couple of features I had to hunt around for, and I wouldn't have even known those features existed if I hadn't learned them from the old UI, which presented them front and center.
My company uses JIRA for bug tracking. They switched to a new GUI a while back, and I hate it. It's harder to find things that used to be presented front and center. And as an example of #3: It used to be possible to just type an issue number like "392" in the search box, hit Enter, and be brought immediately to that issue page. Not anymore; if you do that quickly, you get a "no results found" page. If you type the number and then wait a couple of seconds, you get a list of search results, which you can then click on. Pressing Enter then takes you to the first one, but often that is NOT issue #392, it's just some issue that happens to have the text "392" somewhere in it. So you have to eyeball the search results, and then click the right one. The old way was more convenient. Fortunately, I eventually found the preference to switch back to the old GUI, which they helpfully give you because they apparently realize that the new GUI sucks. (I don't know offhand if it reverts the search behavior, because I've already changed my habits to not use it anymore.)
Let's be honest, aesthetic-usability effect is too insignificant to ever prioritize aesthetics over usability and pretty much no company in the world can benefit from it. It's just a justification for producing pretty looking interfaces with awful UX, because UX is hard, a typical designer on the market likely can't even do it and eye candy is more easily sellable in hierarchical organizations, where everyone can impress their bosses all the way to the top.
Of course, in the first 10 seconds or few minutes, but I suspect strongly this effect fades over time.
Most UI redesigns are bad because they focus on the wrong things and throw out a lot of good things, or change for the sake of change.
I see the same thing happen all over the place--branding and UI are very common victims.
Music editing has the same issues as well. Even in the short term - over the course of a day your ears can get tired of a specific set of sounds and you don't hear with 'fresh ears'.
I probably don’t mind a new skit because I’m just looking to be entertained. But I’m mostly looking to get shit done with something that had an actual UI to it, so freshness can be more hit-or-miss.
This is part of the general phenomenon of looking for your keys under the lamppost.
It's easy to do an experiment that tests how people feel about your new design after looking at it for a minute and a half. Want to compare how people feel about the old and new designs after six months of getting used to them? That will take at least six months.
But I'm going to disagree that an hour is enough to reveal any advantages and disadvantages that may be present.
And unless the software is quite simplistic, 5-6 people is just enough to falsely validate the preconceptions of the UX designer.
the first 10 seconds of ux is extremely important, since it's basically the top of your funnel.
[1] https://www.weidert.com/whole_brain_marketing_blog/bid/11696...
However, as people start to actually use the site, I think they care a lot less about a lot of cosmetic things.
That's definitely true, _if_ they start to actually use the site. You need something to hook them in the first few seconds.
This means the OP is correct. New paint doesn't make it more useful. To really help users, optimize for usable design, not just aesthetics.
This seems like a call to seniority. Just because you've been there for X more years doesn't make your input automatically more valid. I get his disclaimer i.e. 'I am not a designer', but yours just feels a bit like bragging.
Cool, cool. To preface this comment, I'm a user experience designer, and I've been doing web software development and design for over 20 years.
In reality, your conjecture turns out to be largely untrue. Visual design quality does have an impact.
Main principle you want to look up: the Aesthetic Usability Effect. Basically, users perceive your product to be more usable if it's aesthetically pleasing.
> Summary: Users are more tolerant of minor usability issues when they find an interface visually appealing. This aesthetic-usability effect can mask UI problems and can prevent issue discovery during usability testing. Identify instances of the aesthetic-usability effect in your user research by watching what your users do, as well as listening to what they say.
From https://www.nngroup.com/articles/aesthetic-usability-effect/
See also: https://www.nngroup.com/articles/perceived-value/ (other ways users perceive value based on the UI)
Of course, this has limits. A rebrand or redesign that, all other things equal, is mostly the same quality as before probably won't get much benefit. I've seen many redesigns and that tends not to be something people do—there's usually a good bump in visual quality in the process.
So, regardless of whether you, personally notice the different functionality, many redesigns are actually a success at improving the perceived value, perceived usability, and overall evaluation of the brand, company, and product.
People aren't idiots. They don't do this work for no reason. Try to understand and respect the work outside your own department and specialty. Building respect across those boundaries is a rare and valuable thing.