3 ms·
> Users absolutely hated the new system. Sure, the old system was ugly, but it had everything they needed, right at their fingertips! I'm not sure this is abou
by jrochkind1 8y ago
> Users absolutely hated the new system. Sure, the old system was ugly, but it had everything they needed, right at their fingertips!
I'm not sure this is about whitespace or information density.
I think that users, especially users using something as part of their job on a regular basis ("enterprise"), hate change. Any change. If they know how to use the thing as part of their job now, it is very difficult to make a significant change that they won't (at least initially) say they hate and want the old thing back. Even if the change would have been liked better by more new users/customers. Even if they hated the old thing too!
And aside from just change-aversion, of course, there may have been lots of knowledge/decisions about what users actually needed to do to do their jobs "encoded" in the old UX, as a result of lots of changes over time, that can be lost when creating a brand-new-from-scratch UX -- especially if you aren't doing a lot of (or any? it wasn't mentioned in the post) UX research in advance of the re-design.
I think this story may be about change, without necessarily being able to conclude anything about the factors of the change/design, such as whitespace, or any other design elements.
If you're doing UX design, you should be doing UX research. And not assuming any universal principles about whitespace or information density from this blog post.
- hinkley 8y agoYeah I have similar concerns about the lessons learned. Power users rely on muscle memory. Productivity is boosted by familiarity. Unless there is a great deal of turnover on the team, the thing they are familiar with is the thing they have. If you want to change that you have to come at it with respect and empathy. Fields nobody uses anymore? You can take them away but that changes tab order. So you might have to do that piecemeal or one screen at a time to give people time to adjust. UX for pros runs counter to a lot of guidelines for beginners. You’re trying to reduce the amount of attention they have to dedicate so they can go faster or juggle the feelings of the person they’re talking to. They want speed and predictability. Discovery is only for very obscure workflows. Important, yes, but not paramount. I’ve seen this even with developer tools. When someone starts yelling at a dev the conversation goes smoother when the task is straightforward. “Let me just pop in here and look... here’s your problem.”