3 ms·
I had to share this with my team today. We produce an app for banking that is used at the front line (i.e. in the branches). We have explicitly acknowledged the
by bob1029 6y ago
I had to share this with my team today. We produce an app for banking that is used at the front line (i.e. in the branches). We have explicitly acknowledged the fact that the bulk of our users are going to be new to the business & are going to be paid peanuts while simultaneously being expected to produce consistent business outcomes. As a result, we have tailored our interfaces for self-discoverability and intuitiveness. Making a UI intuitive is a book all by itself, but suffice to say that we spend a lot of time agonizing over how UI elements are laid out so that users are less likely to make errors in judgement.
Our application is not immune to exposing exceptions to the business. But, we have added measures throughout to minimize this as much as possible. In areas where there is a lot of jargon which might confuse new employees, we put help buttons which allow a user to quickly review important terms & other documentation in-line with the actual functionality. This makes our application almost a training course in and of itself.
Additionally, in cases where we identify that poor choices could have broader impacts to other parts of the business (i.e. lighting 500mm on fire), we add explicit validations with hard cutoff limits to prevent insane things from happening. In this specific case, we would probably walk the user through a decision tree to force them down a valid path and ensure the funds were being tagged to the correct account(s). We also have approval loops in our application for more sensitive operations, but even these have integral validations & other measures to ensure that "experienced" employees don't screw up either.
- CobrastanJorji 6y agoThis is a great lesson. However, I'm afraid for you're designing your product to be good for the people who are being paid peanuts and are new to the business, but those are not the people who are buying your software. They're just the users of the software. Oracle put basically no thought into their UI but put a lot of money into promotional videos and sales, and they sold their software to giant international banks because the people buying the software experience it only through videos and salespeople. I'm terribly afraid that you're going to be punished for focusing on the right things.
- bob1029 6y agoThe entire point of our software is to be intuitive enough so our clients can hire cheap labor. Its a first class feature. Why would we be punished for this?
- CobrastanJorji 6y agoBecause every product promises that it's intuitive and nobody ever bothers to check in with the poor cheap labor told to use it.