In software development, it is best to know that you should avoid the mantra of "if you built it, they will come" especially in relation to software projects. Some people think it will work and let them shell out less effort in their tasks. However, it will only achieve the opposite! If you continue to think like this, then your company will flop since you are not able to deliver the needs of your clients. This mistake can be remedied of you get to know the users of your software program. When you do so, then it is easier to come up with an accurate program which your clients can use.

Basically, it is important to know the following things about your users: what they expect their software to fulfill for them, what kind of input they expect, the kind of output which they want to turn out, what it is that they can do with such an output, how interactive the user can get with the program and how such a program will be able to fit into the real world. It is also important to understand some problems which might be linked with your users. Usually, you might get three out of ten users that will just be a waste of both time and effort. They have no real insight about their world and they do not care to explain their thoughts to you. Second, around four users in ten will provide you with good information, but might have another take with regards to some issues.

You should listen to them as they will provide you with the basic features that ought to be part of your program. And finally, the last three members of the user group are the best because they will provide you with great ideas on how to make the program truly relevant to users' needs. If you listen to them and distribute a program which all ten users can use, then you cover seventy percent of your user base who initially did not see the potential for greatness in your program.

As a word of caution, it is important to take note of some rants given by some of your users. Think of it as a great opportunity to provide a solution which is very important to them. It does not even help thinking that people who use the program cannot provide significant input about it, because through their own work experiences they can paint a picture of the ins and outs of their work that can be remedied by tweaking your program.

Another mistake in connection to this is not talking to users because you do not have time. This is very important because if you cannot find the time to speak with your users, then how will you know about any problems that came out in your program which you did not foresee? To save time, effort, money and grief, it is important to speak to your users thoroughly the first time and then to follow it up post program launch.

Print

Location: BlogsOSD Blog