Instructions: Given the following two scenarios, create a rapid prototype interface (I recommend storyboard sketches) that would support the user goals from each scenario and bring both interface ideas to class (submission counts for individual credit).

• In your groups on Tuesday, select the best prototype for each scenario.
• Then, fill out the chart (transparency copy will be provided in class) with claims for supporting the user goals with respect to the interface components and the information design aspects listed. For example: “use of animation” = tickering text, “font attributes” = bold red letters, “color and pattern” = high contrast, muted colors, “layout” = strong category emphasis, “use of audio” = beep, “semantic representation” = using icons or words, level of detail/summary.
• Finally, highlight the three claims for each interface that you feel are most important to verify with user testing.

Scenario A. Sheryl often works with Ted for several days at a time on producing project reports for their design team leader. They both use a shared editor on their desktop machines. Knowing what section of the document the other is working in is important for avoiding overwriting one’s changes and duplicating work. Gaining this knowledge should not require interaction with a separate window or other interface controls; it should be readily available from the current work area. Performing some other task in response to someone’s actions is not part of their work goals.

Scenario B. Chuck is a businessman who frequently writes documents at his office computer but must also attend regularly scheduled meetings and respond to important emails, thus he relies on calendar and email alerts. Redirecting activity to the right place, at the right time is the only important consideration. Recalling details of his appointments or emails is not an important factor for him. If Chuck misses being informed when appointments draw near and when urgent emails come in, he may lose his job.