CourseCompass
Mobile / UI + UX / Interaction
The Problem
So, UM students need more efficient ways to make informed decisions on course planning.
Target Audience
Goal
Context and Environment
Design Process
User Interviews
- Students need a platform that integrates course-related information.
- Students want easy ways of finding courses that fit their schedule, avoiding conflicts and planning courses (both short and long terms).
- Students need to hear more for advice from peer or senior advisors.
- Students want to hear experiences from previous students who have taken the courses.
- Students want to know what courses closely related to their interest fields.
- Students want to which courses can help them gain a career in their interest fields.
Personas
Competitive Analysis
QOC Diagrams
- The first diagram targets towards the basic needs of the users - how to help them schedule their courses.
- The second diagram targets towards the psychological needs of the users - to get more in-depth insights about courses and make informed decisions about course planning.
- The third diagram targets towards the self-fulfillment needs of the users - to find their interests based on the courses they have taken and find courses that align with their interests and career goals.
Narrative Storyboard
The purpose of creating scenarios and storyboard at this stage was to develop deeper understanding and details of the context of use and to make sure that my design system aligns with the users' needs and goals. In this process, I clarified the time and location where users would use my product. It also reminded me that incoming students may not be the primary user of this product, because they usually have to take required courses in the first semester.
Story Mapping & User Flow Diagram
Prototyping
After constructing a user-flow diagram, I made a low-fidelity prototype. I made the prototype interactable, so that I can do some early testing and get feedback.
I did 5 micro-usability tests. One problem is that the function of each icon on the tab bar is not clear, so I put description fields below them in the mid-fi prototype. Another feedback I received is that the sample academic plan is very useful, so I made it interactive. Meanwhile the profile page is not used very often, so I replaced it with the interactive plan. I also made a few changes to the UI design. This was the mid-fi prototype I made.
Now that the mid-fi prototype is more interactive and complete. I did a few usability tests again and get some new feedbacks. Based on the feedback, I evaluated the current design critically and decided to add a few more features. At the same time, I was not satisfied with the UI design, so I read Google's material design guideline, and this was the hi-fi prototype I made.
Key Features
Holistic Course Information
Interactive Academic Plan
This feature is designed to solve students' needs of long-term planning and determine their future paths. The plan shows a sample plan with required and recommended courses initially. Students are allowed to add/remove courses from the plan. The tool provides an easy way for students to plan in advance and find their desired path more easily. Because once they have made a plan, they would know better what their goals are and be more persistent towards their goals.In addition, the system checks pre-requisites and other enrollment requirements automatically. It also prevents students struggling to meet graduation requirements in their last semesters.
Course Listings by Fields
I decide to give this feature an important role because my biggest design goal is to help students find their interest. I want to encourage students explore on their own instead of relying too much on the recommendation system because this is an important decision they should figure out on their own. Meanwhile, my tool would make the process as easy as possible.
Course Eligibility Checklist
This feature helps students generate schedules easily by automatically checking enrollment requirements and time conflicts. Students can add sections/courses to the checklist, and the checklist would find a workable schedule for them. If no workable schedule can be found, the system would tell students what courses conflicts. This would be helpful when courses have many sections. To enhance the inclusiveness and usability of the app, the app also allows students to choose their preference, such as class time and instruction mode, for the system to make general more personal schedules.Final Thoughts
Technical Feasibility
Reflection
One lesson from my needfinding interviews was that not all users are like me. Some students tended to make careful decisions before choosing classes and some just chose randomly. It was also different how each student feels about their interest level of their paths. The needfinding interviews broadened my perspective and made a foundation for my following steps.
Another lesson I learned was to speak with different people, whether it's about knowing the problem and the users more or about the design itself. I think speaking with other people, learning their perspective and listening to their advice helped me refine my design.
Last but not least, I think it was very helpful to be critical about the design throughout the design process and keep thinking deeply about the goals and needs of users. Sometimes, just rethinking the design features and the goals can give me inspiration.
Challenges
Another challenge was to discard the bias of myself as a designer and to really listen to the perspectives of different students. Because I was also a student, I always reminded myself to leave my opinions aside and accept users' opinions.