subject: How To Develop Easy To Use Business Software [print this page] When developing software, there are two critical criteria to bear in mind. The first criterion is that the software should be appropriately priced for its intended audience. Pricing software too high for the market will turn potential buyers off. Vice-versa, pricing software too low can cause customers to devalue your software, assuming it is of low quality. The second criterion to bear in mind when developing software is to make the software easy to use. Given the choice between two business software packages of similar price, studies have shown that most potential customers will choose the software package that is easiest to use.
Always aim for ease of use when developing any business software package. Do not worry that any package that appears easy to use will automatically be dimissed as simple and of lower software capability. Remember that it is only by trying out your software that a user will really find out if the feature set is appropriate for their business needs. The more approachable a piece of software is, and the easier it is for a user to discover the package features, the more satisfied the customer is likely to be and the more likely it is that you will gain a sale.
One of the main problems in designing easy to use software is that it is far more difficult to do than designing without ease of use in mind. Many software packages appear like reference manuals - every possible feature is crammed into the package with no thought given to simplifying workflow for the user. The user can do everything they would like to do, but little to no help is given in aiding the user to access the most commnly used features.
To design easy to use business software and to ensure that your design is truly ergonimic and easy to use, you will have to conduct user tests. The important part of any user test designed to measure ease of use is that you observe the users running your package and performing the key workflows. Do not lead the user or try to aid them through difficulties they may encounter. Let the user make mistakes and observe how they use the software to approach a solution. It is important not to pressure the user in any way, make it clear that they can make mistakes and that it is the software that is being tested not the user. If a user struggles to complete a test, do not take it personally - the users feedback and your observations of how the user navigated the package will reap benefits if you carefully analyse the user actions and construct alternative software solutions.
