UrPlan by Team Corgi
Design Process
Storyboards
Storyboards help us to closely inspect how our design can help our users in their daily settings. Our storyboards were the first imaginings of what our product could do, while focusing on the user’s experience and how it fit into their lives. We designed these based on the interviews and other research we had done, trying to fill in the gaps that currently exist in this space. These storyboards are how we began to discuss and think about what would be included in our final designs and have direct links to our design goals and requirements.
Below are 3 examples of storyboards we created. These all imagine different scenarios surrounding social events and planning and several of the example features even made their way into our final designs.
Using the results of our interviews and competitive analysis, we translated our user’s needs and responses into our Design Goals and Requirements. The goals are the broader things we hope to accomplish with the design, while the requirements are specific tasks users should be able to carry out. Our requirements followed the format of “Action, Object, Context” and “Data, Functional, Contextual,” which helps us be more specific and structured. These goals and requirements are built from the areas we identified in previous portions of this project as being necessary and will go on to help us as we begin to create the screens for our app.
Design Requirements and Goals
-
Find available events
-
Suggest nearby ongoing events to join
-
Set up events for others to join
-
Increase the average attendance of events
-
Generate a common time for all participants
-
Planners and attendees can share highlights from the event
-
Q&A sections for users to ask questions about the event
-
Polling for events
-
Reminders for polling and attending events
-
Ability to form interest groups and invite the whole group
-
Ability to make posters for events quickly and easily
Goals
-
Make it easier to meet new people and stay in touch with friends
-
Help to build communities of people who share hobbies and interests
-
Allow users to engage with these tools without having to learn new platforms.
Requirements
Information Architecture
To go along with the low fidelity prototype, we created a information architecture diagram. As seen below, the home screen is the root, with the 3 main functions coming off of it: viewing your upcoming events, exploring events available in your area, and creating a new event. The nodes that extend from those 3 illustrate the other pieces of that portion of the app. This diagram helped us to fill in the gaps of what needs to be included in our app and connect the dots of what we were missing or where we could better connect the flows we had originally connected. Features were chosen based on the design goals and requirements we created from the research we did. This also sets us up for what we need to add to the final prototype and how we should link our pages together.
