New Software Application Versus What Users Want

Software Application Debate

Computer users may not be interested in how software actually work, but they certainly want to be able to get the hang of things easily and without much trouble. When Microsoft or any other firm for that matter comes up with a new software application, initially there is apprehension as people are afraid of the unknown. While they are keen to see how the new software benefits them, they are also scared of what they might encounter and many feel more comfortable with the old version. But software developers know how the new software application offers increased functionality and thus are keen to help people accept the new software quickly. It is important to understand that oftentimes software may not offer exactly what the customer desires because there software developers are more concerned about functionality than they are about people's wishes and expectations.

For example with every new version of MS operating system, people are expecting some features which might be missing when the OS comes out. What people fail to understand is that software involves complicated coding and it is more important to make them work properly and offer as many conveniences as possible. For this reason, it is not possible to meet the demands and expectations of users. The best thing thus is to find a middle ground where both the users and developers can agree. This middle ground is the place where developers can actually see users being more accepting of the new software. In short, despite all the apprehensions, what users really want is to be able to understand the new software. They don't want the developers to hand them something that appears complicated or does something without them knowing about it.

For this reason, the three important rules of software design are transparency, defaults, and configurability. The more these rules are followed, the easier you make it for the users to accept the new application. Transparency refers to clarity of actions. What is the software meant to do? Make sure it does just that and nothing else. This is exactly what users want. They don't want the software to be keeping information from them or taking actions that the user is not aware of. For example if the software keeps user data on a file or make it easier for third parties to access customer information, then it is user's right to know about it. This is the transparency factor. While enhanced functionality is what everyone would want and developers would seek the most, still it only pays to follow these rules of design in order to help users readily accept the new software.

The second important rule is to leave default setting to the user. Developers complain that users are wary of new software application and do not understand functionality issues but the truth is that most people only want to be able to understand the software and they do not welcome exploitation in any form. Now this is an interesting concept. When MS keeps all default settings to itself, it becomes difficult for the user to later change them. For example whenever you click on an email address on a website, Outlook Express pops up. It may not be needed. Developers should therefore offer users the options to set their own defaults.