4 ms·
Based on my experience and that anecdote, I think the lesson might well be that users of existing complex software hate any change. Maybe it was "hard to learn
by jrochkind1 3y ago
Based on my experience and that anecdote, I think the lesson might well be that users of existing complex software hate any change.
Maybe it was "hard to learn", but they had existing customers anyway despite that who found value of some kind, and their existing users have already not only already learned it enough to do what they need to do (and don't want to relearn anything, like all of us), but they fact that they have learned a complicated thing is a badge of honor and even (subconscious) job security.
I'm not confident the whitespace or design goals were the issue, rather than any change at all -- I'm not even confident that _new_ users would have preferred the old design.
Or if there was a really good design out there that would have worked better for most both new and existing users, which a skilled and experienced designer could have come up with after actually observing and talking to users and understanding their work well -- I'm still not confident in any conclusions about how much whitespace it would have had.
- zdragnar 3y agoIf your job relies on using some software for hours a day, you'll quickly learn whatever quirks it has. Making a design change means throwing out the brain equivalent of muscle memory for every one of your expert users. If you don't have a very, very good reason to do so, you're basically dropping them off in the wilderness and expecting they'll find their way back home on their own, with no familiar landmarks to guide their way.