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

* Research: Different Analysis

Image
  Research Methods - Be transparent about what your biases are/could be in your research. - Theme names give some indication of what problem you are addressing -Appendices will give people opportunity to check your code and data Thematic Analysis: Look for patterns (Themes, hence the name) across textual data. The examples he showed was transcripts from conversations between researchers. He also showed us an example where the designers that updated the Metro used Mural to organize their themes and notes on the different areas that need to be addressed in their design. The themes can have subcategories that are more descriptive( CCTV--> Anti-social behavior). The Process:  Familiarization--> coding --> generate themes --> review themes codes --> define and name themes --> write up analysis  Grounded Theory: This one is different because you don't have a specific theory or hypothesis (or preconceptions about the theory). You just select an area of interest and begin
Read more

Week 2: Lecture 4 Ideation, Co-creation and concept sketching

 Ideation and Concept Sketching Project expectations: Communicate a critically analyzed design  Don Normans 4 Principles: 1. Understand people 2. Focus on the people 3. Solving the right problem not the symptoms     -Users may tell you small problems(Symptoms) and it's your jobs to identify the bigger problem 4. Always be iterating and improving Card-based Techniques for Ideation: When designers are developing ideas it forces yourself to consider different design/user aspects  Why? help us better understand the end user population and the research context or setting  What? Think about ideas and sensitize people to the ethics. Evokes consideration and discussion of longer term effects
Read more