Bureaucrats, emailconfirmed
1,221
edits
→Interviews
| Line 191: | Line 191: | ||
The first steps are the most difficult but once the interviewee talks it usually runs smooth.So it is a good idea to start with some questions that are useful for you to know and have clear and simple answers like the profession, years of experience etc. | The first steps are the most difficult but once the interviewee talks it usually runs smooth.So it is a good idea to start with some questions that are useful for you to know and have clear and simple answers like the profession, years of experience etc. | ||
With the interview '''we want to find out about the user's goals, motivations and current problems'''. A good way to do that is asking open questions and not direct ones. So the answers you should aiming for are not "yes" or "no" but e.g. the ones the user can tell you experiences or explains you something. Often it will be useful to follow up something the user said. Asking why a decision was made in a specific way or how something works can reveal important facts. | |||
By asking open questions you '''don't make the user a designer'''. Users are very bad in telling what is good for them and what is bad. In this case you better do a test with a prototype. | |||
Here are some open Questions as an example | Here are some open Questions as an example | ||
| Line 197: | Line 199: | ||
* What was the best day at work in the last weeks? (Follow up with "why?") | * What was the best day at work in the last weeks? (Follow up with "why?") | ||
* What annoys you when you work on this? | * What annoys you when you work on this? | ||
When you do interviews there are some common problems that can occur. | When you do interviews there are some common problems that can occur. | ||
| Line 203: | Line 206: | ||
#'''The Interviewee answers in very abstract ways'''<br>Interviewee answer: '''"In general these things make me think about..."''' <br>The answer does not tell us something interesting about the real life of the user. <br>Solution:''"Can you tell me about the situation it happened the last time?"''<br><br> | #'''The Interviewee answers in very abstract ways'''<br>Interviewee answer: '''"In general these things make me think about..."''' <br>The answer does not tell us something interesting about the real life of the user. <br>Solution:''"Can you tell me about the situation it happened the last time?"''<br><br> | ||
#'''The Interviewee demands a specific feature'''<br>Interviewee answer: '''"Well... You just need to put a red button here!"''' <br>Users don't know what would make a design that is good to use for everybody. We don't know either for sure, so we do research!<br>Solution:''"How would the red button help you?"''<br><br> | #'''The Interviewee demands a specific feature'''<br>Interviewee answer: '''"Well... You just need to put a red button here!"''' <br>Users don't know what would make a design that is good to use for everybody. We don't know either for sure, so we do research!<br>Solution:''"How would the red button help you?"''<br><br> | ||
#'''You want to know if | #'''You want to know if something you have in mind would help the user'''<br>You: '''"Would it help you to have a green lever that does [whatsoever]?"'''<br>Here you make the user a designer. This is similar to the situation above. <br>Solution:Don't ask this question! In a latter section you will read about testing and prototyping such ideas. If you want to gather information on the specific feature in the interview nevertheless: gather informations about the user and his/her context that could reveal if the user needs the feature that you have in mind. | ||
During the interview you '''take notes or record the audio''' (Ask for permission if you do the latter) So you will be able to review the interviews. | During the interview you '''take notes or record the audio''' (Ask for permission if you do the latter) So you will be able to review the interviews. | ||
Take some time to do the review and gather all you notes or recordings. Read or listen through them. Remember, | Take some time to do the review and gather all you notes or recordings. Read or listen through them. Remember, we 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 to participate is to improve their CVs and to get known.'' | 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.'' | ||