Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Observations & Interviews

1. The Architect

  • An architecture student doing graduate-level training for professional architecture work

...

  • Wants review audiences to have limited visibility of each other (e.g professors shouldn't be able to see what her friends think of her art)

2. The Filmmaker 

  • A technical artist at an Academy Award-winning special effects studio.

...

  • Really enjoyed contextual feedback (i.e. "oh this is a lot like <some other film maker>")** Especially helpful when such comparisons inspired collaboration.** Would have liked a forum in which people could post videos of related work.

3. The Digital Artist

  • Background in painting 

...

  • Efficient feedback
    • Artists don't want to spend a lot of time getting feedback (e.g. at gallery critiques)
    • Artists would like to get feedback online
    • Artists would like to get feedback frequently
  • Constructive feedback
    • Commenters should be able to include references (e.g. this work reminds me of..., try to make this work more like...)
    • Commenters should be able to provide graphical examples (e.g. sketches) and annotations (similar to pen/paper or sticky notes in traditional critique sessions)
  • Variety of feedback
    • Artists would like to reach a wide variety of commenters (e.g. friends, professors, professionals)
    • Artists may be interested in collaborating with others
  • Organized feedback
    • Artists would like to organize feedback by type (e.g. emotional, like/dislike, technical)
    • Artists would like to set privacy/viewing settings between groups (e.g. professors should not be able to see comments from artist's friends)

Task Analysis

Task 1: 

  • Why is the task being done?
  • Where is the task performed?
  • What is the environment like?
  • What are the time or resource constraints?
  • Who else is involved in the task?
  • What does the user need to know or have before doing the task?
  • How often is the task performed?
  • How is the task learned?
  • What can go wrong?

Task 2: 

  • Why is the task being done?
  • Where is the task performed?
  • What is the environment like?
  • What are the time or resource constraints?
  • Who else is involved in the task?
  • What does the user need to know or have before doing the task?
  • How often is the task performed?
  • How is the task learned?
  • What can go wrong?