IITB has a huge spread intranet service approximately used by 1900 employees and 8000 students. More than 100 active web spaces used on a daily basis by these users. The dashboard I designed provides an actionable interface, which makes it easier for the user to perform any task. This project is an attempt to get all the necessary academic and everyday information floating on the intranet, which is made relevant to every student on a unified dashboard.
The final concept binds the information into categories based on priority/ criticality, timeline (calendar), etc. which further gets distributed according to the student's profiles (department - specialization - year-date). The solution provides the freedom to customize the information which the student wants to receive. A single dashboard lets the student view and manages the information from a single interface. It allows the user to add, subtract, update and categories. It organizes and informs the student about the future tasks.
The users are in categories of students (UG, PG, Ph.D.) staff (academic, cash, hostel, etc.), faculty (different department ). My aim was to design a personalized dashboard for IITB students which can further be customized by them. Through the findings of my user studies, I observed that every department works differently and every student uses variable web space on intranet according to his or her personal preference.
Over the years the services on Intranet has spread exponentially. An Intranet is used to communicate and to collaborate amongst the users of an organization. Intranet enables workflow management, project management, etc. IITB intranet has four major divisions, which are populated and handled by different centers and a council.
These services did not provide user-specific menu and categorization to fulfill requirements of all the user groups from a single interface by providing all the information.
There were some system-level problems in the existing product as they were not stitched to work together. Therefore, the spaces showed irrelevant menu information upfront, the student had to visit multiple web-spaces to gather information and system did not recognize the Student ID.
Student use ASC extensively at the end or a start of a semester commonly.
The timeline shows a student's journey with intranet from the first day till last. After few stages, the journey is similar throughout the year. The information is in a loop when semester comes to an end. The user studies conducted with students at different stages of the timeline, starting from first time users to final year students in UG and PG program.
To view, manage, indicate the intranet service provided in IITB campus on a single page.
The method to be followed is to push useful, user specific and critical information upwards and up-front. Therefore inverted pyramid approach would let the user interact with relevant information. When the dashboard populates with updates, this approach will help get information up front.
If it is an intimation which is not critical present the facts first, the details could be read later if the user is interested. It will reduce the stress and time.
This chart explains which information will fall in as critical/must do, optional /can do and optional updates (not interested). All the updates mapped on time as the day of announcement/update, pending and reminder (deadline passed).
This Dashboard follows the approach in which few categories are fixed, and few are variable. Here the dashboard is majorly divided into three units of information that is.
Low fidelity prototype was given out to the users with specific user task. Think aloud protocol was used to decipher where and for what they were looking.