12 Matching Annotations
  1. Oct 2021
    1. Very few of the failed teams did their own research. Most didn’t do any research. Instead, they made up the personas out of whole cloth and what they imagined their users to be like.

      Assumption! What you would do or what you think a group of people would do based on your sociologic experience is a quick, easy and cheap way of doing things - but will prove a problem in the long run. Those shortcuts might have worked doing homework in high school, but it will never apply to product design and UX research as it is simply not the real world... even if your assumptions are close!

    2. When we talked to the successful projects’ team members, each one could, without fail, describe the personas from their projects. They knew who they were and what made each one unique. They did this all from memory, often months after the project’s completion.

      It is a beautiful thing to see how much of psychology and sociology is tied into UX - something I must admit I was not very aware of before starting the course. As a naturally empathic person it is exciting to know there is a world where that meets with art, curiosity for people, and a general desire to understand people better.

    1. One of the first steps in each round of usability testing is to develop a plan for the test. The purpose of the plan is to document what you are going to do, how you are going to conduct the test, what metrics you are going to capture, number of participants you are going to test, and what scenarios you will use.

      Interesting to see how much planning into the totally unplanned activity that is live user testing - so much going on on the tester's side versus complete improvisation and flow by the test subject.

    2. Critical Errors:  Critical errors are deviations at completion from the targets of the scenario. For example, reporting the wrong data value due to the participant’s workflow. Essentially the participant will not be able to finish the task. Participant may or may not be aware that the task goal is incorrect or incomplete.

      It would be cool to watch a critical error happen when the user is not aware of it happening, because the damage is not really done, but you can still get a sense of what would happen if the user went down that route in a real life scenario.

    1. Concurrent Think Aloud (CTA) is used to understand participants’ thoughts as they interact with a product by having them think aloud while they work. The goal is to encourage participants to keep a running stream of consciousness as they work. In Retrospective Think Aloud (RTA), the moderator asks participants to retrace their steps when the session is complete. Often participants watch a video replay of their actions, which may or may not contain eye-gaze patterns. Concurrent Probing (CP) requires that as participants work on tasks—when they say something interesting or do something unique, the researcher asks follow-up questions. Retrospective Probing (RP) requires waiting until the session is complete and then asking questions about the participant’s thoughts and actions. Researchers often use RP in conjunction with other methods—as the participant makes comments or actions, the researcher takes notes and follows up with additional questions at the end of the session.

      Interesting to think this works just as well with kids as it does with adults. I guess the key is to make your test subject as comfortable as possible, to make it feel like a playful, interesting activity and to let them know they are helping you by participating.

    2. Remain neutral – you are there to listen and watch. If the participant asks a question, reply with “What do you think?” or “I am interested in what you would do.”

      This part I feel would be challenging to remember - to not do the task for them, but rather encourage more action and thought on their part through open ended questions and small nudges instead of hints.

    1. Sometimes it makes sense to create connections with other clusters using lines or other devices between individual bits of data or clusters of data.

      I guess here is where modern technology comes in handy. If you're doing this on a whiteboard maybe you can draw lines to connect ideas - definitely harder to do on a wall with post its - but you might end up smudging the ink or creating more work for yourself. Tools like FigJam seem like a beautiful way to still have that organized brainstorming feel while enjoying the perks of digital creation.

    2. The method is also called “Space Saturate and Group”. The term “saturate” relates to the method in which everyone covers or saturates the “space” with images and notes, in order to create a wall of information, to inform, and start “grouping” the following problem-defining process. You then draw connections between these individual elements to join the dots and develop new and deeper insights. They will help define the problem(s) and develop potential ideas for solutions. In other words, you go from analysis to synthesis.

      Interesting how in today's class exercise, after doing our 7 interviews, we kind of broke it down like this on FigJam without having read this article. Feels like an intuitive way of organizing a lot of different info you've got from several interviewees whose answers you have a feeling have a lot in common.

    1. User experience leadership

      How much of this can be learned and how much of it is innate? I have found myself in the past not being great at leadership and the managing of others, but if it's a skill necessary to create a well rounded UX designer it would be interesting to see how much of it can be taught to someone.

    2. Product Designer

      I knew nothing about UX UI a few months ago, but from the prework we've done and what I know about myself I think this would be my preferred area (or at least, what I'd be inclined to be better at).

    1. Avoid talking about yourself#section11 Sometimes, what starts as active listening turns into, “Let me tell you about a similar experience I had….” The interview isn’t about you or your opinions. This can be very hard to remember and takes practice to avoid. So, if you find that you’ve inserted yourself into their narrative, just stay relaxed and steer the conversation back on track.

      Another great lesson that sounds like it could be in 'How to Win Friends and Influence People' by Dale Carnegie.

      101 insta-likeable trait in someone you're having a conversation with but so hard to master! Normally the interjection comes from a good place ('I've been through that too, let me relate to you so you know I know what you're talking about!') but much more level headed and mature to let the person speak and show them you relate by really listening.

    2. When you’re interviewing someone you know nothing. You’re learning a completely new and fascinating subject: that person.

      This reminds me of a great lesson I was taught as a teenager doing martial arts that I never forgot - you can learn something from anyone and everyone.

      This applied in my world at the time when referring to more senior martial artists always open to learning from other students and practitioners (regardless of their rank) but it's a very humbling trait to always be mindful of - you can speak to anyone of any age, background or walk of life and rest assured you will learn something new every time.