Social Web 2.0 course notes:

• Identity Key User Scenario
  • Describes user sequence for a particular user, but not specific features.
  • Example for group mobile messaging system with photo sharing:
  • Jane is having an impromptu dinner party on a Friday night. She creates a dynamic communication group “Jane’s Dinner Party” of her friends with her mobile phone, and invites them. The group of friends she invites for the dinner party use the communication group to organize rides prior to the dinner, and to share photos after the dinner. One of her guests brings a friend. Jane easily adds the friend to the communication group at the dinner party. Several people take pictures on their camera phones and share them with the group. Two weeks later, one of the people at the Jane’s dinner party is organizing a new year’s party. He wants to make a new group with most, but not all, of the original group, as well as additional people. He quickly makes a group using Jane’s dinner party list, and then adds and removes a few people.
• Traditional Story Board
  • Sequence of scenes
• Story Board for Web Site
  • Sequence
  • Interaction capabilities means more flow charts 
• Storyboarding tips
  • Use key user scenario to assure have primary pages in story board
  • Start with sticky notes on white board, then take picture and convert
  • Think through sequence of events, arrows appropriately
  • Minimal clicks possible
  • Always clear to user where to go next in sequence – don’t overpower with a million options, 1 to 3
  • Visio? Photoshop
• Wireframes
  • Line drawings of user interface
  • Key pages in user scenario
  • Focus is on interaction design, not on making too pretty
  • Start with sketches
  • Then do in visio/photoshop
    • Tendency to “overload” pages
    • Important to see if feasible to fit it all on one page
• Raw sketches