Reflecting on the Hierarchical Task Analysis

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 different methods. I am ashamed to say that I pushed to simplify the process by using the simplest method rather than the method that was the best at representing a variety of methods (culturally) of making tea. In the hope of making things more easy I excluded whole groups of people are their way of making tea. 

       Pros

  • Uses visual representation that's easy to understand and navigate by most people
  • Flows well (Sequence is easy to follow)
  • Encourages concise language to keep things simple
    • just gives essential information so its a very quick and easy "downloading" of information 
        Cons
  • Can't go into too much details or it will get chaotic and confusing
  • It can be difficult as designers knowing where to start and how detailed it can be without confusing the user
  • doesn't highlight any problems users can have and how to resolve them
  • cultural differences aren't representing. Implies there is one way of doing a set task and doesn't account for the variety of users





Work Objective Decomposition

 Reflection


    Focuses on the users objective rather than their behaviors. With clear objectives it eliminates the need for steps or a plan for the user. With significant objectives further details are given. A con of this process is no priorities are assigned. Another is if the user has a problem there's no information to address it.

    Example:

functional decomposition education informationExample found here!



Good and Bad Designs:




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