Hi,
You don't say how large your survey population is, but our company uses a CHEAP and easy to use tool called Survey Monkey (see
I was amazed at the functionality we get for the price; we used to spend a lot of staff time administering and compiling the results of surveys; no more.
My advice on the questions...
*Always provide a 'not applicable' choice so that employees who don't do the function (or use the app) you are asking about have some way to convey that. In many companies I've worked in, the fact that a user had never attempted to get into an application came as news to management.
*Allow the employee to make suggestions for improvement: feeling listened to goes a long way for user relations, and often you'll be surprised how much they may want things that are inexpensive to provide.
*Don't forget to ask questions about the business process that the application supports. Often issues expressed about an application are really problems with the business process the application's use is imbedded in, or visa versa. If the user has no other way to give feedback about the rest of the process, they may use the application survey to convey those gripes, rather than not express them at all.
* Divide questions about an application into categories by probable cause up front. This helps in analyzing root causes on the back end. Some suggested categories...
ACCESS: -hours of availability, -passwords/ids, -equipment functioning
SUPPORT: - help line availability and help desk staff competency, -written/online doc
GUI: -easy of understanding without using doc, -does the application 'make sense', -what is missing?
FUNCTIONALITY: -reponse time, -bugs/error messages, -does it meet the users' needs, or must they 'work around' the system?
Off to the train,
chicagoAnalyst