Showing posts with label Seminar 1 notes. Show all posts
Showing posts with label Seminar 1 notes. Show all posts

Thursday, September 18, 2014

Reading notes for Seminar 1 - Thomas Ziegelbecker

At the end of chapter 2, which describes the principles and differences of the 4 approaches to interaction design, I concluded that using User Centered Design (UCD) is the best approach to address the task at hand. The user base is narrow and the requirements are very vague. I also think that we will use elements of Genius Design (at the beginning - eventually already mocking up stuff for interviews) at some point as most of us have already experience or touched on with HCI.
I believe that Systems Design and Activity Centered Design will not play a major role in our case. As we are going do not address the masses but a particular target group.

We are certainly going to use recommendations made in chapter 4,  which is about qualitative research / Design Research - (act of investigating a product's or service's potential or existing users and the context of use) and how to prevent product lunches where it does not meet the users needs. Things that we we probably also use are:
  • research hunt statement
  • creat a screener - set of initial question to check the fit!
  • Have a moderator script - what and in which order (incl. instruction for the interviewer)
  • Keep in mind the 3 rules of DR (you go to them, you talk to them, write stuff down)
  • Parts of the 3 Categories of conducting such research: Observations (fly on the wall, shadowing, ...), Interviews (Directed storytelling, unfocus group, role playing...), Activities
In Chapter 5 there are ways of how to structure research findings that tells you to look for patterns and unique phenomenon (unusual behaviour). For me i abstracted the following steps, through which we will go through in our project.
  • Prepare Data (Make data physical, to be able to draw connections)
  • Manipulate data (cluster, combine, juxtaposing related..) 
  • Analyzing the data (analyze - e.g. alignment lists, explore - make a new whole, abstract - reduce noise). 
At the end this should lead us to a Conceptual model, which includes boundary objects, pain points, opportunities, etc., and then presented graphically (linear flow, spider, sets, venn, matrix..). Another important way to present our user group and the finding at the end is to use Personas (common set of behaviour, expectations and motivations).

Key Principles for user-centred systems design - describes an in-house software dev. project (based on RUP, with action research), lists problems, which occurred and derives 12 key principles. At the end they compare agile methods to UCSD and conclude that both can complement each other, as agile methods can compensate the missing lifcycle/longterm view of UCSD.

ISO-9241-11: gives ideas of how to define usability with a framework with measures such as effectiveness, efficiency and satisfaction as outcomes. this involves description of goals, users, tasks, equipment, environments. It gives ideas of how to interpret those measures, as well as how to evaluate and specify during design. E.g with Usability Activities and Documents/Outputs

ISO-9241-210: gives normative descriptions of terms used in Human-Centred Design (HCD), as well as the rationale why to use it. It lists for instance activities and outputs of HCD and explains how it improves quality and reduces risks, as well as it underlines the importance of an explicit understanding of users, tasks and environments.

Question: When should we use which research method or methods to structure our research findings in relation to our project?.

Reading notes for Seminar 1 - Alex Hoffmann

After going through the provided chapters an articles i found the following useful for the design task at hand.
In the beginning of the project we should keep our view broad and keep almost every possibility open. Since we do not have a lot of experience we will probably need several tries to get from our first idea to a proper product. It will take a lot of reconsideration and changes to get to a point where we can say that our product is presentable.
We should definitely choose the user centered approach to the problem because the project is in a field where we have no experience and we are beginners at designing as well, because of that the systems and activity centered design should not be chosen. To use the UCD we will apply the tree rules (go to them, talk to them, write stuff down). The interviews with the people in the museum have to be well prepared because the whole project will rely on the conclusions we draw from that. so we will prepare a interview script and try to get an hunt statement out of the interview. But at the same time we should not loose too much time in the first pile of data because our process will take several iterations to get to a decent result.
After the examination of the interview data we have to specify the product as soon as possible and start producing the first drafts to evaluate ideas. The team will generate a lot of different ideas because of our strongly different backgrounds so we have to rely on the insights from the interviews to pick the right way.
Since we dont know what product we will design or even the direction we might take yet, it is impossible to tell how our way after we created the personas of the persons we detected as our target group. But we have to keep the users integrated in the process so we might have to take a second round of interviews once we developed the first ideas for evaluation.
The ISO norms 9241-11 and 9241-210 propose a way to measure the efficiency of a interface to compare it and measure its outputs. As well as the normative declarations of User-centered-Design and the way how to use UCD. We can use those declarations on our later way in the project to evaluate results of iterations and decide what way to choose.

A difficult consideration is how much time and how many iterations should we spend in this early phase on the users?

Reading notes for Seminar 1 - Johan Lindeberg

While reading through the assigned chapters in our course book I had the recurring thoughts "Well that's obvious" or "This is just common sense". A few examples would be
  • To not overly complicate things, 
  • Take input and point of view from clients, stakeholders colleagues, teammates etc.
  • That the brief should be just a starting point.
  • Genius design is best practiced by experienced designers.
  • That you can only hold so much information in your memory (The Magical Number Seven).
  • Placing a button at the edge of the screen makes it easier to click (Fitts' Law).
  • Putting constraints on products to prevent errors (Poka-Yoke).
These statments all seem rather intuitive to me. However, as I think back of how I've approached problems in the past (working with developing webpages and tools for Swedish middle school students studying spanish), these points is not something I have focused on. Instead I've mostly listned to my boss telling me that he wants this functionallity, and then just implementing it without giving too much thought towards the end user. This is something I will try to put more focus on in my work as well as during this course, and it's well summarized in a quote from the Summary of chapter 3: "..we should never forget who these products and services are for: the users". 


As for our project, and the upcoming interviews, some things we should keep in mind is:
  • Let the interviewee know who we are, what we are doing and why
  • Be well prepared (recording equipment, pens, paper, what we are going to ask)
  • Letting the interviewee speak for herself (Awkward pauses can be a good thing!)
  • Asking "Why?"
After we have conducted the interviews, we will have to brainstorm ideas. Some good points to keep in mind is to start off with a warm-up exercise to get engaged before generating ideas, to brainstorm for not more than two hours, to not spend a lot of time on one idea - rather generate as many ideas as possible and to use the space you have available (sketching or writing down ideas on paper, placing them on the walls or tables so you can see them.

Walking even further down the road of our project, we arrive at prototyping, and a valuable point brought up in the article Key principles for user-centred systems design is that - just as for brainstorming - using a lot of quick sketches and mockups is a great way to support the creative process. Also that producing many prototypes in parallel lets you keep a creative mindset.

Question: As we have no real brief (or a very vague one) for this project, how will we define our product? 

Reading notes for Seminar 1 - Jessie Pease

After reading about the different approaches to interaction design, it seems that for our project with the museums, it might be best to use user-centered design or activity-centered design. The genius design approach is definitely too advanced for our level of knowledge. UCD gives good structure for the problem we are trying to solve at museums. 

Throughout our design process, we will do research in which we will interview and observe our users, analyze the results, make conclusions about user’s needs, brainstorm possible design solutions, define and set goals for design, build the design, test design with users, refine design (complete that process multiple times), and finally have a working prototype or solution. Throughout the design process, it is helpful to have a “hunt statement.” For our group, Swedish Blondies, it might be something like, “We are going to research how children interact with exhibits at the Natural History Museum of Stockholm so that we can help improve their interaction experience.”

Throughout our research it would be helpful to follow some guidelines suggested by the reading. Some good guidelines were:
  • Be overly prepared for interviews (with pens, paper, recording equipment, etc)
  • Work in pairs so that we get different perspectives on the same feedback from users
  • Choose a variety of user-subjects to interview that all fall into our sub-group we are researching
  • Ask unbiased questions
  • As “how,” “what,” and “why” questions instead of yes/no questions
  • Do not make subjects do any work; we need to approach them and record their answers
  • Observe potential users in the environment. Observe their interactions with the environment as well as the users as people. 

Once our user observations and interviews are complete, that is when we can start our conclusion making. The best way to do this is to physically organize all of our interviews and observations on a board using post-its and physical notes that we can organize. This makes it much easier to draw conclusions. 

Throughout the entire process we need to remember that we are thinking of ergonomics of design and also doing a human-centered design process. Since we are making a product for users, they should be the center of our research, design, and testing processes. 

After creating a product, we want to measure success by looking at effectiveness, efficiency, and satisfaction of users. Each these categories has different ways of measuring success. I learned how to measure such successes using those categories in the ISO documents. In short, effectiveness is how successful was the user at completing a task. Efficiency is measured in how long it took or how much effort was put into completing a task. Finally, satisfaction is measured by, "the extent to which users are free from discomfort..." (ISO-9241-11).

Questions:
  • Is it appropriate to ask users if they have a design solution themselves while we are interviewing them? 
  • Users will likely have different preferences, so is part of the testing process designing for approval from the masses?

Wednesday, September 17, 2014

Reading notes for seminar 1 - Petter Janse

For the coming seminar we were given the task to read three chapters dealing with; the four major approaches used in interaction design, how to collect data from research and how to process this data into useful information. I felt a lot of the information in the book relate to bigger and more complex projects than the one we will be doing, meaning a lot of the approaches mentioned in the book will be out of scope for our project.

Out of the four approaches two fall out right away. System design is for far more complex projects than our and simply would not fit our project. And since it is mandatory for our project to do user interviews and create a persona this contradict the genius design that doesn't take users into account until a later stage. It does however fit the User-centered design approach, so this will most likely be the main approach used in our project. However, while the book talked a lot about choosing one, or switching between them for different project, I am wondering if you could not combine two, or make a compromise. To me a mix of UCD and ACD seems like a good alternative.

During our first meeting we did some research planning as suggested, deciding that our subgroup (end-user) will be children in the environment of a museum and with the goal of our project to make the visit as amusing for them as it is for the adults. As for collecting data the only mandatory task is user interviews, but it will hardly be sufficient for a successful project. I think while we are at the museum for the interviews there will also be a good opportunity to observation our end-users. What do they do at the museum? Do they seem satisfied as it is?

Since we are working with such a specific subgroup there will be no need for a screening process of the users, apart from maybe define the age range for what we consider children and make sure the once we interview/observe fall into this range. We have also decided to meet the day before going to the museum to prepare a moderator script for the interviews, as well as making sure we are on the same page. Having the five of us making five different interviews with different goals will make the later data processing very hard.

Once we got our interviews and observations this will be the time to process the data by creating a persona and try to find patterns among our users. With only five interviews to base the persona on, and given our small subgroup a single persona should be sufficient. As I mentioned in the beginning I found a lot of the things mentioned in the processing of the data to be aimed at bigger projects with huge amount of data that simply cant be reviewed unless processed. But hopefully we can find some that fits our project.