> There seems to be this notion that if the users don't immediately understand the interface, then it's a bad interface. This might make sense for b2c public

> There seems to be this notion that if the users don't immediately understand the interface, then it's a bad interface. This might make sense for b2c public services, or areas where a high cost of training on continually 'new' users hits the bottom line. It makes far less sense for internal services/apps, and it's something I end up 'fighting' with with clients sometimes. They'll have 'design teams' who justify their "ux of the day" decisions with data from public services. An internal reporting system with 10-12 dedicated users who will use it 3 hrs per day as their main operating function should have more levers/buttons/filters/etc than a marketing website aimed at getting people to buy a specific brand of dog food. But that marketing site looks so 'good' and 'inviting' because... there's only 2 buttons, in particular shades, etc. The reporting interface should be warm and inviting right? With smooth transitions to bring a sense of calm to the users, rather than induce tension, right?