When we examined the technological capabilities of the product, we noticed the high value it produces in analyzing the student's progress in reading. The problem was that we assumed that the student's parents would see high value in analytics. We didn't imagine that parents have no real value in this data because they don't know what to do with it.

But from the teacher's point of view, the need was obvious. And through in-depth interviews with several teachers, we were able to put up a system and a dashboard for the teachers to use.
Our goal was to produce a system that would ease the existing situation of assistant teachers in several aspects.

The first thing we decided to investigate is how the teachers monitor and check the personal reading progress for each student. Another understanding we tried to understand was what the accepted method in schools in the United States is to deal with students who have difficulty reading. Do they get extra tutoring outside of their classroom? Other questions we wanted to check our how the teachers keep in touch with the student's parents.

We spoke with several elementary school principals as well as district principals. I wrote the interview questions, and the product manager conducted the interviews. The research gave some fascinating insights that guided us later in the design phase.

We clearly divided each component according to explicit heuristics in most of the firms.We did not encounter a problem except for two issues we had difficulty solving.
After we mapped the hierarchy of the categories, we started designing the user journey from the onboarding stage until reaching the main board.
Student Dashboard- The teacher can monitor the student's reading results and progress.
Users- A list that manages all the students who use the device, with the option to filter by groups or classes
Plans-Manage the devices you have and their programs
Discover- Essential learning of using the device and how to use it in your daily life.
Home screen-A general view of the devices and users' activity, plans, and updates.
Our most significant difficulty was creating a system suitable for both a physical device and a web platform. In a multi-cross device environment, we encountered issues that we had not experienced before-Our first solution was to activate the device and then force it to register itself as a user, But we understood that this could confuse him.

We used the concept exposure method, which is a type of semi-structured interview that, in the end, presents a prototype of the product to the user, and then he is asked a series of questions about what he understands from the product. The user experiences it and thinks out loud about how he would use it daily. Through this exposure, we know the user's way of thinking through the prototype we createdThe main goals of the dashboard are divided into an overview where the teacher can quickly and easily locate the student's improvements and performance. We divided the screen into three parts:

after that we made a usability testing and we got a great insights for some of our question.

After understanding where improvements need to be made, we mapped and coded the components to find repetitive behaviour. My main resrach insights

(1) The reading comprehension graph was not intuitive enough.so the solution was to turn it into two separate graphs. Do not insert another form of a chart that needs to be learned
(2) The teacher often identifies one problem and misses another-the list of problems is arranged according to the hierarchy. In the end, there will be a general tip.
(3) Need to sort groups of students according to their problems-so on the users' page, we will add an option to: "sort by..." where we will also enter sorting by specific problems.