The Seattle School Portal brings together several e-learning services that help students and parents manage tasks, grades and overall performance. Unfortunately, the current SPS portal is dated and hard to navigate and consists of multiple unique URLs.
Redesign the portal to make a clear connection between services, and add a simple, user-friendly navigation. The single platform should be easily utilized by busy and overwhelmed teachers, students, and parents. The solution should unify the software into one unique URL and mobile app, guided by principles of accessibility and inclusive design.
Figma
Photoshop
Illustrator
UX Research
UX/UI Design
Maya Suzumura
Tristan Pierce
09.2021 - 12.2021
or 9 weeks
There are 3 main groups of users of this service: teachers, students (from kindergarten to 12th grade), and their parents.
The Seattle School Portal serves the needs of users throughout the greater Seattle area. It is a multi-component platform that includes several different services such as The Source (grade checker), Schoology (assignment management), School Pay (payment system), Clever (useful learning apps), and bus notifications.For the research, we decided to use a qualitative approach in order to get a deeper understanding of the pain points of users, and the biggest problems with the current portal.
That's annoying that I need to use several different services instead of using one system.
When I'm paying for fees I never receive confirmation so I'm not sure if the fee was actually paid.
Can’t find assignments in the same place.
SPS has limited access and can be used only by approved users as teachers, students and their parents. During out interviews, we asked them to demonstrate how service works and created a Flow chart based on these information.
Service needs visual and usability cohesiveness and reduction of extra functions.
There are 3 main groups of users of this service:teachers, students (from kindergarten to 12th grade), and their parents.
Based on this data, we created 3 main personas:
By combing user pain points, main problems and previous research we created 3 main user flows:
We decided to focus on a dashboard and a calendar view set as a default for our users. After defining this principle, we moved to a lo-fi wireframe stage.
After making wireframes for flows and creating prototypes, we had a series of usability testing sessions with real portal users for each scenario. This gave us useful results because users had already used the previous portals.
Using this feedback, we refined our wireframes.
I feel attendance wasn't very necessary for me as a teacher and I won’t consider using it that much.
It looks like the card I use more often is already selected. Why is he lower than the other? It's usually different.
Why do I have due today and due in purple color? It will be better to have a deadline time instead.
As a parent, you are looking to complete any payments owed to the school.
Cart includes payment, pay later, search and history tabs. The pay later option can be used by users who meet financial requirements.
Starting from the dashboard, parent can seethe calendar and his tasks according to the dates. User’s tasks are color-coded, which makes it easier to orient between them.
As a teacher, you are looking to post a math assignment for your students to complete.
Starting from the dashboard, parent can seethe calendar and his tasks according to the dates. User’s tasks are color-coded, which makes it easier to orient between them.
By clicking side bar menu, user can go to the assignment page where she can check due dates and also create a new assignment. After it’s done, it’ll auto-populate on the calendar.
As a student, you are looking to mark your upcoming math homework as completed.
On the home screen of the dashboard, user can see assignments color-coded by different classes. He can click on the unchecked assignment to see details.
User check assignment as completed and it auto-populates as checked on the calendar view.
The portal should look simple and clear, but also have bright accents to keep children’s attention. To follow these principles, we decided to use mainly light background colors with color coding accents.
Using multiple tools in Figma, we made sure our color choices, type sizes and typefaces were inclusive and accessible for everyone. We checked the colors to make sure they worked for color blindness. We also wanted to make sure we included options during the onboarding process to customize the platform to whatever language you need.
Designed and prototyped screens illustrating the concept of redesign of a Seattle School Portal. A new design, that solved all main user problems.
Review its accessibility for different user groups. In the future iterations we want to: