tisdag 3 februari 2015


To ease up the work with making a good foundation to our project is there 5 key points from the literature that will help us with the interviews. 

1) Goal – to have a clear goal with the interview and why we are really asking these questions.  
2) Population – Who are we interviewing? We can choose people by random or go after a specific pattern. 
3) Relations with the interviewer and the people that are being interviewed – To keep a professional relation is important. It’s also important with an approval from the people that are being interviewed. And at last to inform what the interview will be used for. 
4) Triangulation – To investigate problems from different angels. 
5) Pilot study – Try our interview questions before we use them. Is it really going to work? This will save us lots of time.
There is also different kind of interviews we can use. A structured, Open Semi structured or open questions.

What requirements for this given design task should we have?

The key activities we can lean back on and repeat from the literature is
1) Establishing requirements. 
2) Designing alternatives. 
3) Prototyping 
4) Evaluating.
Even if we won't have that much time to repeat these steps over and over again do I feel like these steps could really help to make a product “perfect” I think it’s good to have an open mind about the initial requirements at point 1 here and not get stuck on some idea that can’t be changed.  I think these theoretical steps will help us in our user studies, instead of just going out and watching people at a museum we have specific points to go on and we could establish some kind of ground to work on when we kept developing our product.
I think the key requirements for a given design task should be:

1) Effectiveness – easy to use, do what it’s supposed to do. 
2) Safety- safe to use. 
3) Utility – satisfaction, you get some kind of feeling when you use it. 
4) Memorability – easy to remember how to use. 
5) Learnability – easy to learn how to use. 

I also think that the product should give back adequate feedback to the user instead of just printing out an “Error – wrong” or “No” or something like that. Another thing that goes hand in hand with effectiveness is that features should be visible. They talk about visible in the literature, the more functions that are visible it’s more likely that the user will really use your awesome features, this way the user will get what he paid for and really get the whole experience of your product. Another good requirement is the consistency in a design. I didn’t think of this but the literature did, but it really hit me how incredible annoying it is when you use something and the interface isn’t the same for each menu or some button moves around for each step you advance into the application. Another thing is a profound investigation on the current market, what existing technologies are already out there, copyrights etc. I have no mentioned a row of requirements that should be in a design task. In a real design, will there be lots of different professionals involved so the process won’t be the same for everyone. But some key features the literature points out is the and summarize all above:
1) understand the requirements 
2) produce a design that satisfies those requirements 
3) evaluate the design. 

If everyone in the team knows about this we have a stable ground to develop on.

An interesting questions to discuss under the reading seminary is:   
 How can we use triangulation in the best possible way? I mean how can we really step outside the box and look at the problem with a totally new angel.