BRAND
Teno
PROJECT
PRINCIPAL DASHBOARD
AIM
Designed and developed a dashboard for school principals where they can see and monitor all the school-related data and activities in one place.
RESPONSIBILITIES
User Research
Wire-Frame
Visual Design
Prototyping
THE MAIN OBJECTIVE OF THE PRINCIPAL DASHBOARD
In the Teno application, there are 4 specified roles which are Admin, Teacher, Parent, and Student. The Principal is the person who has numerous responsibilities toward school management and he or she has to be aware of every activity that takes place in the school on day to day basis. So, that is what the Teno application's new feature helps us with, which is called the principal dashboard.
RESEARCH
Starting with the basics, who, what, and why?
We started with strategy and identified the primary and secondary target audience. Since we were talking about a new role (Principal), we started from scratch. So, for the research, we interviewed our target audiences and drew insight into the initial states. So, based on those interviews, we created an empathy map that will help us to guide and create a new role.
FEATURE IDEATION
After conducting multiple interviews, we came up with various features for the Principal
Dashboard.
USER PERSONA
After conducting user interviews and creating empathy mapping, we developed Rajesh Manohar’s persona (based on one flow).
Rajesh Manohar has been the principal for the past 4 years, he is fully occupied with school management-related work and can not give proper time to check daily school attendance. So, he wants an application where he can see all the school attendance in one place at his convenience.
STORYBOARD
Yes, everything starts with a story!
While diving deep into the user personas, we figured out the multiple scenarios, which helped us to create a user flow. This exercise helped us to identify what type of information will be required for the principal.
The principal wants to check
Class 7A attendance.
The principal wants to check
Class 7A attendance.
The principal wants to check
Class 7A attendance.
He opens the Teno app
He opens the Teno app
He opens the Teno app
Went to the attendance section
Went to the attendance section
Went to the attendance section
Select Class 7A
Attendance overview of all
students.
Rajesh wants to see class 7a student attendance.
TASK FLOW
Performing the task analysis allowed us to easily walk through the flow to identify the key screens necessary to understand how the principal will check the student's attendance.
Some key things we strived to understand are:
-
How they are going to see the average attendance of the school?
-
How they are going to see class-by-class attendance?
-
How they are going to see particular classes’ day-by-day attendance?
Understanding these things is vital for the creation of the site and helped us to create a wireframe.
SKETCHES
After doing user research, persona creation, storyboarding, and task flow, we landed to
create a low fidelity wire frame.
We wanted to keep it very loose and flowing and not get distracted by a lot of details. This exercise allowed us to start thinking about where the content would fall on the page. Here, you see the dashboard page and attendance flow layout. Using sketches allowed for quick iteration and the generation of ideas very quickly.
HIGH FIDELITY WIREFRAME
After reviewing the sketches with the product team and a couple of iterations, it's time to
start refining in the form of a high-fidelity wireframe. Here, We further identified the layout of the interface. Utilizing wireframes in the beginning phases of design is an efficient way to determine the placement of elements without getting too much bogged down in minute details. A huge benefit and timesaver are that the layout can easily be changed.
HIGH FIDELITY PROTOTYPE
The high-fidelity prototype is created in the preparation for usability testing. In this step, we defined what we wanted to test and why. It was our main task flow to check class 7A attendance. We developed a test plan and created a prototype using the marvel app.
USABILITY TESTING
PARTICIPANTS
Total 5 test subjects
OBJECTIVE
-
To determine the ease at which users can navigate through the application to accomplish their task, which will be checking class 7A attendance.
-
To observe how users searched particular class attendance.
-
To observe the user can easily understand it in graphical format.
-
To test the overall ease of use of navigating the application.
-
To observe any frustrations or obstacles users may have that may impede their ability to complete their tasks.
OBSERVATIONS
-
Users had very little trouble completing the task asked of them.
-
They had difficulty reading some text.
-
Minor concerns in the color pallet.
