> People spend many hours perfecting their workflow in one environment and FLIP THEIR LIDS when someone changes it. It's not a rational thing
I've had some thoughts on this recently, and wholeheartedly disagree. We spend aeons engineering stability into every other interface within a software ecosystem, since it's supposed to improve stability, reduce surprising breakage, improve engineer efficiency, discoverability, etc., but when it comes to interfaces in the user plane, it's like the only established methodology is FUCK YOU Driven Development.
In these systems, and Gmail, the user is not considered an intelligent, complex actor in the system, but instead something more like a child sitting in a cinema whose only criteria for synchrony is to be repeatedly dazzled by confounding changes to the way it interacts with the system.
This is fundamentally wrong in so many ways. Not least, the user is the main purpose for the existence of these systems (er, right??), and yet the user's interface to the system is the one most likely to functionally break without warning.
You cannot address the reliability of the entire system without considering the last mile - dropping a change the size of the Gmail redesign on millions of users without a multitude of small iterations, or with a huge amount of fanfare and warning, is an unmitigated disaster for the reliability and efficiency of the overall system.
I don't give 2 fucks how much of the scientific method was abused to create the new system up to that point, if it doesn't comfortably fit the millions of delicate tendrils that have grown between my mind and it, then from the user's perspective the change is much closer to an abject failure.
I suspect in years to come this will be an increasingly important area for study, and I pray the outcome to some extent will simply be that corporations will need to give up achieving quick feel-good wins by arbitrarily fucking with the user-machine interface, although I could be wrong. We could always be further reduced to that mindless entertainment-only child in the cinema, responsible only for the most basic direction of the outcomes of our interaction with the overall system, the tacit attitude of the large corporations as they drop huge changes like this without warning.
The outcry we hear over these changes isn't just bored people being picky, it's the sound of a trillion dying neurons in a million interconnected biological systems. Much as a fully grown cat wouldn't fare well being stuffed into a jar, the users here suffer just the same. Thin the cat's diet slowly over time, widen a border here, replace some text with an icon there, and the small bits of death and shrinkage that occur over time will mean that cat will soon be ready to contentedly purr its way into that jar and fall into a dreamy slumber all of its own accord.
Gmail gave people months to use the two interfaces side by side before dropping the old interface. And they flooded users with notifications of every incremental change, and were roundly mocked for that too. It is impossible to satisfy everyone all the time.
Keeping the old interface was a good move, although it only (at least for me) leads to procrastination. The same problem exists, which is the mental adjustment that you need to make at some point.
Another interesting angle is that in the new interface, they had to add a dropdown menu to control the amount of padding used on UI elements (compact, cosy, comfortable). Had they gradually moved from compact to cosy, then to comfortable over a longer period, the need to provide an option might have been removed entirely. So some of the complexity avoided in having incremental changes over a fixed term has instead become software complexity needing maintained over a potentially longer or indefinite period.
In either case, a gradual transition would avoid the need for all this. For me, the two biggest gotchas with the new design was the text->icons change and associated relocation of some buttons, and the border change. Had the text->icons change been introduced distinctly, and allowed to stew for a few weeks - months, then the border size changed from compact to cosy for a few months, I possibly would have had no reason to complain at all (the amount of adjustment/effort required for each individual change is amortized over time, and by the time a new change appears, my comfort level has already returned to maximum for the current state of the UI).
The outcry we hear over these changes isn't just bored people being picky, it's the sound of a trillion dying neurons in a million interconnected biological systems.
You seem to be suggesting that having to learn something new is like having your brain die. That seems inaccurate. Isn't learning a (not very) different interface more like having to exercise a muscle a little bit that you were hoping not to exercise? I mean, not a cool thing to do to your users if the new interface is worse, but not inherently a bad thing.
It's the sort of thing that happens when a priesthood in a field comes to possess the One True Knowledge. They start to issue statements like "you can't trust your intuition" and "you don't understand this enough to like it yet"
I've had some thoughts on this recently, and wholeheartedly disagree. We spend aeons engineering stability into every other interface within a software ecosystem, since it's supposed to improve stability, reduce surprising breakage, improve engineer efficiency, discoverability, etc., but when it comes to interfaces in the user plane, it's like the only established methodology is FUCK YOU Driven Development.
In these systems, and Gmail, the user is not considered an intelligent, complex actor in the system, but instead something more like a child sitting in a cinema whose only criteria for synchrony is to be repeatedly dazzled by confounding changes to the way it interacts with the system.
This is fundamentally wrong in so many ways. Not least, the user is the main purpose for the existence of these systems (er, right??), and yet the user's interface to the system is the one most likely to functionally break without warning.
You cannot address the reliability of the entire system without considering the last mile - dropping a change the size of the Gmail redesign on millions of users without a multitude of small iterations, or with a huge amount of fanfare and warning, is an unmitigated disaster for the reliability and efficiency of the overall system.
I don't give 2 fucks how much of the scientific method was abused to create the new system up to that point, if it doesn't comfortably fit the millions of delicate tendrils that have grown between my mind and it, then from the user's perspective the change is much closer to an abject failure.
I suspect in years to come this will be an increasingly important area for study, and I pray the outcome to some extent will simply be that corporations will need to give up achieving quick feel-good wins by arbitrarily fucking with the user-machine interface, although I could be wrong. We could always be further reduced to that mindless entertainment-only child in the cinema, responsible only for the most basic direction of the outcomes of our interaction with the overall system, the tacit attitude of the large corporations as they drop huge changes like this without warning.
The outcry we hear over these changes isn't just bored people being picky, it's the sound of a trillion dying neurons in a million interconnected biological systems. Much as a fully grown cat wouldn't fare well being stuffed into a jar, the users here suffer just the same. Thin the cat's diet slowly over time, widen a border here, replace some text with an icon there, and the small bits of death and shrinkage that occur over time will mean that cat will soon be ready to contentedly purr its way into that jar and fall into a dreamy slumber all of its own accord.