| Analysis |
|---|
 Image Added
| Design 1: Linear timeline
The user is initially presented with a series of checkboxes (much like the "customized build" of Bootstrap) that allows him or her to specify which services, events, and features they would like to be included as part of the wedding, based on resources, personal preference, etc. A timeline of circles is generated from these choices, based on a sample order. The user is presented with this timeline, and can drag and drop the individual items to rearrange them along the timeline. Once the order has been confirmed, the user can then navigate through the events/tasks on the timeline one by one. Each circle on the timeline represents an event or task, and its color indicates the completion status so the user can see what needs to be done and their overall progress. When all events/tasks have been scrolled through, the user can see a summary page with an overview of all the items of the timeline. |  Image Added
| Design 2: Requesting feedback/notifying parties
Tasks and events are displayed on a sidebar, broken down by month. For each action item, the user can see the details of their choices (venue, vendor, time, etc). They are presented with two options: getting input and notifying involved parties. For the first option, the user can pose a question in a text area. The pictures and details of all involved parties are displayed, and the user can select which specific people to solicit feedback from, much like a Facebook invitation. For the second option, they can review all the information for the task or event and then select which parties to notify with a similar interface as the first option.
Design 3: Calendar view (design for the elderly)
To make the interface more learnable for elderly users like Lucille, who may not have experience with modern web applications, this design makes use of a calendar metaphor. The events are highlighted on the calendar and only one event has focus at a time. These are stepped through one at a time to make everything clear and obvious to the user. Here I pursued two different possibilities: in the first, after reviewing all the events, the user is presented with a macro overview of the entire timeline and can submit feedback on the timeline as a whole. However, after more thinking, I felt a second option would be more suited for elderly users---for each event, they give a thumbs up or thumbs down, and only when they thumb down a specific task or event are they prompted for feedback on that specific item. | Connie's Sketches | Analysis |
|---|
 Image Added
| Design 1: The user first sees two options on the landing page: seeing sample timelines or creating one of his/her own using a quick start feature.
Sample timelines emphasize the budget, amount of time spent planning, location and suggested milestone dates.
Once the user is ready, he/she can set up their own timeline using the information they have at the moment to populate a timeline of events to complete.
Getting input from other people involves going to a page that aggregates all of a certain type of info (i.e. the page that contains all the info about potential caterers) and dragging and dropping photos and hiring details into a message box that will send this information to users who also have accounts on our website. They will receive it as a nicely formated message that hey can respond to. |  Image Added
 Image Added
| Design 2: The user goes through a similar process of populating a timeline as Design 1's process, but in this design they will have the option to expand the timeline into child timelines that are more specific to a type of task (finding/booking catering, finding/booking a venue, etc.) because all of these have different schedules that each contribute to the overall timeline of things to complete. Under each child timeline is also the option to add to-do list type tasks for actionables that do not have a deadline (one flaw of the timeline is that every item on it needs some date associated with it)
The user can share their timeline to a select group of people using a unique generated link. The people with access to the timeline will have the ability to click anywhere on the timeline and add a public or private comment in a Google Docs style, raising "issues" that the main user will have to resolve. This commenting system is designed to encourage specific feedback on specific decisions or deadlines on the timeline, while also being visible enough to generate discussion to help the main user make all the involved parties happy.
|  Image Added
| Design 3: This design is for the elderly. This is the interface a grandparent might use -- it is a simple calendar that only lists the important deadlines and dates that the bride-to-be is considering. Under each date entry, there is a smiley and frowny face. Clicking the smiley face will signal that the older user is happy with the choice. Clicking the frowny face opens up a box where they can send feedback about the event.
The older user should not have to deal with emails, accounts or anything other than a calendar, which they should already be familiar with. |
Yi's Sketches | Analysis |
|---|
 Image Added
| This is a design for the sign up page. The top screen is the home page, with a button to sign up at the center. In the right corner is the login button for returning users. When a user clicks on signup button, A popup screen will appear (bottom sketch) and it will have an option to sign up using facebook or making an account separately. |  Image Added
| This page has 2 of my designs. The top two sketches represent an interface to ask wedding party, family, etc for input. The sketch in the top left corner is a textbox with a editing bar at the top. After the user write her/his message, he will click on submit, which will lead to the sketch on the top right corner. He/she can choose the contacts to send the message to and click on send. The message will then to sent to the contact's email or facebook depending on previous preference.
The bottom sketch is an ultra-efficient timeline design. The first node is start of planning date and the last node represents the wedding date. To add an event to the timeline, the user simply clicks on the line and a box will be created. He/she can then type the details of that event into the box. |
Team StoryboardsStoryboard I Image Added  Image Added
Analysis: Learnability - Relies on the calendar metaphor, which typical users are familiar with. The interface has external consistency with popular existing applications, such as Google Calendar or iCal. For example, users can view events by hovering over a date.
- Uses menus and forms, as well as direct manipulation. This increases learnability because the interface relies on knowledge in the world, as opposed to knowledge in the head.
- Notifications are shown upon log-in, so they are less likely to be missed.
Safety - Users can drag and drop certain events on the calendar. This allows them to alter event deadlines that they previously approved at any stage of the planning process.
- Users can delete or edit tasks, and send notifications of these changes to wedding guests.
Efficiency - Checkform enables users to choose multiple events to include in their timeline (i.e, bridal shower, bachelor party, etc), rather than add each event on a new page.
- Users can see multiple months at once, instead of seeing only individual months or days. This allows them to make changes quickly in multiple months (i.e., dragging and dropping multiple event deadlines in different months)
Storyboard II Image Added  Image Added
Analysis: Learnability - Uses the menus and forms and direct manipulation interaction styles. Reliance on knowledge in the world and constant feedback increase learnability.
- External consistency with common color connotations (red = incomplete, green = complete) make it easy to tell which tasks are complete and how much of the full timeline is done.
- Users can see comment notifications directly on the timeline, so it’s immediately obvious which timeline items are generating the most discussion.
Safety - Tasks and events can be reorganized and edited throughout the process, even after being confirmed. Changes are reversible and thus the interface is safer overall.
- Other users can see what the primary planner has done and comment on items even if feedback hasn’t been explicitly requested. They serve as safety nets during the entire process.
Efficiency: - The “custom build” screen lets users quickly populate the timeline in bulk even though details may not be fully set in stone.
- Tasks are scheduled based on a sample timeline and shortlisted suggestions are given for each choice, expediting the wedding planning process by doing the preliminary legwork.
Storyboard III Image Added  Image Added*
Analysis: Learnability: - Utilizes a set of timelines (progress bars) that relies on knowledge in the world to master. Getting input from other user classes and sending out final decisions are both done through email, which is integrated into the site.
Safety: - All events and tasks on the timelines can be dragged and dropped to the correct place. Users can also delete and retrieve old timelines and tasks as different aspects of the planning process change. However, the safety of getting feedback and delivering decisions is lower because of the ease of error when emailing.
Efficiency: - Timelines are stacked so the user can choose to focus on the overall timeline that aggregates all tasks, or a sub timeline that helps them visualize all the deadlines and milestones of a specific aspect of the wedding (guests and invitations, catering, etc).
- Each timeline also features a task management system to quickly add actionables to a timeline that may not have a deadline.
- Using email and private links to relay information between the wedding planner and the relevant parties is efficient because every user already has an email
|
|
