Bureaucrats, emailconfirmed
1,221
edits
m
no edit summary
(psyco) |
mNo edit summary |
||
| Line 120: | Line 120: | ||
If you release a successful 1.0 Product you can still extend it in the 2.0 version even with features that are not very-super-crucial. But I write this to help you to release a successful 1.0 version so I did put emphasis on the simplicity. | If you release a successful 1.0 Product you can still extend it in the 2.0 version even with features that are not very-super-crucial. But I write this to help you to release a successful 1.0 version so I did put emphasis on the simplicity. | ||
=Research= | =Research= | ||
The research is the preparation for the actual design process. Doing research will help you to design for what the users want to archive and to avoid common problems. It is also likely that some other people did work you can build on. This can save you a lot of time and pondering. | The research is the preparation for the actual design process. Doing research will help you to design for what the users want to archive and to avoid common problems. It is also likely that some other people did work you can build on. This can save you a lot of time and pondering. | ||
| Line 320: | Line 320: | ||
==Improving your Product== | ==Improving your Product== | ||
Having a list with what causes the user problems you know can refine your work. In early satges you will have seen which of some different ways will be dismissed and which will be further explored. | Having a list with what causes the user problems you know can refine your work. In early satges you will have seen which of some different ways will be dismissed and which will be further explored. | ||
In later phases of your project you will have a list with ranked problems that need to be resolved. Start with the ones you consider the most serious and solve the problems. In doing so you often can build on the think-aloud-protocol you wrote. It give insight in the way the users think about the actions they took and about the responses of the software. This will help you to find a decent solution that will work better. | In later phases of your project you will have a list with ranked problems that need to be resolved. Start with the ones you consider the most serious and solve the problems. In doing so you often can build on the think-aloud-protocol you wrote. It give insight in the way the users think about the actions they took and about the responses of the software. This will help you to find a decent solution that will work better. | ||
- | [[Category:Design]] | ||
[[Category:Courses]] | |||
[[Category:Student]] | |||
[[Category:Jan Dittrich]] | |||
[[Category:Jens Geelhaar]] | |||
[[Category:Interaktion]] | |||
[[Category:Interface-Design]] | |||
[[Category:Design]] | [[Category:Design]] | ||