Bureaucrats, emailconfirmed
1,221
edits
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
''A Students Guide to Interaction Design'' | ''A Students Guide to Interaction Design'' | ||
Solltest ihr irgendwetas ändern: bitte beachtet, dass eure Beiträge unter Creative Commons Lizenz stehen werden. | |||
If you change something, please note that this work and you edits are licensed under a Creative Commons | |||
Licence: | |||
This work is licenced under Creative Commons Attribution-ShareAlike 3.0 Unported. | This work is licenced under Creative Commons Attribution-ShareAlike 3.0 Unported. | ||
| Line 30: | Line 30: | ||
=Foundations= | =Foundations= | ||
==What do you want to do?== | <!--==What do you want to do?== | ||
Everything starts with an Idea. So does your interaction design project. Before you start you should take a moment (or a few more) to consider what you aim for. Sometimes it is not that difficult: A client or you professor will state in which direction you shall go. | |||
If you are on your own or with a team of students this is more of an issue. So think which issue you want to tackle, which problem you want to solve, what you want to try. | |||
In the coming parts of the book you will see that I often reccomand to write down what you want to do in the next step. This has two reasons: | |||
If you need to write down something in a clear and concise way you will note if there is anything unclear about your goals. It is difficult to build on a unclear vision. And a good way to test this is to write it down. | |||
Having a goal is even more important if you work in a team. If everybody supposes everybody works on kind-of-the-same but actually everybody images something very different it is likely that at some point this will have bad consequences like people being upset because there work was not cosidered as useful or fights about the actual direction of the project that would not be necessary and just cause bad mood or in the worst case the whole project breakes down. --> | |||
==Iterative Design Process== | ==Iterative Design Process== | ||
[[File:IterativeDesign.png|300px|iterative design process]] | [[File:IterativeDesign.png|300px|iterative design process]] | ||
| Line 116: | Line 121: | ||
=Research= | =Research= | ||
The research is the preperation 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. | |||
==Use what is already out there== | ==Use what is already out there== | ||
The easiest (though least exiting) way to get insights is researching for ressources you can use. | |||
If the topic you want to work on is new for you it might be a good start to start with a book. | |||
==User Goals== | ==User Goals== | ||
==Planning Interviews== | ==Planning Interviews== | ||