I have focused on reading the three articles provided.
Out of the three, I found Key principles for user-centered system design the most interesting and useful. The article brings up, as the title suggests, a list of principles to define user-centered system design (UCSD), but also descriptions of some problems the people behind the article ran into during their project and suggestions on how to apply UCSD.
Emphasis is put on the importance of involving users in the design process. This also introduces the need of easy-to-understand design representations and terminology — the future users who are involved in the design process should have no problem understanding the project. As we are going to be doing interviews with the target group of our product it might be a good idea to consider this, even though our projects may not be as complicated as the one in the article.
The usage of an activity list is suggested as a means of introducing each key principle into the project, and includes specific methods on how to achieve this. This can be used as a checklist throughout the project. I believe using an activity list could help us structure out project as well.
The list of the problems encountered might not entirely apply to our project, as we won’t be working in the same way and most likely won’t even have a finished product in the end, but I still think it is worth taking into consideration, if only to have something to reflect on.
Ouestion: How can we involve our users in an effective way?
Inga kommentarer:
Skicka en kommentar