Employee research, multiformulary or single form?

Asked

Viewed 53 times

0

I am developing an app that should be made available to employees of a particular company, so that co-workers themselves make the evaluation of one (two, three, etc.) working friends by answering questions (several of them, quantity also configured by the Rh sector) registered by the Rh sector.

I was left with the following doubt, I do everything in a single form and use javascript to go showing one question at a time, or I do several form, one for each question?

The employee should be able to partially stop the process and pick up where he left off.

  • Just a comment totally disconnected from the technical content of the question: in my humble opinion, request this type of 360 employee evaluation without any context (and sometimes anonymously), is a bad practice. It’s not productive and it’s unreliable. Anyway, it’s just institutionalized gossip.

  • @Luizvieira, you are absolutely right, but it will not be without technical content and it will not be anonymous, the evaluated will not know who evaluated it, but the Rh department will know exactly who answered, thus giving an evaluation of the evaluator.

1 answer

2


I was left with the following doubt, I do everything in a single form and use javascript to go showing one question at a time, or do several form, one for each question?

In principle it should be very bad for usability to have multiple forms. It will be exhausting (and unnecessarily useless) from the point of view of the user, having to click "Send" to-each-maledeta-question. It only makes sense to separate in different forms questions that are about different subjects. If it’s all about the same subject, just use one form. However, it makes a little more sense to separate different questionnaires for each other employee being evaluated.

Showing a question at a time is not necessarily a problem, if you use another way to provide progress feedback. The user needs to know how many questions he has answered and how many more to answer. The most direct and clear way to do this is simply to ask him all the questions at once.

If the form has many questions, you can use scroll bars or pagination bars. It does not change the fact that it will be perceived as a single form. Finally, I want to say that the organization and the implementation are different things.

The official should be able to partially process and resume where you left off.

This is really important, especially if there are many questions to be answered. But this is another question of implementation. Suppose, for example, that you have a single form presented with scroll bars. Nothing prevents you from saving what has already been typed to re-present if the user closes and comes back later. Now, note that regardless of the choice to use one or more forms, the user need to have feedback of what has already been filled.

If your implementation has many questions, you should already position the questionnaire in the first unanswered question when the user accesses again; and, mainly, you need to include some clear indication of where the remaining questions are. You can use color, you can use a "Gutter" (type the side map that some text editors use to represent the code overview), may even have the option to filter only unanswered questions. The important thing is to provide this facility to the user.

I know it’s pretty generic tips, but that’s what you can ask for an equally abstract question. If you have a more concrete example, then you can do a more detailed analysis.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.