4 ms·

What should really happen is putting these "designers" into the helpdesk seat. Or at the very least have them observe how people use their designs and they are

What should really happen is putting these "designers" into the helpdesk seat. Or at the very least have them observe how people use their designs and they are not allowed to interfere. It will be a painful lesson for them. But as long as these things don't happen, we will be stuck with this major suckage that is modern UI.

kalleboo 4y ago
I miss the old days when Apple and Microsoft had teams of people user testing every new feature instead of just following the whims of their designers
- speed_spread 4y ago
  I remember the time when we would pay for software and expected quality in return. Nowadays it's either free (sponsored by ads and or surveillance) or bundled with hardware to be abandoned when the manufacturer wants money again.
riedel 4y ago
I wonder if you could actually rather quantify date related errors by analytics. I actually booked the wrong return flight once because the date picking logic was too intelligent for me. There should be many signals pointing to this.
andrepd 4y ago
> What should really happen is putting these "designers" into the helpdesk seat. Or at the very least have them observe how people use their designs and they are not allowed to interfere. The fact that this isn't natural standard practice speaks volumes to the current state of """UI design""".
mannykannot 4y ago
My personal experience is that a significant number would simply blame the users.
- bell-cot 4y ago
  Gut reaction: Designers blaming a serious percentage of users are obviously working for a company with users who are a poor match for their skills. Management should "encourage" them to move on, to other companies, whose users would let them really shine.
- Zuiii 4y ago
  I call this the gnome affect.
  - Forbo 4y ago
    Can't seem to find this when I search, care to elaborate?
sidlls 4y ago
At a certain point companies employ "experimentation" (mainly A/B tests) to do exactly this. They measure dropoff and other things, and have targets, e.g., "acceptable dropoff" or whatever they might term it internally. That small amount of user loss (fraction of a percent to a few percent depending on feature/daily usage/other metric) due to a design is considered acceptable: not that they don't care, it's just not considered impactful enough to the business to matter.
friend_and_foe 4y ago
Any user who designs something like this that doesn't realize the number of mouse clicks needed to navigate this interface doesn't need to be a designer. Helpdesk experience won't save them, they're either bottom of the barrel incompetent or outright malicious. I could understand if it were something more complicated, but there's no excuse for this stuff with date pickers.
neycoda 4y ago
This is called dogfooding, and developers have to do it all the time to make sure functionality works before deploy. I feel like designers do this minimally, or can get away with more functionality breakage or poor UX because they can make things look slick.

kalleboo 4y ago

I miss the old days when Apple and Microsoft had teams of people user testing every new feature instead of just following the whims of their designers

speed_spread 4y ago
I remember the time when we would pay for software and expected quality in return. Nowadays it's either free (sponsored by ads and or surveillance) or bundled with hardware to be abandoned when the manufacturer wants money again.

riedel 4y ago

I wonder if you could actually rather quantify date related errors by analytics. I actually booked the wrong return flight once because the date picking logic was too intelligent for me. There should be many signals pointing to this.

andrepd 4y ago

> What should really happen is putting these "designers" into the helpdesk seat. Or at the very least have them observe how people use their designs and they are not allowed to interfere. The fact that this isn't natural standard practice speaks volumes to the current state of """UI design""".

mannykannot 4y ago

My personal experience is that a significant number would simply blame the users.

bell-cot 4y ago
Gut reaction: Designers blaming a serious percentage of users are obviously working for a company with users who are a poor match for their skills. Management should "encourage" them to move on, to other companies, whose users would let them really shine.
Zuiii 4y ago
I call this the gnome affect.
- Forbo 4y ago
  Can't seem to find this when I search, care to elaborate?

sidlls 4y ago

At a certain point companies employ "experimentation" (mainly A/B tests) to do exactly this. They measure dropoff and other things, and have targets, e.g., "acceptable dropoff" or whatever they might term it internally. That small amount of user loss (fraction of a percent to a few percent depending on feature/daily usage/other metric) due to a design is considered acceptable: not that they don't care, it's just not considered impactful enough to the business to matter.

friend_and_foe 4y ago

Any user who designs something like this that doesn't realize the number of mouse clicks needed to navigate this interface doesn't need to be a designer. Helpdesk experience won't save them, they're either bottom of the barrel incompetent or outright malicious. I could understand if it were something more complicated, but there's no excuse for this stuff with date pickers.

neycoda 4y ago

This is called dogfooding, and developers have to do it all the time to make sure functionality works before deploy. I feel like designers do this minimally, or can get away with more functionality breakage or poor UX because they can make things look slick.