Ergonomics: PRACTICAL #7 Card Sorting and Affinity Diagramming

Ergonomics


Ergonomics: Designing for a range of people/body types so they are efficient and  comfortable.

Height, arm length, grip strength, finger length, etc are all physical qualities we should consider in our designs. Each population has their own averages.

Biochanics: the study of the structure, function and motion of the mechanical aspects of biological systems, at any level from whole organisms to organs, cells and cell organelles, using the methods of mechanics. 

 ex. measuring diameters of door hands compared to grip strength. Tool designs people need to consider the jobs it will be used for and what bad habits they can 


Design the physical interactivity. How do people interpret the world and interact with the things around them? Why do they do those things? Why are certain things more intuitive or convenient than others. 

Practical 7

Affinity Diagrams and Card Sorting

Card sorting: working with users to design an understandable information structure for something (website, app, software). Ex. Navigating a site like amazon they need to think of the grouping and categorization of products and functions. using the right kind of language is crucial.  


It was a great exercise that made us aware of our different ways of perceiving the world. We categorize things differently internally and had to compromise where and how to sort the things at the café. A danger designers with different thinking run into is creating too many categories or sticking all the things that don't seem to belong to their categories into "Other". We used productive cheating to compare our categories to pre-existing ones on different café websites. We also used ChatGPT to generate café items for our menu.

Affinity Diagramming: Organizing the experience of the user. We decided to organize it into actions at the café/ the duration. We
Here!


We revisited our Costa observational research data to diagram and organize the user experience. We decided to use a mind map that went through the journey of being at a cafe. Entering to departing. We included things they encounter and used emojis and colors to express emotions and whether it was positive or negative. 

SRS: Software Requirements Specification 
Specifies what will be built (requirements and expectations)
There are functional and non-functional requirements. 
Design Requirements: Define user requirements and specify usability should do and what the quality of the XP should be like


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