6 ms·
Counterpoint: as a user, while you realize you hate the frequent changes in UI and workflow -- you're not realizing that you're using software with a much bette
by crazygringo 4y ago
Counterpoint: as a user, while you realize you hate the frequent changes in UI and workflow -- you're not realizing that you're using software with a much better UI now overall than it would have been if not for the frequent experimentation over the past e.g. 2 years.
Rapid release and experimentation means ultimately finding better solutions for the users faster. If you go slow, things don't change as much but they don't get better much either.
We tend to assume that all of the good changes would have happened anyways and all the bad changes are because of rapid release.... but that's not how it works.
- candiddevmike 4y agoYour entire counterpoint assumes the UI improves...
- Godel_unicode 4y agoThis is an excellent example of the headwinds/tailswinds asymmetry; we often don’t notice when a rough edge gets sanded off the UX but we scream when one gets added.
- 411111111111111 4y agoI disagree that ui changes in general are an example of this. You'll be able to find examples such as that, sure. But that doesn't make it generally true.
- jacobr1 4y agoOne of the keys to rapid iteration is having a good feedback-loop. So if there are UX regressions, they can be rapidly identified and rolled back.
- wizofaus 4y agoShort of having an army of testers whose job it is to continually retest the same UX sequences with every release, how is that possible? Rapid release to me implies releasing changes faster than they could possibly be manually tested. And automated tests are going to do a rotten job of detecting most UX regressions.
- jacobr1 4y agoYou need to instrument real user activity on the site, like tracking shopping cart completions for retail.
- wizofaus 4y agoSo you're saying that the way to maintain a stable UX...is to release changes directly to customers (or at least a subset of) to test, and if they react badly, roll it back?
- jacobr1 4y agoIt is one part of more wholistic UX/PM practice. Yes, you should have mechanisms to validate the impact of your changes on your customers. You should be having regular conversations with various subsets of your customers for qualitative feedback, both on specific changes and roadmap. You should be doing things like heuristics reviews and user-testing. You should have UX designers with experience designing interfaces with plans for gather feedback _before_ deployment and then validate that change _after_ the deployment with further analysis. During development you also need all the regular QA type testing as well. But yes, if you are regularly changing your UI in order to improve your system and roll out changes, you need to validate the impact. When I was last a PM, I spent a bunch of time monitoring the rollout of changes via Pendo to understand BOTH, if was getting the adoption of features I expected from certain cohorts and seeing if there where any shifts in user behavior (either organically, due to intentional or unintentional changes) And we did this for "beta" groups as well to really validate that feature were working with early adopters before broader rollout. I guess you might not consider the later "production" in sense, but these were real customers with real workloads.
- lazide 4y agoIn my experience, that only happens when customer attrition is double digits. Otherwise, everyone has their head up their ass enough they’ll ignore or spin the feedback at 99% of organizations.
- JohnFen 4y agoThis an interesting point. I would disagree that UI constantly improves, though. I can think of lots of examples where the opposite is true. But that's not due to rapid release, that's due to other issues. > If you go slow, things don't change as much but they don't get better much either. It's hard to think of when I've seen improvements that were so good as to be worth the cost, though. Things certainly change, but change is not always better, and even when it is, it's not always worth the cost to the user.
- torginus 4y agoYou are posting on a site that is performant, light on resources and has great UX - and has been mostly unchanged for a decade. Its counterpart, Reddit has only regressed compared to its biggest competitor, it's old self. I haven't noticed any significant UX changes in any software I use in the past two years, and would struggle to name improvements, even over a longer timeframe.
- dntrkv 4y ago"Great UX" If HN had such great UX, there wouldn't be multiple browser extensions (and clones) that focus solely on fixing the UX. I'm not saying the UX is terrible, but I wouldn't call it great. I think the best term for it would be "consistent." It's basically Craigslist. It's fine if you've been using it for years and have adjusted your behavior to work with its quirks, but it does not provide a smooth experience that would work for a community you're starting today.
- mod 4y agoWhat types of changes would you make?
- wizofaus 4y agoThe grey text for posts needs to go, I always think it means they've been downvoted, and is surely insufficient contrast to be WCAG/508 compliant.
- plorkyeran 4y agoLight grey text does mean that the post has been downvoted below zero.
- wizofaus 4y agoMy understanding is that that's only true for comments not posts?
- 4y ago
- horsawlarway 4y agoI think you're missing an obvious dichotomy here. Better UI is not universal. And the absolute, hands down unquestionably best, UI that can possibly exist for any given customer is the one they're already an expert in. Can a different UI end up being better for them? Sure. Will it be better the day it's released? No. The user has to pay a cost every time the UI changes, regardless of whether it's actually better for them or not (and it will never be better until much later, once they've become an expert in the new version). Worse - I see more and more companies optimize UIs for the "initial user experience" and onboarding new users (more paying customers). The sad truth is that many times that means dumbing down a much better UI for the "already expert" customer - just like putting training wheels on the bike is great for the person that's never biked, and utterly infuriating if you already know how to ride. This is why existing customer bases are so rarely fond of any change - regardless of whether they end up liking it in 3 months time. It has a real cost, right this second, and they're being asked to pay it.
- lazide 4y agoIt’s also an existential risk for many business customers. If you already spent months training a new hire on how to get something working with all the different random tools and software they use, changing something meaningful means breaking that persons ability to do what they need to do for their job, at least for some time. Even changing something inconsequential will confuse some users for a bit, require making/updating new training guides, etc. If it’s a business on the edge or under during a stressful period? That can literally tip it over and make it non functional. That is especially true for small businesses.
- crazygringo 4y agoBusiness productivity software is usually much more slow-changing than consumer software, precisely for this reason. They know customers' training guides need to be rewritten so changes become a big deal. This is one of the reasons business productivity software becomes unwieldy after a while -- it's fine to add buttons and menus, you just can't change existing ones or what they do. So then version 5 will finally introduce the massive, desperately needed UI refactor after ten years, while plenty of clients just stay on version 4. (An example of this is the Blackbird CMS -- old Blackbird vs new Blackbird.)
- plorkyeran 4y agoIt is very unusual for software that's been around for a while to actually have better UI than it did two years ago. Every time I pull out an old laptop or phone running 5+ year old software I notice that things look different and buttons are in different places, but functionally there's very little difference. Most changes to already functional software are just changes. They aren't improvements or regressions; they're just making things different.
- pdntspa 4y agoWhy do you assume the changes automatically mean "much better"? In my experience it feels about 50/50 for better/worse, whether that is features taken away due to some business concern, blatant contempt for existing muscle-memory, or misguided designers reworking things that did not need a rework.
- oceanplexian 4y agoPick up a vintage Mac and a copy of Word from the 90s. The UX is superior in every way to modern word processors. It’s more responsive, more intuitive, faster to start up, more reliable, easier to learn, and so on. Decades of “experimentation” have not improved the act of typing out a document in any meaningful way. Now, they have improved the experience for the corporations who can profit selling out their users data to the highest bidder and locking them out of their own devices while charging a subscription fee.
- jameshart 4y agoThe rose tinted glasses people have for old computers. Here’s a transcript of me using a Mac SE in 1995 to try and finish writing a college essay in Microsoft Word: Chugchugchugchugchugchugchug Watch icon Chuchchugchugchugchug Disk eject sound Please Insert the disk ‘Docs 1’ Clunk Watch icon Chugchugchugchugchug Word count: 2351
- int_19h 4y agoThat is a commentary on the performance of that software, not on the quality of its interface. Run the same app on a machine from 2000, and it'll be blazing fast - and have sane UX.
- jameshart 4y ago> more responsive, more intuitive, faster to start up, more reliable, easier to learn More responsive? No. No it wasn’t. Disks were slow. Memory capacity was low. You used to have to use third party RAM disk software to complete some tasks in a reasonable time. Or install a ram doubler to let you work on reasonable sized documents at the expense of slowing your machine down even more. More intuitive? Hard disagree. The example I gave above was of getting a word count. You had to find the menu option to do that - it wasn’t just visible on screen. Same with spellcheck. Global search and replace was slow and clunky and felt risky. You only had one level of undo. Faster to startup? Hells no. Again, slow disks. More reliable? There was no auto save. Everyone who used a computer in the 90s has a story of losing hours, or even weeks of work to a crash. Everyone. Easier to learn? Learn how? Word came with a few hundred pages of dead tree manual, but if you were on an institutional machine or running a ‘borrowed’ copy you didn’t have that. There was no internet to look up how to do stuff. Maybe you could pick stuff up from the tips section of a magazine? Sure. It was super easy to learn. Compared to all of which, google docs or Word365 is just… light years ahead.
- lelanthran 4y ago>Counterpoint: as a user, while you realize you hate the frequent changes in UI and workflow -- you're not realizing that you're using software with a much better UI now overall than it would have been if not for the frequent experimentation over the past e.g. 2 years. CounterCounterPoint: If the software was perfectly functional two years ago, all that can happen with a change, any change, is to make it worse :-)