Milestone 5: Scenarios

Review of Milestone 4

For the last milestone, we received many inputs both in class and from our client.  We regard these critiques as very important reminders as we move on to our Hi-Fi prototype. Besides, our client Jakob Hilden got back from Gallery Developers' Meeting, and brought us valuable feedback as well as suggestions on Hi-Fi.

Altogether, the inputs are the following:
- option to remove slidebar items or add more
- delete individual photos
- batch delete a bunch of photos
- in place editing for title/description
- rotate photo
- reordering per drag and drop
- batch editing of fields that make sense to be batch edited

The critiques are really beneficial for Phototic, since we may miss some basic functions like deleting single photos or rotating them as we concentrate on more complex interactions.

Getting started with Scenarios

Among the many ways to create scenarios, we chose persona- based scenario methodology instead of use cases. Because we don’t want to treat all possible user interactions with equal likelihood and importance. We think a goal-directed scenario will best suit our project, prioritizing certain functions that specific users interact with.

According to About Face 3, we go through five steps to complete our scenarios:
1. Creating problem and vision statements
2. Brainstorming
3. Identifying persona expectations (goals)
4. Constructing context scenarios
5. Identifying requirements

First, we create problem statement to redefine the purpose of the design initiative.

Then we start to brainstorm. We had a discussion about whether we ended a scenario in a way that didn’t satisfy the persona. After a thorough consideration, we decided not to use a dysfunctional scenario because it only shows that the new design is not good still. We will want to know this through user testing and make improvement on it, not in a scenario.

The third step is to identify persona expectations. Since we have clear goals of each persona, we try to satisfy these goals in the corresponding scenario. We make storyboards to help construct the context scenario. 

Finally, we go over the user requirements again to identify whether some are left out.

Persona-based Scenarios

Now it's time to recall our four personas! Remeber Beth, an IT specialist working for a non-profit organization; Alan, a senior software engineer; Liong, an international graduate student; and Seice, a market dealer and civil engineer?

We'll walk you through their stories with Gallery.



 

Beth Johnson

IT Specialist

Scenario-1: A Nice Start





Alan Anderson

Senior Software Engineer

Scenario-2: Alan's New Experience




 

Liong Jiang

International Graduate Student

Scenario-3: Liong's First Impression





Seice Penn

Market Dealer, Civil Engineer

Scenario-4: Seice's Serendipity




© PhototiC, 2008-2010