I did this graphic as a basis to talk with my supervisors about how I intend to go about my research. I am not sure I can cover all of these areas, but at this point it seems the most logical approach.
Basically I propose to start with a literature review to see previous work that has been done in this area. Then I will conduct a survey or interviews of architects to get a sense of the need for this work, and the best way I can help. Then I will conduct small lab experiments where I test out some of the User-Centered design methods I have identified. After these tests I will make a connection with one or two architecture offices that I can collaborate with and custom implement some of the methods. After the research I will do another survey or interview to see if the new methods are helpful.
Click on the above image for a pretty sweet little slide show on how to do a "cognitive walkthrough" (if I do say so myself)...This graphic may not be clear on its own, but once its explained in the slideshow I think it will all make sense.
The cognitive walkthrough is a usability test that you can do without having to bring in outside participants to test it on. It is a good way for the design team to state their assumptions about the users and test the design throughout the process.
Basically, the blue is the "Preparatory Stage" where you define your users, Try to explicitly state your assumptions about how they behave and their motives. You then think about what they would do with your design and outline specific tasks that they need to accomplish for them to reach their goal. An example in architecture might be:
The cognitive walkthrough is a usability test that you can do without having to bring in outside participants to test it on. It is a good way for the design team to state their assumptions about the users and test the design throughout the process.
Basically, the blue is the "Preparatory Stage" where you define your users, Try to explicitly state your assumptions about how they behave and their motives. You then think about what they would do with your design and outline specific tasks that they need to accomplish for them to reach their goal. An example in architecture might be:
1)User - 80 year old woman who likes to attend weekly bridge game
-What are her motives?
-What are her physical abilities/challenges?
-What will she want/need to do?
2)Tasks - What are the basic tasks she needs to accomplish?
-park her car
-find the front door
-walk to the front door
-hang up her coat
-find the bridge room
-find the tea and cookies
-find and use the washroom
-etc
The orange is the "Analysis Stage" where, the design team goes through the task list and figures out whether it is reasonable that the user can accomplish each task. You can ask these 4 basic questions:
1)Will the users try to achieve the right effect?
2)Will the user notice that the correct action is available?
3)Will the user associate the correct action with the effect trying to be achieved?
4)If the correct action is performed will the user see the progress is being made towards solution of the task
You can record the results on flipcharts or on tables. The information should give you a clear idea where users might have challenges and where further design should be done. It also gets the design team to think in terms of the end user early in the design process.
No comments:
Post a Comment