Cafe Observations

 Collecting Evidence of User XP

Observational Research

Formulate Plan:

Before heading to a cafe our group of 5 put together a list of questions and details we would look for. We wanted to record how many people were there, what they were doing, how long it took to get their products, what they seemed to be enjoying from the environment and what the pain points were.

Collect Data:

Costa Coffee

Quantitative Research

How many workers: 3 
How many people sitting: 15 
How many takeaway: 2 
Outside seating: 4 
Inside seated: 11 
Most people standing in line at one time: 5-6 
Wait time: 2-4 minute 

Gain points 

Fun watching experience as your coffee is made
Calm Environment
Food and Drink Variety
Seat Variation

Qualitative

Limited Accessibility
Crowded Que and waiting area- 
Revolving Menu- frustrating/anxiety
Serving Tray didn't fit the tables
ect. See mural for more 



Reflection:

I enjoyed observing the environment and finding what worked and didn't work there. However there were some problems to this method. When we were observing it was hard to gauge peoples emotions and what was the cause of them. It's hard to pinpoint exact causes of frustration. Therefore a lot of assumptions are made. For example, we assumed everyone prefers window seats due to all those seats being filled but maybe there was another cause for this. The other seats could have been filled prior to us coming and those were the left over seats. Or perhaps there was another reason that we didn't connect. Perhaps those seats were all close to sockets or something.  We were only there for such a short time so you had a very narrow sample and no way of gauging if that was the normal crowd or not. I think this kind of method for research is fine as long as it is supplemented with more in-depth research. It would also need to be repeated at different times of day and different days of the week to get a full picture.  

Comments

Post a Comment

Popular posts from this blog

Slow Computing, Digital Civics and Portfolio Project

 Slow Computing & Digital Civics Slow Computing: - Cultural shift towards slowing down life's pace - Computing is deeply imbedded in our lives - Slow computing VS Calm technology     - calm tech promotes moments of reflection and mental rest. The info is presented passively and it's usually in our poriferas.  - Some Design: meditative bodily introspection -Fast Technology: well-defined task, efficient, easy to use Reflection: Most companies are focus on quick profits, fast technology. Slow technology cares more about the users mental wellbeing. As UX designers we need to design for slowness, solitude and mental rest. How do we change the functionalities and design to help the users not get overwhelmed? We could avoid numbers based goals and information. We should reward users for taking their time and  "Living Technology Lives", people are always on their phones and rely on it heavily. It has become an assumption that everyone has a smartphone and is online 24/7.
Read more

* CS806 Research Methods Lecture 2

 Qualitative Research Data Collection Qualitative -Research Questions -Words as data -Local meaning, patterns divergence & difference -Values subjectivity * A good researcher is always systematic Systematic -More than a summary or "averaging" of data -Using recognized methods -Reporting on how methods used and findings derived -So you can make claims from your data -Could another qualitative researcher follow your work? Could they appreciate where your findings come from?     -need to have necessary details about participants so someone can replicate it and understand the findings better Where do we use it? -Evaluation studies -Understand User Group and Environment -Analyze the language people use to describe technology Example Qualitative Research Questions: 1. Whats women's experience on dating sites? 2. How do patients perceive doctors in a hospital setting? 3. What are non-experts ideas and opinions about climate change? Terminology Ontology :  Relates to reality
Read more

Reflecting on the Hierarchical Task Analysis

Image
Hierarchical Task Analysis   Pros and Cons      My team and I chose to use Mural to show the HTA of using the self-service machine in the library. The first problem was knowing where the task started. Should we include "Get a book from the library" or is that too obvious. But what if they expected to check to see if the book is available and checking it out was something done before hand? But most libraries would have you get the book prior so we went with finding a machine for the first step. We tried keeping all the instructions concise to try and prevent them from feeling overwhelmed. We used lines to help direct the viewers attention to the corresponding steps and subcategories. The subcategories that we put below were the options they would see on the screen. We didn't include any plans for if something went awry to avoid confusion.  Our team also made a HTA for how to make tea. It seemed simple enough but once I started talking with my team I realized we all have d
Read more