Lexplore
Simplifying a data-heavy screening platform
Oscar Viking Jansson
Game & UX/UI Designer
2021
Lexplore is a screeningtool made for teachers to map students ability to read with the help of eyetracking. The technology makes it easier to discover students difficulties in reading both quietly and out loud. The data provided from the screening is then used to draw conclusions about the student’s reading abillity.
Team Size
4
Role
UX Researcher
Timeframe
7 Weeks
Goal
Simplify Lexplore’s data-heavy screening platform and reduce administrative workload by transforming complex eye-tracking analytics into clear, actionable decision support for individualized student interventions.
Responsibilities
Conducted interviews, surveys, and thematic analysis to identify distinct workflows and pain points between classroom teachers and special educators.
Project Deep Dive
The Challenge
The information presented in Lexplore's service is often detailed and requires a high level of knowledge about reading development, data and statistics. At the same time, they want to create a tool that reduces time for administration among teachers and helps them to implement the right individual measures for students.
Core Question
How can we simplify an information-heavy software in favor of our users, enabling teachers to make rapid, individualized interventions for every student?
Process & Methodology
Target Group Analysis
External Monitoring & Benchmarking
User Interviews
Quantitative Surveys
Thematic Analysis & Pattern Identification
Persona Development
User Journey Mapping
Impact Mapping
Value Proposition Canvas
Ideation Workshop
Key Recommendations & Wireframing
Research & User Archetypes
To reach any form of conclusion in this case we first needed to make sure that we have our focus on the right target group. Because there are different kind of roles in teaching we decided to put our focus on the elementery school teacher and the special ed teacher because they are the main users of the tool.
After defining our targetgroup we started getting to know them. By external monitoring and by conducting user interviews we started our research. Our biggest challange in this phase was that we felt it was hard to process all the information we gathered and we were quite overwhelmed by it. But after a while we started to see patterns regarding our users and this led to us reaching some insights in terms of their goals, needs, problems and pain-points. To summarize the information we had gathered and to empathize even more with our users, we made personas.
We made two personas. One for each of our two usertypes. We could easily understand our users throughout the process thanks to our personas. In almost every part of the process we had them available to help us make the right desisions and to reach the best conclusions.
Personas
User Journey
Trying to understand how our users interact with the tool, what they feel and think and the overall steps they take we made user journeys. This gave us an understanding of what frustrations the tool induce with our users. It also gave us clues as to what needs to be improved in the tool itself.
Impact Map
Impact mapping helped us explore if there was a coreleation between the goals/needs of our users and the goals of the company (Lexplore). We formulated the needs of our users and how those needs could be fulfilled in the form of solutions/functions. The needs of our users could be compared with the goals of the company. If there was a match, we checked what solution/function we had related to that specific user goal and could be sure we went ahead with the right idea.
Key Design Recommendations
A simple overview of the individual student
We saw that our teachers job situation demanded that they always was on their toes. Unforeseen events is a part of their job and their everyday situation. A screening process with one student is not much of a hassle, but with 35 students, it becomes a problem.
Therefore, instead of putting the focus on quantity we thought of a solution focusing on quality. Verified by our research we found that many functions in the view of a single student isn't necessary for the type of decisions a teacher have to take.
Adapt information according to needs
Our other user type, the special ed teacher, has a different work situation than the regular teacher. She works with students in need of special education, far less students and almost always with one at a time. She has a bigger interest in data more indistinguishable data so that she can understand why the student has a lower score and so that she can make the best possible decision to benefit the student.
Therefore we developed a solutions making it possible for all users to choose which kind of view they want to see. Advanced view or a simpler view?
Simpler interaction
It is common that a screening does not only take place in class, some students need to be followed up more frequently than twice a year.
Our solution: the educators can quickly and easily access the most recently screened students on the landing page without looking them up in the class list.
Regardless of how often the educators log in and out of the platform, it should be easy for them to take on the work where it was last completed.
Our solution: the educators get direct access to recently visited classes, groups and pages without having to think twice.
The students level can differ greatly within one and the same class, which makes it difficult for the educator to adapt the education for everyone.
Our solution: an opportunity to, in addition to class division, see students who have similar needs for support and pair them in groups. As well as the opportunity to offer educational materials that are adapted to the needs of the group.
Takeaways & Impact
Advanced diagnostic tools only deliver real value when their information architecture aligns with users' operational constraints and mental models—shifting the experience from raw data to actionable decision support. By utilizing Impact Mapping, we maintained strict strategic alignment, actively filtering out low-value feature ideas to focus exclusively on validated user needs and core business goals.
The resulting deliverable provided Lexplore with a prioritized concept framework, wireframes, and concrete UX recommendations, establishing a clear, actionable roadmap for future product iterations.
Project Deep Dive
The Challenge
The information presented in Lexplore's service is often detailed and requires a high level of knowledge about reading development, data and statistics. At the same time, they want to create a tool that reduces time for administration among teachers and helps them to implement the right individual measures for students.
Core Question
How can we simplify an information-heavy software in favor of our users, enabling teachers to make rapid, individualized interventions for every student?
Process & Methodology
Target Group Analysis
External Monitoring & Benchmarking
User Interviews
Quantitative Surveys
Thematic Analysis & Pattern Identification
Persona Development
User Journey Mapping
Impact Mapping
Value Proposition Canvas
Ideation Workshop
Key Recommendations & Wireframing
Research & User Archetypes
To reach any form of conclusion in this case we first needed to make sure that we have our focus on the right target group. Because there are different kind of roles in teaching we decided to put our focus on the elementery school teacher and the special ed teacher because they are the main users of the tool.
After defining our targetgroup we started getting to know them. By external monitoring and by conducting user interviews we started our research. Our biggest challange in this phase was that we felt it was hard to process all the information we gathered and we were quite overwhelmed by it. But after a while we started to see patterns regarding our users and this led to us reaching some insights in terms of their goals, needs, problems and pain-points. To summarize the information we had gathered and to empathize even more with our users, we made personas.
We made two personas. One for each of our two usertypes. We could easily understand our users throughout the process thanks to our personas. In almost every part of the process we had them available to help us make the right desisions and to reach the best conclusions.
Personas
User Journey
Trying to understand how our users interact with the tool, what they feel and think and the overall steps they take we made user journeys. This gave us an understanding of what frustrations the tool induce with our users. It also gave us clues as to what needs to be improved in the tool itself.
Impact Map
Impact mapping helped us explore if there was a coreleation between the goals/needs of our users and the goals of the company (Lexplore). We formulated the needs of our users and how those needs could be fulfilled in the form of solutions/functions. The needs of our users could be compared with the goals of the company. If there was a match, we checked what solution/function we had related to that specific user goal and could be sure we went ahead with the right idea.
Key Design Recommendations
A simple overview of the individual student
We saw that our teachers job situation demanded that they always was on their toes. Unforeseen events is a part of their job and their everyday situation. A screening process with one student is not much of a hassle, but with 35 students, it becomes a problem.
Therefore, instead of putting the focus on quantity we thought of a solution focusing on quality. Verified by our research we found that many functions in the view of a single student isn't necessary for the type of decisions a teacher have to take.
Adapt information according to needs
Our other user type, the special ed teacher, has a different work situation than the regular teacher. She works with students in need of special education, far less students and almost always with one at a time. She has a bigger interest in data more indistinguishable data so that she can understand why the student has a lower score and so that she can make the best possible decision to benefit the student.
Therefore we developed a solutions making it possible for all users to choose which kind of view they want to see. Advanced view or a simpler view?
Simpler interaction
It is common that a screening does not only take place in class, some students need to be followed up more frequently than twice a year.
Our solution: the educators can quickly and easily access the most recently screened students on the landing page without looking them up in the class list.
Regardless of how often the educators log in and out of the platform, it should be easy for them to take on the work where it was last completed.
Our solution: the educators get direct access to recently visited classes, groups and pages without having to think twice.
The students level can differ greatly within one and the same class, which makes it difficult for the educator to adapt the education for everyone.
Our solution: an opportunity to, in addition to class division, see students who have similar needs for support and pair them in groups. As well as the opportunity to offer educational materials that are adapted to the needs of the group.
Takeaways & Impact
Advanced diagnostic tools only deliver real value when their information architecture aligns with users' operational constraints and mental models—shifting the experience from raw data to actionable decision support. By utilizing Impact Mapping, we maintained strict strategic alignment, actively filtering out low-value feature ideas to focus exclusively on validated user needs and core business goals.
The resulting deliverable provided Lexplore with a prioritized concept framework, wireframes, and concrete UX recommendations, establishing a clear, actionable roadmap for future product iterations.
Oscar Viking Jansson
Oscar Viking Jansson