Bureaucrats, emailconfirmed
1,221
edits
Line 244: | Line 244: | ||
"Designing" in this context means turning your ideas in somehow graspable representations. This is needed for refinement, communication and testing. In these areas the different techniques have different strengths. | "Designing" in this context means turning your ideas in somehow graspable representations. This is needed for refinement, communication and testing. In these areas the different techniques have different strengths. | ||
==...in words== | ==...in words== | ||
Even if this is not seen commonly as "design" you can turn your ideas into words to communicate them or to check if you are clear about what you want to do. This is a technique that is very useful in earlier stages after the first big research on your users and their goals. Guided by what you find out you can write down what you want to provide to meet these goals. | Even if this is not seen commonly as "design" you can turn your ideas into words to communicate them or to check if you are clear about what you want to do. This is a technique that is very useful in earlier stages after the first big research on your users and their goals. Guided by what you find out you can write down what you want to provide to meet these goals. Though one is tempted to start directly with the "real" design (sketches, programming etc.) you should make your mind what the system needs to do. It prevents you to overlook things. | ||
A structured approach of this is defining "Requirements". This is defining the things your product needs to do at the end – in early phases the very essential ones. | A structured approach of this is defining "Requirements". This is defining the things your product needs to do at the end – in early phases the very essential ones. |