Cooperation Eval: Practical #6

 Cooperation Evaluation 

Practical #6


We were in groups of three and took on different roles: evaluator, note taker and user(tester). We all had the same task of recreating a diagram but had to do it in different programs: mural, powerpoint and slides.

-coffee, felt bad about going with the easiest route and not including the cultural differences


Reflection:

I enjoyed this task. I wasn't keen on being the evaluator first but I learned a lot from my mistakes and from watching the others. Asking the questions along the way is difficult at times. It's hard interrupting others. I really enjoyed being the user and expressing the negatives or positives about the process. I also really enjoyed taking notes. I liked the time stamp and incident report template given. It was really useful when filling in the evaluation report so I can find the screenshots faster and I could match and map out my incident logs. 

How to get correct timestamp?

    - Recording time

How can we balance note taking and prompting tester?

    - Take time stamps with brief note to trigger memory

How in-depth should my notes be?

    - It's a judgement call. Usually you will have more time than an hour. You can usually have more time after the test to add onto your notes. 

   How can we put tester at ease?

    -Even if reassured you aren't being tested and given offers for help it's hard not to feel dumb as a user. If you aren't present and the user is more at ease you don't have the opportunity to ask questions in the moment that will be a lot more honest and real. 

In the report is there a portion where we can add positive constructive criticism?

    -Balancing the positives and negatives when reporting back to the team is important. You can add in the praise in a new section on the evaluation sheet. 

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