UX UI Design Sprint
The SJSU UX UI Association partnered with AskClass to host a 2 day design sprint for students as an opportunity to collaborate, build teams and gain experience.
Overview
Timeline
Tools Used
My Role
Team Members
2 Days
UX/ UI
designer
Priscilla Felix
Celeste Sandoval
Context:
The UX/UI Association at SJSU hosted a 2 day student-run design sprint that helps students gain experience and knowledge in the field of UX. The UX/UI Association wants people to build projects with a meaningful impact and hope to learn through real-life experience.
⚡️The Challenge
How are professors able to look at collaboration activity in group projects?
AskClass is a tool designed for students and teachers where they are able to efficiently engage. This tool helps engagement between the students and teacher where they are able to use social and emotional skills that encourage better relationships and classroom dynamics.
The Solution💡
Creating a module within AskClass that allows professors to view student contribution and collaboration on group projects.
Creating an easy-to-use module where teachers can view student contribution and collaboration based on individual student ratings. Essentially, students will be able to rate each other through this module and professors will be able to view it.
Design Process
1.
Research
The first step in understanding the problem we needed to solve was interviewing the users. On day one of the design sprint we conducted six semi-structured interviews with professors from SJSU to gather more information on their issues with classroom collaboration within groups.
Through these interviews we conducted we aimed to learn more about how they use existing websites like canvas, to keep track of classes and students. These interviews revealed that although they are accustomed to these websites, they do have limitations. These limitations included managing groups and viewing collaboration within them.
2.
Sketching
My team member and I began to sketch out ideas to brainstorm and visualize what direction we would take.
3.
Persona
For step three we created a user persona based on the information we gathered from the interviews.
4.
Journey Mapping
We created a journey map to visualize and further understand the process the users go through when they interact with existing applications. Journey mapping helped us examine the weak points to create a strong user centered design.
5.
Wireframing
This was our wireframe for our design, a rough lay out of our structure. Here we focused on how we could create an accessible and efficient structure.
6.
Presentation
The final step of our design process was presenting our prototype on the second day to receive feed back. We wrapped up the final designs and presented our prototype to our peers and judges.
Final Design
Dashboard
This is the initial landing page for the module. Professors can select what they would like to do. This includes a "check-in", "classes" and "announcements " buttons. We decided to keep the design and structure very simple and focused on the hierarchy, emphasizing the call-to-action buttons.
Classes
The next screen displays the classes the professor is currently teaching, this is shown when the user presses the "classes" button in the previous page. My team member and I wanted to create a dashboard where professors can access the different classes in an efficient manner. The three main buttons are the focal point of our design that lead the users' eyes to easily take the next step.
Class / Teams
Once the professor selects a class the screen will display the teams within that class and students. In this screen professors are able to select a specific team or student and it will open to their assessments.
Team Metrics
In the teammate assessments page, the professor will be able to view the team and its group members. Group metrics were a vital feature to have and showcase in the application so having a design that emphasized this was essential.
Individual Student Metrics
In the student portal, we wanted to create a similar design feature to group metrics. Instead we made an individual student portal where professors can look at a specific student in a group; and see the collaboration metrics. We also incorporated a peer evaluation that only the professor can access.
Takeaways
This design sprint was a great opportunity that allowed me to collaborate with other designers and gain real life design experience. Although we did not place in the design sprint, I was still able to practice my design thinking skills and receive feedback. This allowed for my partner and I to reflect on what we would improve next time.
What I would change
1.
Graphics
I would remove the vector graphics because they can be distracting to the user and essentially do not add to the design/ have no purpose.
2.
Prototype
This was my first time using Figma, although I have prior experience with other prototyping softwares like Adobe Xd, I was not as familiar and comfortable with this program. I felt like I could have provided a better high fidelity prototype If I had more time to learn and get comfortable with it. There was also certain functions that didn't work as we wished due to technical issues we were having that could be easily fixed with more time and practice.
3.
Metrics
Showcasing certain metrics were very important to some professors, after receiving this feedback I would improve my design by incorporating where the metrics are coming from when showcasing student assessments.
4.
User Testing
Since time was limited to 2 days, we did not have the opportunity to conduct user testing with our final design. Next time I would hope for the opportunity to be able to do user testing to gain a better understanding if our suggestions in our design created an easier website application for professors to view student collaboration.
