Creating an engaging space for parents to track their childrens' reading
Created a statistics page and led the user research process.
Timeline
Client
Role
Skills
Jul - Aug 2025
UI/UX Designer, Researcher
Figma
Zeal Technology Solutions
OVERVIEW
With a team of four, I conducted stakeholder interviews, user research, and user testing to design and prototype the Statistics page.
Through the UX Design course in Northeastern's Seattle campus, our project was to solve the problem of limited visibility and communication between parents and their child’s reading progress and development. Our team of 4 worked together to design the web platform through Figma, focusing on solid user understanding and iterations.
Approach
Our mission was to create a user-centered platform that makes supporting their child’s reading progress more motivating for parents. Through multiple iterations and user testing and feedback, we produced a design solution, referencing usability design and lessons learned in class.
My Responsibilities
-
Design and prototype the Statistics Page ​
-
User Research and Usability Testing​
-
Branding of Reading Galaxy (logo, color palette)
How might we make deciding where to go more collaborative and engaging for everyone in the group?
INTERVIEWS WITH USERS
We conducted a user interview with two parents and one current teacher.
Since teachers and parents are our primary users, we made sure to interview members of both audiences. We organized our interview notes into three key categories: successful existing strategies, problems, and wants and needs. This helped us identify what was already working, where users were experiencing challenges, and what they were looking for in a solution.
Interview Notes
Affinity Diagram: We synthesized similar notes/patterns into a diagram
USER PERSONAS
I then made user personas to capture the needs and behaviors of our primary users.
I looked at 6 common trip planning platforms and noted how they balance structure with the organic way groups discuss trips.
INFORMATION ARCHITECTURE
Before moving to wireframes, I created a sitemap to organize key features.
I mapped out the platform’s main features and how they connect to create a clear navigation structure. This helped align the team and guide the overall design process.
Key Features
-
Dashboard — Central hub for navigating the platform
-
Statistics — Visualizes a child’s reading progress and statistics
-
Reading Log — Allows parents to log their child’s reading activity
-
Reading Recommendations — Lets parents recommend books to one another and build a parent community
-
Teacher Notes — Allows teachers to leave and review personal notes about each child
DESIGN EXPLORATION
I focused on including four categories in the Statistics page: Genres, Reading time, Comprehension, and Achievements
I explored different ways to visualize each category while keeping the Statistics page easy for parents to understand at a glance. I then tested the designs with users to understand what information felt most useful and where the experience could be improved.
Button vs. Static Text
All four peers who tested our prototype thought the stats at the top was text rather than buttons.
Text lacks Clarity
"What is meant by the share button? Does it mean you are uploading the data? Exporting?"
Bad Communication
The stats button on the top doesn't specify timeframe. Do 214 minutes read mean in the week, month, or all time?
Varying Detail Levels
Parents may have different preferences for how much detail they want to see in their child's reading stats.
MEDIUM-FIDELITY WIREFRAME
Using the feedback given from my peers and client, I refined the layout and usability of the Statistics page.
I focused on streamlining the navigation process and added an initial stats overview page that displays total reading statistics and child profile, with a section at the bottom allowing parents to click into each category to view more detailed information.
The "share" button was replaced with an "upload" button and paired with a recognizable icon.
Reading summary overview that automatically displays total statistics. "Last updated" indicates "all time" stats.
USER TESTING + EXPERT FEEDBACK
Some users had difficulty recognizing that the bars in the graph were interactive, since they did not expect a data visualization to require interaction. This highlighted the need to make interactive elements more discoverable. In our expert review, we also learned that minimizing the number of clicks is essential to helping users access information efficiently without unnecessary navigation.
FINAL DESIGN
I brought our research and feedback together into the final design.
Added a timeframe toggle for clarity
Integrated data visualizations directly into the main page to reduce the number of clicks and improve accessibility
Refined the reading summary overview to clearly present the data (no slider)
Final Statistics Page
The reading summary provides an overview of each child’s reading statistics, while the visualizations below offer more detailed insights.
FINAL PROTOTYPE
This prototype was used to demo the behavior to developers during handoff.
The prototype assumes user data (profiles, user progress, preferences) is stored securely and can be retrieved. It also assumes that the system stores metadata about books (genre, Lexile level, etc.) and uses it across features.
Data visualizations show further details upon hover
The info tooltips show contextual details, such as which book was read and how long, on specific days of the week.
POST-DESIGN TESTING
To measure usability, my team and I conducted a usability evaluation.
My team and I conducted a usability metric to evaluate how easily users could interact with the platform and identify areas for improvement. This was the usability metric for the task of "checking the child's reading stats."
KEY TAKEAWAYS + LEARNING
This experience sharpened my Figma and collaborative design skills!
The importance of usability testing and iterative design
Through this project, I learned the importance of usability testing and iterative design in creating intuitive user experiences. Each round of feedback showed how small adjustments can improve clarity and interaction with an interface.
Communicating effectively with users for interviews
I also learned how to communicate effectively with users during testing sessions such as creating a comfortable environment and applying psychological principles by asking unbiased, non-leading questions. This experience prepped me well for future clients and stakeholder meetings.
Research is the necessary foundation to better understand users.
I hope you found something worth exploring.