Project completed as a team including, Carin Camen, Hannah Ho and Laurie Penalber.
IDO is a concept application I built as a part of a small team during my studies at DePaul University.
The assignment was to create an integrated experience application that would enhance the users enjoyment of an activity or event before, during and after it happened. Our team chose weddings as the even to target because we believed that there was a lot of room to aid wedding couples in planning and documenting weddings.
iDO application concept statement.
Due to the fact that our team was dispersed across 2 states, we had to complete this project entirely online. We met on Google Hangouts to use voice chat to discuss major project points and used email inbetween meetings. We kept our shared working documents on Google Drive.
Each team member conducted 2-3 contextual research interviews on various types of wedding attendees - from vendors like photographers to brides and grooms. During this research we concluded that potential users of our application have difficulty juggling all the planning tasks involved with a wedding. They wanted help negotiating planning and communication - especially between brides/grooms to the wedding party and brides/grooms to vendors.
My contribution to our group's prototype was the to-do list wireframes and task flow.
Wireframes of adding an item to the to-do list - version 1.
Our group chose to create our wireframes tablet sized because we intended this application to be used on web and mobile - by using tablet sized wireframes in order to get a feel for both worlds while constrained by the timeline of the assignment.
While designing the to-do list, I wanted to make sure that it would be easy to use, but also include the robust functionality that a wedding task list needs - including adding/removing tasks, marking tasks complete, sharing to specific people or groups of people and editing.
After the group completed the interactive prototype using mybalsamiq we each conducted two usability evaluations. During our evaluations we tracked both quantitative measures (time to complete task, number of errors, number of clicks) and qualitative measures (noting what was confusing or frustrating to the user and asking them to explain why.)
Our prototype tests returned many valuable insights to our design. One of the major issues our users had was with the menu bar on the main page. In our original design it included both text and icon links. This confused users because they did not see it as a single entity on the page.
In a second iteration of the design, I suggested we change the menu bar to include icons only.
Wireframe of to-do list - version 2, with updated menu bar.
