As I examined the product's technology, I discovered its potential in analyzing students' reading progress. While our initial assumption was that parents would find the analytics valuable, I soon realized that they may not know how to use the data. On the other hand, teachers clearly recognized the need for this information.

To ensure that the system and dashboard met their needs, I conducted in-depth interviews with multiple teachers. My primary objective was to design a system that could ease the workload of assistant teachers in various ways.

Initially, my primary focus was to understand how teachers currently monitor and assess each student's reading progress. Additionally, I wanted to understand the established methods used in American schools to support students who struggle with reading, such as providing extra tutoring outside of the classroom. I also wanted to explore the communication channels used by teachers to keep in touch with students' parents.

To gather this information, the Product Manager and I interviewed several elementary school and district principals. I drafted the interview questions and the Product Manager conducted most of the interviews. The research provided valuable insights that helped guide us during the design phase of the project.

I then organized each component based on commonly used heuristics in most companies. I did not encounter any major issues, except for two challenges we had difficulty resolving. After organizing the categories into a hierarchy, I began designing the user journey from the onboarding stage to the main dashboard. This included the Student Dashboard, where teachers can monitor students' reading results and progress, a Users section for managing students who use the device, with the option to filter by groups or classes, a Plans section for managing devices and their programs, a Discover section for learning about the device and how to use it in daily life, and a Home screen that provides a general overview of device and user activity, plans and updates. My biggest challenge was creating a system that was compatible with both the physical device and the web platform. In a multi-cross device environment, we encountered issues that I had not previously encountered. Our initial solution was to activate the device and then force it to register itself as a user, but I realized this could be confusing for the user.

I utilized the concept exploration method, which is a type of semi-structured interview that involves presenting a prototype of the product to the user and asking them a series of questions about their understanding and potential usage of the product. The user experiences the prototype and provides feedback on how they would use it in their daily life. This method allowed us to gain insight into the user's thought process and how they interact with the prototype we created. The main goal of the dashboard is to provide an overview where the teacher can quickly and easily see the student's progress and performance.

I divided the screen into three parts and then conducted usability testing to gather further insights and feedback on our design.

After identifying areas for improvement, I analyzed and coded the components to identify any repetitive behavior. My main research insights were:

(1) The reading comprehension graph was not intuitive enough, so we decided to split it into two separate graphs and avoid adding any additional charts that would require additional learning.

(2) Teachers often identified one problem but missed another, So I arranged the list of problems according to a hierarchy, and added a general tip.

(3) The need to sort groups of students according to their specific problems, so on the users' page, I added an option to "sort by" and included sorting by specific problems.