AmaMuse
Storyboards
Our storyboards show possible user experiences based off of our design requirements. These experiences can result in different versions of the final product, and helped us define specifics when it came to user needs. Each team member created two storyboards, one hand-drawn, and one made with images. It was a fun and simple exercise that anyone can do, yet yields a plethora of information. For example, one of our story boards made us realize the difference between a user searching for someone with a specific skill set and a user offering their specific skill set. How will these two users find each other? Stories like this helped us expand on our functionality and implementation. For example, it was during this stage we realized that we would need an algorithm for newsfeed and search result displays, displaying posts of highest priority (tags, similar genre, similar following, etc.). Following this, we realized we would need other features like adding incentives to posts or viewing social media notification from the user’s profile.
​
Our design requirements and story boards allowed us to fully build out the functionality of our application, and we were able to start out information architecture...

Miguel Storyboard (Rios, 2017)

Daiana Storyboard (Kaplan, 2017)

Aleah Storyboard (Young, 2017)