Bureaucrats, emailconfirmed
1,221
edits
testing
(testing) |
(testing) |
||
| Line 257: | Line 257: | ||
* If the user really gets stuck you can gradually help. First with something with ''"where do you think could the [whatever] function be?"'' if this not helps in any way you can point to the solution so you can move further: '' "what do you think does this button do?" '' | * If the user really gets stuck you can gradually help. First with something with ''"where do you think could the [whatever] function be?"'' if this not helps in any way you can point to the solution so you can move further: '' "what do you think does this button do?" '' | ||
* If the user forgets about thinking aloud just ask ''"What do you think at the moment" '' | * If the user forgets about thinking aloud just ask ''"What do you think at the moment" '' | ||
==Formulate your findings== | |||
After the tesign you will have a bunch of protocols. You review them to see how you can improve your product. So have a look where people got stuck or where they thought about a feature, menu entry et. differently than you expected. | |||
If you are in an early phase of your project you probably need to decide about very basic things e.g. if your users understand a new way of approaching a common task. In this case you need to decide which of some solutions you will choose. !!!--> interessante Ergebnisse aufschreiben, häufige Probleme etc. Alles was beim weiteren Design und evtl auch forschung hilft. | |||
Bei späteren stages: improvement. Organisierte Liste schreiben. | |||
It is good to order your findings after priority: Problems that could prevent an essential step from happening are improtatant to resolve.(e.g. importing a picture into a photo-organizing application or changing the channel on a TV) Watch out for patterns – some problems will occur over and over again and should have as well a high priority in resolving them. | |||
==Improving your Product== | ==Improving your Product== | ||
=Epilogue= | =Epilogue= | ||