Institute for Youth Research Malaysia (IYRES)
Project & Survey Managing Back-Office for Researcher, Mini-App for Enumerator
Research, Design, Optimizing
Our team was working on a back-office which is used by several type of users on managing surveys, viewing reports and organizing projects and resources.
The users such as researcher and supervisor will use the back-office system to manage resources for surveys, set up project, track timeline, whereas the enumerator will use the mini-app for survey routine.
Additionally, we also designed a mini-app for the enumerators for survey routine purpose.
Inconvenience for researcher to use several third-party site or software to manage their project data and details with the team.
Lack of useful feature for enumerator when using app other than surveying, they still need to contact supervisor for any other requests.
How can the new back-office and app provides more value to users?
How can we design every function that users needed in the back-office while gathering data collected from the enumerator out there without using any third-party subscription?
To improve the efficiency of the workflow and save cost without using third-party subscription.
The framework and methods used throughout the project.
Due to the limited permission and access, our project manager and team lead had several meetings with the client and gathered the user requirement specification instead of the designers.
Through the meeting, they also interviewed the users about the process flow of their work.
After each meeting, we have internal discussion about it, gathered the information regarding the problems they faced currently and how they react accordingly.
The users feedback the pain points when they setup a survey for a new project including too many unwanted info from the third-party site, hard time to manage and approve the responses collected, difficulties to distribute job to enumerator according to the survey coverage area.
The enumerators were also having a hard time to categorize the survey demography with the app.
Users normally use Lime Survey as their current tool for survey because of its variety of features.
They’re known by their survey structure, template and question group which is considered big help for the researcher to manage their survey.
Specifically, their question managing feature, save template as pre-set, and the flexibility to in-depth customization of questions and answers.
The design and features were catered solely for the users. Aside from researching the part where the users manage the project, we focused on the part where users set up the survey.
Our team researched the Lime Survey platform and adopt the survey structure for the user to be more comfortable and familiar with the tools they normally use.
During the process, we filtered out the unwanted feature and additional info that were available from Lime Survey.
The users of the app are the enumerators, they consist of a wide range of users. The users will use the app for their respondent to complete the survey.
Therefore, we prioritized on the simplicity to operate. We designed a dashboard to navigate towards the survey page, buttons which is easily to tap on, other important information such as current progress and time left were also considered in the design.
Statistics of the responses collected were designed on survey details page because of its huge amount of information.
Our team transform the wireframes of the back-office into HTML CSS prototype as requested by the client.
This kind of prototype is closest to the end product without any working functions that allow users to navigate through. The app prototype is by screen transitions.
We gather the feedback from the users by unmoderated remote usability testing method. During the testing phase, there were a lot of changes and additional requirement being added.
For instance, they needed a function for request and termination by the enumerator via the app, along with some materials to be downloaded by the enumerator in order to carry out their work were also added in a related matter. The production started after the User Acceptance Testing (UAT) has been done.
When a researcher or designer gets limited access to the user/client in a project, we need to be proactive in listing out question and communicate well with the agent in between in order to gather information and clarity about the users and the problem they faced.
Assumptions and research need to be prepared in questions for verification instead of waited to be told what’s the requirement, the latter will cost much more time and workload to the team.
Therefore, make assumptions based on research and find similar user for enquiries, then get everyone in a meeting and verify through the process.
View Next Project ↓
