Bureaucrats, emailconfirmed
1,221
edits
→Testing Assumptions
| Line 37: | Line 37: | ||
The Design of digital product is very complex and it is hard to guess how people will understand and use your creations. So it is essentail to see what people need and behave and if your solutions are understood and used by the as you intended. So we will go to the source of interaction, the (potential) users and see if our assumptions are right. | The Design of digital product is very complex and it is hard to guess how people will understand and use your creations. So it is essentail to see what people need and behave and if your solutions are understood and used by the as you intended. So we will go to the source of interaction, the (potential) users and see if our assumptions are right. | ||
Before we have a design we will observe the user, find out about motivations and the context the interaction happens in. After we have a design we test this with the users. | Before we have a design we will observe the user, find out about motivations and the context the interaction happens in. After we have a design we test this with the users. | ||
This means we will check theories similar to a scientist and base our solutions on real observations. I will provide you methods that enable you to check your intuitive assumptions and lead to new insight and inspiration. | This means we will check theories similar to a scientist and base our solutions on real observations. I will provide you methods that enable you to check your intuitive assumptions and lead to new insight and inspiration. Testing can seem tedious. That feeling is all too common and well known by myself. But testing is essential. Especially if I thought that everything is clear, testing was very helpful: It almost always led to results I did not expect. | ||
===Iteration=== | ===Iteration=== | ||
<!-- | <!-- | ||