UrPlan by Team Corgi
Prototype
Lo-Fi Prototype
With the initial research done and guidelines set, we moved on to creating the initial wireframes. Each team member focused on a specific set of pages which we selected based on the design goals we had set. Our designs focused on the overall layout and functionality of the screens and we did our best to check off the design requirements we had laid out previously. This iteration of the prototype is meant to help us visualize what our solution will look like and makes it possible for us to begin evaluating our ideas. Starting with a low fidelity prototype allowed us to quickly show our ideas and get to feedback on it quickly.
A sample of our designs are below. From left to right: home page, explore events, my events, an example event page and create new event. Many of our pages use blocks for the event details, although they were yet to be standardized.
With our lo-fi screens done, we created a document to dive into more detail with our designs. These annotated wireframes show all the low fidelity screens we designed with markers to explain what is included with each. This also creates space for us to explain the more interactive aspects or other things that have not yet been included in the prototype. While this document is best used for presenting our ideas, it also forced us to spend more time with the details of our designs and notice where there may be something missing. This helps us to prepare for further iterations of our design.
Annotated Wireframes
Usability Test
With our digital lo-fi prototype, we conducted usability tests with three target users. We conducted these tests to evaluate the design ideas and choices of UrPlan.
Participant
Participants were those we had previously interviewed, all college students with some experience using technology to organize plans.
Method
For each participant, we give them the interactive prototype and asked them to do several tasks: “RSVPing to an event, finding a public event to go to, and creating an event”. We do not interrupt them when they are doing these tasks unless they are stuck and asked us for help. We will observe and take notes about how they interact with the prototype. When they successfully completed these tasks, we ask them some question about how and why they take certain actions.
Findings
Main issues:
-
Navigation between flows and from the home page was difficult for many. Navigation on each page was different (various home, back, etc buttons)
-
A lot of the labeling was confusing. Most of the users could guess what was happening, but there was still a lot of confusion.
-
Our prototype was not complete in some ways (buttons which were not working, etc) which was very confusing for interviewees.
We also conducted Rapid Iterative Testing and Evaluation (RITE) to discover and address major issues in our design prototype. This process includes letting a participant
With the suggestions from Usability Testing and further refined plan, we further improved the previous LoFi prototype. Each team member was responsible for a specific set of pages which we selected based on the design goals we had set. Our modications and changes focused on the solutions of problems that mentioned in Usability Testing, consistency and the overall interaction flow.
