5 ms·
White space killed an enterprise app (2019)
- voidz 3y agoGood article, but visually representing data differently from how it's stored in the database can be a huge PITA. A pet peeve of mine is real names as an example, Dutch family names may have an infix (van, van der, den, van den) which is always in lowercase, and usually is not even an option on non-Dutch websites. You can't leave how to display these things up to the designer: the user has to know (imho) how these are stored. For example, sorting on last name should not happen on the infix, but only by lastname. E.g., "Dijk, van" comes before "Meulen, van der". For completeness sake, the full names here may be "Bert van Dijk" and "Anne Jan van der Meulen". Also, "Anne Jan" is a single first name, despite the space.
- marcinzm 3y agoExactly. Especially in something like customer service where they're often helping fix and issue. If they don't know the name is incorrect then they will have a lot harder time figuring out why a downstream system is sending the wrong mail to the customer. In their example, the change is also much harder to read for me. It takes up just as much space but logical categorical groupings are no longer visible at a glance. Previously you could see all the people from the same zip code, city or state. Now you can't because they're all mixed together at different horizontal offsets. You could also pull out the different information at a glance by using the horizontal offset which you now can't.
- ChrisMarshallNY 3y agoEast Asian names (Korean, Chinese, Japanese, etc.) can have a great deal of variation in surname/given name positioning. In my app, I don't even try to separate them. I just give a single string that can handle UTF-8, and let the user do what they want. However, I also don't need that data for tagging, sorting or anything else, so it's easy for me to say.
- loloquwowndueo 3y agoI’ve been in this boat and then had to justify the choice when integrating with third party vendors whose backends absolutely want names split into first/last components. We would set up integrations sending the full name in the “first name field” and then a hard coded “notmylastname” string in the “last name field”. And then have about 3 days of back and forth usually including a link to https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... and explaining that no, you can’t reliably use a regular expression to split the full name data into first/last components.
- Mordisquitos 3y agoThat reminds me of my own pet peeve regarding anglocentric UI assumptions. Spanish naming customs are 'Given_name First_surname Second_surname' [0], such as for example Spanish director Pedro Almodóvar Caballero, whose name would be shortened for convenience by dropping the second surname — Pedro Almodóvar. The problem is too many US/Aus/UK developed UIs assume the whole world follows English naming customs, and thus would insist on showing his initials as 'PC' or shortening his full name as 'Pedro A. Caballero'. For reference, that feels as wrong as it would be to an American for a website (assuming Spanish customs) to initialise the director of E.T. and Jurassic Park as 'SA' or display his full name as 'Steven Allan'. [0] Spanish given names may often be two-words-long (e.g. 'José Manuel') and a surname may less frequently be more than one word (e.g. 'de la Fuente'), but this isn't a necessary detail for my base rant above.
- erikw 3y agoAnd the inverse is also somewhat common- forms which require both a maternal and paternal surname, and won’t let you continue with just a single surname.
- loloquwowndueo 3y agoThat’s not even a totally UI concern. See https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
- narag 3y agoIn José Manuel, Manuel would be the middle name, just like in English. It's not a "two-words-long first name". Sometimes first and middle names are coupled like a whole, like it's usual for José Manuel. Also for José-something or Juan-something in general. Other times, the middle name is never used, like in Nicolás Antonio, being the Antonio part extra annoying, because the SS personnel, for some reason, insists in calling me that when it's my turn.
- javcasas 3y agoMy wife's sister decided to name their two newborns with three names, on top of the usual two surnames. I wish luck to those two little guys, as their names will be misrepresented pretty much in every system in the world.
- _xivi 3y agoPrevious discussion: Whitespace killed an enterprise app - https://news.ycombinator.com/item?id=19153616 https://news.ycombinator.com/item?id=19153616 - Feb 2019 (435 comments)
- nkrisc 3y agoIt’s early for me, but I missed the part where the UX designer actually talks to the people who use the app. That’s what killed it, not white space.
- PaulHoule 3y agoSomebody drunk on white space will “listen” but not hear.
- Lalabadie 3y agoAs a long-time designer, this is one of my main beefs with the rise of UX Design as term for design leadership (that's compared to UX positions that include "research" in their role, for example, and are usually great contributors to a project). When you design a digital product, it's a given that the redesign should perform better in real life situations compared to the current version. Sometimes, the current version is a digital product as well, but sometimes it's forms, a pen, and an efficient clerk. These are the benchmarks from which the product should deliver clear improvements. Most quote-unquote UX designers of the last decade, including many authors on uxdesign.cc, have a career arc that's an ignorant rediscovery of an existing discipline (interface/product design), which they keep not learning because they must appear above the existing skills and workers to keep the illusion going in the face of their managers and LinkedIn audience. (If you think I'm equating lots of UX designers to middle-managers who sometimes ship a wireframe, you're reading me right!)
- nkrisc 3y agoWith 12 years experience as a UX designer, I’ve found that the best UX designers I’ve worked with usually had backgrounds and careers from a non-UX field before UX. Often academic backgrounds, such as anthropology, for example, and had at least some graduate degree. They understood actual primary research and applied it to their design process, and the results spoke for themselves. Once UX became something you could enter from undergraduate studies (guilty as charged), or no degree at all, you end up with a lot of UX designers who lack those skills. And unless you are lucky enough to work with people who have those skills (as I was) or are a particularly motivated autodidact, you end up with articles like this.
- negative_zero 3y agoTIL frustratingly hiding basic information within a menu, within a menu, within a menu, within a menu that's within a menu is called "progressive disclosure" (top marks for that amazing euphemism). I really wish it were possible to calculate the total destruction of human productivity caused by whitespace and "progressive disclosure".
- User23 3y agoYes, the optic system, including the speed of the optic nerve and the eyes ability to saccade, among other things, has a functionally unlimited ability to keep the brain aware of activity in the visual field (modulo optical illusions). The short term memory on the other hand is extremely limited. As always, design should be based on fundamental principles of human biology.
- nraynaud 3y agoIt's also a way for newcommers to discover what an app can do, people know that opening menus has absolutely no risk, while clicking a button might open a modal or actually do something. So generally you want 3 levels: menus, buttons in the UI, and shortcuts.
- jwells89 3y agoYes, I liken a proper menubar to the index of a book. You should be able to find just about every function a program has in its menus. It also serves as a key shortcut cheat sheet which is important for cultivating a fervent base of power users for your app. Maintaining a knowledge base article of shortcuts is probably good enough for existing power users, but it won’t grow that group nearly as well as menus can.
- jwells89 3y agoProgressive disclosure is an important principle in designing good UIs, but as you’re pointing out it’s often misused or used to excuse cuts and burying things for the sake of aesthetics. When applied correctly, all the term really means is thoughtful, research based surfacing of features, taking into account target audiences and the way features relate to each other. It’s why you don’t just dump all your features into the main window of your program, turning it into a Great Wall of Buttons. Thoughtfulness is increasingly uncommon though, UI design has more and more been treated as generic visual design instead.
- jrochkind1 3y agoBased 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.
- cess11 3y agoRight, yeah, systems people use eight hours a day are quite different from 'e-commerce solutions' and 'corporate blogs' and have very different UX-demands. When you're in front of an application that much layout is more or less unimportant as long as it can easily be interpreted by someone who has been sitting there for a year or more. This typically means that a newcomer will feel an immediate discomfort at layout and program flows, there's just too much and much of it is impossible to interpret without initial assistance. This also means that when you change something it has to be run by pretty much every user first, or the one percent users that is actually really annoyed will pull in the rest and everyone will hate your revamp of their workplace. Typically you can add to the interface though, and that's how long-lived 'enterprise' software gets cluttered views that are incomprehensible to newcomers. If you enter this segment of development you need to understand that the users are like Unix greybeards, it's just that their version of urxvt and zsh and vim is a graphical interface to business processes. They'll get mad when things aren't like they've been for decades, and they'll try to have you guillotined if you force 'whitespace' and 'just enough information per view for the purpose I, master developer, think it should have'.
- anilakar 3y agoMy pet peeve is UX designers who design GUIs on large color-corrected desktop displays with no light reflecting on the screen, often with hairline fonts. Then the application will be run on an embedded PC with a small low-contrast touchscreen at an awkward angle and sunlight behind the user's back.
- jwells89 3y agoConversely, I find it frustrating when UI designs targeting some of the most capable displays that have ever existed make little use of the incredible color, contrast, and sharpness offered by those displays, sticking strictly to vague monochrome glyphs and the occasional hint of color.
- RedShift1 3y agoThe low amount of color thing is a design fad, not because it's being designed for the "lowest common denominator" or something.
- jwells89 3y agoA big contributor to the popularity of flat design is how non-designers could make reasonably ok looking stuff with it, whereas more graphically rich style unavoidably requires the work of a skilled graphics artist (which a few developers happen to also be, but the number of people who are good at both is small).
- anilakar 3y agoThat's an issue with Material Design 3 though. Blame Google.
- RedShift1 3y agoYeah especially noticeable with fonts nowadays. I'm sure they look great on their high DPI monitor with perfect colors, not so much on a generic normal DPI display.
- chasing 3y agoThis anecdote is not about white space. It sounds like some junior designer was allowed to go nuts and do whatever they wanted with zero regard for the actual users. The designer just found a bunch of stuff they liked online and just did whatever. The first thing their manager should’ve done upon seeing this work is correct them about the nature of their job: Designers must first understand problems and then solve problems. It’s a creative field, but at the end of the day designers produce business outcomes. Having sexy portfolio pieces and creative work that truly expresses the inner experience of the artist is great — but it has to take a back seat to what the designer is being paid to do. Maybe “being oblivious to the needs of paying customers killed an enterprise app” is a better title.
- Andrex 3y agoIt's hard to do design right the same way it's hard to do kanban right or Jira right. Less skilled people chase the trends without understanding the fundamentals.
- keybored 3y ago> I don’t know who this was but it sounds like a junior developer Why has HN in the last three years or so gotten this collective irresistible urge to insert “junior developer” into every conceivable ill and malaise? The thesis sounds straightforward. Power users need the app to be efficient. Naive outsiders fret too much over æsthetics and the potential usability for newbies. In turn change does not work out for the better.
- thrawa8387336 3y agoAI insecurity
- chasing 3y agoBecause not talking to users and then implementing a drastic change they don’t like sounds like a rookie move? Although, as I kind of allude to, I also place a lot of blame on management: Employees will make mistakes. Big ones. That’s life. A company needs to be structured so there are checks before those mistakes go out into the wild. But, yes: Senior designers can also make mistakes. I’d argue they make less glaringly obvious mistakes, but humans will human.
- YourCupOTea 3y agoWork in the options market making space if you really want to experience users who need immense amounts of dense data available across half a dozen 32 inch screens. The amount of effort that goes into saving the tiniest amount of screen real estate is amazing. Also, *everything* must be customizable.
- IggleSniggle 3y agoArrgggh. The story is about how the data took too much to uncover with the redesign. Then the very first recommendation is "first, reduce data volume." No! No! No! And stop reducing data density, too! Just because something has a higher learning curve doesn't make it bad. Dense data lets a skilled user understand more in a glance. Data density is GOOD if you are building something that is meant to be used more than an hour every single day. Now, if you are building a consumer app where nobody wants to do the chore and you're making it easier, THEN data density is bad.
- IggleSniggle 3y agoAnd if you must make it less data dense because you're selling to a dense-headed exec and not the actual user (the usual with enterprise software), then just provide an easy to access user-preference toggle (and let the preference be saved). You can demo the "sleek" interface to the exec and the user can actually get their job done efficiently. You'll make the initial sale AND the resale when it comes time to renew.
- javcasas 3y agoThe exec dictates what is bought and renewed. You don't really need the useful UI to get it sold and re-sold.
- IggleSniggle 3y agoYou need to in order to get it re-sold if the exec listens to their people at all, even if they buy into the sales pitch for the initial sale.
- javcasas 3y ago> if the exec listens to their people at all And that's the problem. The other week we had a "technology decision meeting" where we were going to decide on one of many technologies after evaluating them. The exec came into the meeting with the decision pre-made, then asked for our opinion. When I voiced my opinion on the sub-optimality of his choice, he agreed with me citing his bad experience with the vendor, he said "we hear you", and didn't alter at all the decision. So yeah, lucky you that your execs listen. My exec just "hears".
- Scubabear68 3y ago“Information density” of screens is highly important in many professional domains like financial trading platforms, pricing screens, etc. For inputs as well, as command line lovers and Bloomberg terminal users can attest.
- leduyquang753 3y agoSo there weren't any usability tests carried out in the development process??? This should be also a planning/management failure.
- pocketsand 3y agoWhat was enlightening for me was watching my wife, who is a physician, work in electronic medical record software like EPIC. It's ugly, it's dense, the colors are high contrast. It also fits everything they need to see in one place and makes it easy to make changes. I do not think there would be a way to make it look "modern" without making it harder to use.
- pavel_lishin 3y agoI don't think I like the grouping example; yes, it looks better when you show a single row from each one, but when I'm looking at 50 rows, it becomes much easier to spot any outliers (like one San Francisco among 49 Los Angeleses, or a Carolina hidden among Californias).