Bureaucrats, emailconfirmed
1,221
edits
→Get to know if your ideas work!
| Line 469: | Line 469: | ||
* Write down typical tasks one can resolve using your product. This is a little brainstorming. | * Write down typical tasks one can resolve using your product. This is a little brainstorming. | ||
* Out of the tasks you wrote down you choose the ones that you feel are typical for your software and crucial for using it. If you have someone at hand who is firm in the subject your users are working in you can ask for a countercheck on realism. | * Out of the tasks you wrote down you choose the ones that you feel are typical for your software and crucial for using it. If you have someone at hand who is firm in the subject your users are working in you can ask for a countercheck on realism. | ||
===Write the tasks=== | ===Write the tasks=== | ||
The tasks you have now determined need to be written down in a way that makes clear what the you want the user to do. | |||
* You need to think about a suitable context for your tasks. So don't just write: "import the pictures from the SD card into the Program" but something like "You are a Photographer and just finished shooting. Please import the pictures into the program for doing further work with them" | * You need to think about a suitable context for your tasks. So don't just write: "import the pictures from the SD card into the Program" but something like "You are a Photographer and just finished shooting. Please import the pictures into the program for doing further work with them" | ||
* It needs to be clear when a task is finished. So don't write any open ended tasks but one that have a clear goal and condition one needs to reach. <br> E.g. the example above could be improved by changing the end to "Please import the pictures into the program, so that you can see the images thumbnails in the program" | * It needs to be clear when a task is finished. So don't write any open ended tasks but one that have a clear goal and condition one needs to reach. <br> E.g. the example above could be improved by changing the end to "Please import the pictures into the program, so that you can see the images thumbnails in the program" | ||
| Line 476: | Line 478: | ||
===Build a Paper-Prototype=== | ===Build a Paper-Prototype=== | ||
[[File:PaperPrototyping_Zeug.jpg|right|200px|thumb|A paper prototype consists of Paper or Cardboard pieces and a few additional materials]] | [[File:PaperPrototyping_Zeug.jpg|right|200px|thumb|A paper prototype consists of Paper or Cardboard pieces and a few additional materials]] | ||
Now as you | Now as you now what you want to test and how you make this clear to the user, you can build your prototype. It needs to simulate the situations that can occur when the participants do the task you gave them. So at least you need to cover the possibilities to resolve the task and some sideways that don't lead to the task's solution. Otherwise the Participant will try to interact and your prototype will not be up to responding and "crashes". | ||
I reccommand to build your prototype in paper. It may sound strange but it is easily done, costs almost nothing and usually has good results. The basic principle is to mock up the Interface using paper and some other stuff thats probably in your office. | I reccommand to build your prototype in paper. It may sound strange but it is easily done, costs almost nothing and usually has good results. The basic principle is to mock up the Interface using paper and some other stuff thats probably in your office. | ||