When making the User Flow, I started by evaluating the needs of my user by looking at the User Journey Map. I tried to put myself in the shoes of a middle school student and see the learning platform from their perspective. I then developed a hierarchy of levels, starting with the log in screen. I then thought about the student needing a home base within the platform, so I developed a Student Dashboard. From here the student can access all areas of the learning platform, but to keep it streamlined, there are 8 categories (Octo). I broke each main section down into actions that the student can take from that page. The second main page for a student will be the Classroom. From here the student will be "locked in" during class, but will also have access to all they need within the platform for class, again in 8 categories. After my User Testing session I discovered a few navigational concerns as well as naming concerns. I addressed these issues and edited my User flow. This week I looked at it again and added 2 additional categories to the classroom (to total 8).
I realized that the User Flow is all about organization and ease of access. The user needs to intuitively understand how to navigate and there should be as little possibility fr confusion or user error as possible. In the case of middle school users, they already have enough to worry about dealing with learning curriculum, their learning platform should be streamlined and easy to use.
This week I also continued to refine my logo and word marks. I am still trying to figure out how to incorporate the logo into the word mark and have the octopus interact with the letter forms. I will continue to work on it in the coming week.
MFA Graphic Design Student at Academy of Art University of San Francisco (on-line)