Understanding Project Scope
Reconstruction of registration process to create user efficiency and reduce user error.
The directions for the registration process were written and shared in a google doc. Faculty were expected to find
-
due dates
-
forms
-
detailed instructions of data entry into Veracross
-
how to advise students
-
filling out the registration form
It was quickly recognized the current system of scrolling through the document took too long to find key information and as a result, the following areas became problematic for the registrar and faculty:
-
due dates were missed
-
abundance of emails asking questions
-
frequent one on one meetings to go over data entry concerns
-
resources in many different places
-
handwritten forms that were difficult to read
-
forms that were missing areas that were critical to completing the registration process
-
acquiring teacher approvals by hand
-
data entry was not automated
Control Group Criteria
Careful selection of control groups to assist with success and completion rates.
CONTROL GROUP
5 new faculty members and 13 new students were given Registration Instructions and the Registration Sheet and asked to perform the task on their own.
CONTROL GROUP TASKS
Each person was asked to record
-
how long it took them to complete reading the instructions.
-
immediately record questions after reading.
-
re-call specific dates.
RECORD PROCESS
Next, each control group was asked to perform the registration process.
Areas carefully watched
-
annoyance
-
repetition
-
organization of tasks
-
how often forget instructions
-
difficulty in finding information/classes
-
approval process
-
feeling of success level upon completion
-
if user checked for accuracy, how many mistakes were made
User Interview and Insights
Specifying the criteria that defines our ideal participants.
PRE-SCREENING QUESTIONS
POST TEST QUESTIONS
-
How difficult are the tasks? Scale
-
How would you describe your overall experience with this process?
-
If you could change one thing in this process, what would it be and why?
-
What do you expect to see in the process in the future?
-
What features do you find most valuable and why?
-
Can you give a few examples of real situations when you would need to read a document and retain 90% of the information you read?
-
What do you think about the design?
-
What prevented you from completing a task easily?
-
I noticed you kept going back over the document. Why?
TESTING AREAS
User and Usability Testing Areas
-
annoyance
-
repetition
-
organization of tasks
-
how often forget instructions
-
difficulty in finding information/classes
-
approval process
-
feeling of success level upon completion
-
if user checked for accuracy, how many mistakes were made
-
How much time do you spend online?
-
What apps and websites do you use on a regular basis?
-
How often do you read long documents all the way through?
-
Which device do you typically use to check something or look something up?
-
Have you registered with MICDS before?
-
Have you registered anywhere before?
-
If so, what was your experience like?
Prototypes
The growth of our idea.
VERSION 1
The initial design used the software Adobe InDesign to transition the user from a piece of paper to an online version.
WEBSITE
The software Adobe InDesign became an issue for the person responsible for updating information.
Therefore; Google Sites was agreed upon based on level of skill needed and ease of sharing permissions with others.
REGISTRATION FORM
The first version of the form remained the same, but was formatted in Excel.
The second version of the form more research was conducted and the second version was created based on user feedback.
Designing for Users
Satisfying users based on research and hard work.
MICDS BRANDING
-
Our design needed to be on brand.
-
I used the same fonts, color palettes, icons, and shapes.
-
When there was a new design without any reference, I created designs that align with MICDS design style as much as possible.
