3 ms·

> Power users need the app to be efficient. Can we dispense with this "power user" bs? The reason anyone uses software is efficiency. The end goal is to delive

> Power users need the app to be efficient. Can we dispense with this "power user" bs? The reason anyone uses software is efficiency. The end goal is to deliver value (measured by productivity/$ spent) with a specific toolset you are tasked with building and maintaining. Stratifying your customer base by ephemeral computer literacy ideas will just distract from delivering a product that addresses everyone's needs.

seabird 3y ago
Productivity unit per dollar spent is going to follow making your system most efficient for the people that spend their entire day in it (the power user) and just workable enough for an outsider to do occasional work. Compromising the workflow of your full time SCM expert in your ERP system for the sake of somebody who spends an hour or two a month filling out purchase orders is just stupid.
- darby_eight 3y ago
  > Productivity unit per dollar spent is going to follow making your system most efficient for the people that spend their entire day in it (the power user) and just workable enough for an outsider to do occasional work. Well, why bother making this distinction to begin with? The whole concept of a power user just reeks of lazy product design. > Compromising the workflow of your full time SCM expert in your ERP system for the sake of somebody who spends an hour or two a month filling out purchase orders is just stupid. Yes, this is lazy product design in the other direction. It's not clear why you can't just satisfy both groups.
- AnimalMuppet 3y ago
  But see, there often are more of those "hour or two a month" people. If you have, say, 20 times as many "non power users" as "power users", then "an hour or two a month" times 20 adds up to a significant amount - still less than the "power users", but not negligible. And that's the problem of a lot of enterprise apps. The UI design is one that makes sense and is efficient for power users, but a large number of regular users use the app too, and the UI design absolutely stinks for them.

seabird 3y ago

Productivity unit per dollar spent is going to follow making your system most efficient for the people that spend their entire day in it (the power user) and just workable enough for an outsider to do occasional work. Compromising the workflow of your full time SCM expert in your ERP system for the sake of somebody who spends an hour or two a month filling out purchase orders is just stupid.

darby_eight 3y ago
> Productivity unit per dollar spent is going to follow making your system most efficient for the people that spend their entire day in it (the power user) and just workable enough for an outsider to do occasional work. Well, why bother making this distinction to begin with? The whole concept of a power user just reeks of lazy product design. > Compromising the workflow of your full time SCM expert in your ERP system for the sake of somebody who spends an hour or two a month filling out purchase orders is just stupid. Yes, this is lazy product design in the other direction. It's not clear why you can't just satisfy both groups.
AnimalMuppet 3y ago
But see, there often are more of those "hour or two a month" people. If you have, say, 20 times as many "non power users" as "power users", then "an hour or two a month" times 20 adds up to a significant amount - still less than the "power users", but not negligible. And that's the problem of a lot of enterprise apps. The UI design is one that makes sense and is efficient for power users, but a large number of regular users use the app too, and the UI design absolutely stinks for them.