Simplified school admins' course progress analysis and reporting through user interview, requirement definition, and testing
Lab.computer is a web-based coding environment designed for programming education. It enables students to code and submit assignments online, while instructors can grade and provide feedback on assignments, eliminating the need to set up programming environments.
ROLE
As a product designer, for 3 weeks, I was responsible for:
• Gathering requirements by talking to the client
• Ideating and designing solutions and prototypes in collaboration with an engineer and founder
• Testing with the client to get feedback
• Handing detailed flows and design specs to engineers via Figma
CHALLENGE
When the client and I had a product feedback meeting with a user, the school admin user mentioned that he wanted to improve a way to extract grading for reporting to his client. We saw it as an opportunity that could differentiate the product in the market and believed that a solution could be an essential feature to sell the product to the targeted clients - schools and education services.
The problem statement is:
How can we make the analysis, reporting of course progress, and engagement faster and easier for professional school admins?
DISCOVERY
To understand user needs, I needed to understand his current process and pain points. I interviewed the user about “What,” “How,” and “When” he reports to the clients and the obstacles that he is facing in the process.
ASSUMPTIONS
• Every professional school admin needs to analyze when they need to report course progress.
• Most corporate trainers visualize the analysis instead of handing over a spreadsheet.
FEATURE DEFINITION
Based on the discussion with the client, I defined the high-level requirements for a solution.
Users can view the analysis with measurements:
Who students are (Individual students/whole class)
What students have done (Each quiz/assignment)
Time duration (Whole course duration)
Users can view the outputs:
Submission rate (%)
Score (%)
Ranking
Users can download in the form of:
PDF
PNG
JPG
Users can create:
One graph/view at a time
Selected graphs at once
SUCCESS METRICS
Time spent creating overall course graphs
Time spent creating individual reports
Number of students
USER FLOW
With the requirements, I defined three possible user tasks with the feature.
The user mentioned that he needs to produce graphs of the overall score and submission rate of assignments and student ranking.
The user mentioned that he needs to produce graphs of the overall score and submission rate of each student.
The user needed to collect data and create graphs, which took a significant amount of time.
TESTING
• How do you look at the overall course performance in week 1?
• How do you download the charts and graphs for the overall course?
• How do you look at one student’s performance in week 1?
• How do you download the charts and graphs for the student's performance?
QUALITATIVE RESULT
There is a class where he has more than 50 assignments. In order to show all of them on one page, a horizontal bar chart is better suited than a vertical chart.
He is only interested in looking at and exporting Top 5 or 10 and Bottom 5 & 10 rather than the full list.
He uses another platform for multiple-choice questions. In order to analyze the class progress, he might need to combine raw data from different platforms into one Excel file.
QUANTITATIVE RESULT
During the testing, he spent 1.7 minutes on the overall course graph and 0.7 minutes on the individual student graph. In contrast, it takes him 3 minutes to extract a grade for one student and 6 minutes to create a graph using Excel.
ITERATION
A user can see the graphs with many assignments without scrolling, and the graph height will adjust based on the number of bars.
A user can have Top 5, Top 10, Bottom 5, Bottom 10, and the full list on the student ranking.
A user can select the raw data export at the beginning of the export process. (It is only available for the course analysis page.)
NEXT STEP
I couldn't assist with implementation since I was no longer part of the team when the client started implementation. I left UI specs for developers to implement the design pixel-perfectly.
LEARNINGS
Working with a single client streamlined the process by focusing on one voice instead of navigating varied feedback. However, seeking additional feedback would provide diverse perspectives to better cater to user archetypes.
By maintaining constant communication with the client, I grasped their business needs and technical capabilities to design what they could build. Adhering to their current design ensured a consistent user experience, helping users understand how the new feature works.