6 ms·

I noticed an interesting dichotomy watching people use software I worked on: - When engineers design software, we design it with the mindset that people like u

by allo37 6y ago

I noticed an interesting dichotomy watching people use software I worked on: - When engineers design software, we design it with the mindset that people like using software and will appreciate all the cool features. - When non-engineers use software, they do it because they need to use it, not because they like it. They have other stuff to do. If anything it's an obstacle to what they need to do, so they interact with it as little as possible to do what they need. So, imo that line about respect for your users was spot-on. Don't get in your user's way more than you have to.

etripe 6y ago
While I am a software engineer, I don't particularly identify with your self-ascribed and generalised engineers' view. Maybe I'm different because I've previously manned help desks. Maybe I'm more neurotic than you are. I always design from a perspective of having experienced a lot of truly horrible software, from websites that require spelunking to find the nugget you came to find to HR time-tracking applications that don't even allow you to define a standard week. While I do assume people like using software and all the cool features, that stance takes a backseat to thinking about how to: * fit flows to what they actually want to achieve * minimise the amount of data entry and clicks * produce meaningful messages (errors, tooltips and descriptive text) * not overwhelm the user with features irrelevant to the current view/flow. I'm by no means particularly knowledgeable in "formal" UX, but I find focusing on usability does make users appreciate your software more. YMMV
- allo37 6y ago
  I think you're interpreting my comment too literally, I'm basically saying the same thing you are; I also try to think of software from the perspective of people who will actually be using it. All I'm saying is that I've noticed that often engineers and product-owners ( or whatever we call a boss nowadays) are out-of-touch with what their end users actually want and need.
  - etripe 6y ago
    > I think you're interpreting my comment too literally That's been known to happen :)

by allo37 6y ago

etripe 6y ago

While I am a software engineer, I don't particularly identify with your self-ascribed and generalised engineers' view. Maybe I'm different because I've previously manned help desks. Maybe I'm more neurotic than you are. I always design from a perspective of having experienced a lot of truly horrible software, from websites that require spelunking to find the nugget you came to find to HR time-tracking applications that don't even allow you to define a standard week. While I do assume people like using software and all the cool features, that stance takes a backseat to thinking about how to: * fit flows to what they actually want to achieve * minimise the amount of data entry and clicks * produce meaningful messages (errors, tooltips and descriptive text) * not overwhelm the user with features irrelevant to the current view/flow. I'm by no means particularly knowledgeable in "formal" UX, but I find focusing on usability does make users appreciate your software more. YMMV

allo37 6y ago
I think you're interpreting my comment too literally, I'm basically saying the same thing you are; I also try to think of software from the perspective of people who will actually be using it. All I'm saying is that I've noticed that often engineers and product-owners ( or whatever we call a boss nowadays) are out-of-touch with what their end users actually want and need.
- etripe 6y ago
  > I think you're interpreting my comment too literally That's been known to happen :)