Bureaucrats, emailconfirmed
1,221
edits
testing, design
(testing) |
(testing, design) |
||
| Line 182: | Line 182: | ||
Take some time to do the review and gather all you notes or recordings. Read or listen through them. Remember, whe want to find out about user goals and existing problems. Write what you consider as important down. Now you should get an overview by grouping the findings. Some will occur more often or add up to a kind of problem field. | Take some time to do the review and gather all you notes or recordings. Read or listen through them. Remember, whe want to find out about user goals and existing problems. Write what you consider as important down. Now you should get an overview by grouping the findings. Some will occur more often or add up to a kind of problem field. | ||
After doing so you should try to put your key findings in a few short sentences. An example is: ''"The goals of our potential users | After doing so you should try to put your key findings in a few short sentences. An example is: ''"The goals of our potential users to participate is to improve their CVs and to get known.'' | ||
Write down common problems as well so you know which traps to avoid and where new solutions are needed. | Write down common problems as well so you know which traps to avoid and where new solutions are needed. | ||
| Line 188: | Line 188: | ||
=Designing= | =Designing= | ||
"Designing" in this context means turning your ideas in somehow graspable represenations. This is needed for communitcation, presentation and testing. In these areas the different techniques have different strenghts. | |||
==...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 dow what you want to provide to meet these goals. | |||
A stuctured aproach 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. | |||
==Sketches== | ==Sketches== | ||
for keeping ideas and communicating in the team. | for keeping ideas and communicating in the team. | ||