Bureaucrats, emailconfirmed
1,221
edits
no edit summary
No edit summary |
No edit summary |
||
| Line 35: | Line 35: | ||
* Communicate in a team | * Communicate in a team | ||
--> | --> | ||
Designing interactive products is complicated. And we as designers err sometimes or need experiment with different solutions and we'll hopefully some insights at different stages of the design. E.g. we could see that we need to find out something about the context the interaction happens in while we already test our design. Are we screwed than? no. | Designing interactive products is complicated. And we as designers err sometimes or need experiment with different solutions and we'll hopefully some insights at different stages of the design. E.g. we could see that we need to find out something about the context the interaction happens in while we already test our design. Are we screwed than? no, since we will design in iterations. | ||
[[File:IterativeDesign.png|300px|iterative design process]] | [[File:IterativeDesign.png|300px|iterative design process]] | ||
What | What does that mean? You don't do exploration-design-testing only once but you go through it several times, improving your design further and further by working on it from different perspectives and checking with reality. Over each iteration your design will become more concrete. At the beginning you test basic and broad assumptions and ideas (like "who are your users?"), at the end specific ones ("will users understand this icon?") | ||
The iterative process helps as well to be more creative as well. As you go though a circle of steps you can experiment and err without spoiling the project and always build on your previous experiences. By dealing with your users, you will see your designs from a new perspective and so develop new ideas. | |||
When you design minor features, you don't need to do all steps each time you try to solve a problem. It is very common to design, test and refine the design based on the test's results to test again. | When you design minor features, you don't need to do all steps each time you try to solve a problem. It is very common to design, test and refine the design based on the test's results to test again. | ||
| Line 55: | Line 57: | ||
So what is all that good for? Following the steps helps you to understand your users by doing research. So you don't design for non-existing needs or interfaces nobody can use. | So what is all that good for? Following the steps helps you to understand your users by doing research. So you don't design for non-existing needs or interfaces nobody can use. | ||
'''A small Example:''' | '''A small Example:''' | ||
Imagine you design a new mobile phone. You can use the process that is suggested here to design the general product: You will research how people will use the phone, you will determine which features you need for meeting the users needs. Than you will design how all features work together in the phone and how it will look like. At the end you test it. | Imagine you design a new mobile phone. You can use the process that is suggested here to design the general product: You will research how people will use the phone, you will determine which features you need for meeting the users needs. Than you will design how all features work together in the phone and how it will look like. At the end you test it. | ||
| Line 70: | Line 72: | ||
What you do now is trying out different ways to make the type-selection easier, so you just repeat the "mini-cycle" of testing and design. | What you do now is trying out different ways to make the type-selection easier, so you just repeat the "mini-cycle" of testing and design. | ||
During the design process you will refine what you want to do. This will be especially after you did some exploration or testing. One advice I consider as important: Write down your idea, your findings and aims. This will help you to be clear about what you need to do next. If you designs together you will hardly succeed without this: You need to communicate clearly and have a common idea of what you want to do. | During the design process you will refine what you want to do. This will be especially after you did some exploration or testing. One advice I consider as important: Write down your idea, your findings and aims. This will help you to be clear about what you need to do next. If you designs together you will hardly succeed without this: You need to communicate clearly and have a common idea of what you want to do.--> | ||
===Structure=== | ===Structure=== | ||
This course aims for covering the whole design process. This means you will learn | This course aims for covering the whole design process. This means you will learn | ||