Tuesday, September 13, 2011

Perceived needs vs observed needs

To each and every project, design teams have it's own perceived notions. These tend to bias us towards what we make, and learning more about the users allows the team to temper their personal beliefs and find sympathy for the user's needs.

For the final part of the Exercise 2, you will document your research by:
  1. Capturing the clusters as a image/photo 
  2. Label the discovered topics generated from the clusters and lable them on the image 
  3. Write 3-5 insights/discoveries/gained knowledge from your interviews. From the insights gathered, brainstorm possible needs for a product your participants mightt find useful, usable and desirable. 
  4. You will turn this in as a PDF to my email by 2 PM, Sept. 15. This due date is the correct one and the syllabus is incorrect. 
  5. Size of the document is 11x17 (tabloid). 
  6. Remember, this is a designed document. It should have a title page, team names, give it a title. 
Review the example documents under Course Materials. Needs answers the purpose of your product. Everything you use, it addresses some kind of need. Others do it better, some do it worse. Your perceived needs are important but the observed needs generated from research are significant. Design teams can generate interesting ideas but will be similar to other design team's. Ideas generated through research tends to be more unique and sometime more subtle, but will become the differentiator to a user's experience.

No comments:

Post a Comment