Qualitative research and ignoring three types of feedback (February 26, 2020)

 


This week the teacher assigned two online readings and i am here to summarize them

In the first article, Taylor Nguyen talks about “How exactly do you find Insight from Qualitative User Research?”. She states that it’s all about synthesis, or the process of creating an understanding that goes beyond all data points after being collection. Nguyen talks about this being a four-step process (there is also a chart Nguyen provides that I included on the top of this journal entry:

    Step 1: Extract and summarize data  - From note, transcript, and artifact, It’s about fnding key information and write them down on sticky notes. The small size of a sticky note force you to summarize information into the key takeaways.
    Step 2: Find patterns across participants  - where the person starts to cluster similar information into themes. As a starting point, you might group information based on broad categories such as demographics, workHow, pain points, etc.
    Step 3: Create insights  - Ask yourself a few times for how different data might relate to each other, what’s the underlying reason for different behaviors and needs, then rearrange sticky notes into themes of insights.
    Step 4: Organize insights into a digestible format  - organizing insights into research artifacts that you can present to others. (This can be done in the form of either a user persona, journey map, service blueprint, and empathy map)

She discusses the procedure, elaborating that step three is usually the hardest as it usually entails what they mean by insights. Nguyen ends the article by saying that improving synthesis skills is about doing three things:  persistence, knowledge, and practice.

In the second online article, Jeremiah Lam gives us the “3 Types of Feedback to Ignore” when dealing with UX/UI Design.

The first type of feedback to ignore are, self-motivating statements, in which we try to improve our prototype designs, or to use a quote from the reading to put it in perspective: “It’s naive to think that a feature is able to change the user’s core behaviour” , meaning that the functionality of a design isn’t going to dramatically improve over the course of an update.

The second type are hypothetical statements, in where users like to predict their behavior (e.g. “I will upgrade if there’s this function”, or “they will pay for it once their team is big enough”) The third and last type is third-party statements, which are are basically a form of hypothesis from a non-user guessing the behavior of a potential user. I like how the author of this piece ends the essay with the quote that “The evidence of a real problem isn’t based on self-motivation, hypotheticals or hearsay. It’s rooted in actual experience.”

Comments

Post a Comment

Popular posts from this blog

Maze Compatibility pt. 2 (May 12, 2020)

I talked with my teacher on an issue regarding Maze and how to get a user testing run via Figma (from the Figma Website) as I might be doing something wrong. Talking through him, I think I realized my problem: I have been clicking the “Share” button by it, but somehow I thought there was a faster way. I thought hitting the play arrow button on the top right corner would allow me to instantly hook up with Figma. I tried this over the weekend, but couldn’t as FireFox (one of my two web browsers) wouldn’t allow me to use it as it would open additional pop-up windows. He went over the steps again and I took screenshots. The first step he said was to go the user testing portion of the home page and to click the ‘create a new project’ link, but after that I told him that I think I might know what the problem was. The problem wasn't that I was doing the steps wrong: I was doing them right. In fact, it had to do with which web browser I was using. I had Firefox opened, and that sho...
Read more

Chapter 2 Summary (February 2, 2020)

Chapter two of the textbook reading begins the process that was discussed in the previous chapter. The research phase begins the UX process; this is the process where a person understands the business content and gains an appreciation for the key markets. That’s the definition that the book says, but the key word in the first phase of UX design is all about ‘research”. That is, taking the time to do some research on either your target audience or competitors (or both), and when you’re done with that give a rough sketch or outline of what idea you are proposing. It’s also better to collaborate and communicate in this phase and have a business model idea (or framework) handy to maintain daily conversations with your clinch that will ensure back-and-forth discussions/healthy dialogue. the dialogue also consists of asking the right questions that should pertain to the business aspect in relation to the product and what they hope to get out of it. These questions might consist of the client...
Read more

Chapter 1 Summary and Online Reading (original post: January 30, 2020)

Image
The UX book that I will be using for class reading is “Killer UX Design: Create User Experiences to Wow Your Visitors” by Jodie Moule. UX is short for user experience, and is based around computers and the internet. The book defines it as a series of interactions that a person has with a specific product, service, or organization. Moule also brings up the methodology for user-based design systems, and the remaining seven chapters of the book will be based all around this method, with the chart found below. There’s also qualitative and quantitative research as methods for testing during the UX process: quantitative research looks at the actual behaviors of clients/users in order to get an understanding of why they do what they do, and quantitative focuses on mass data collection and analysis themes in order to make assumptions regarding human behavior. In order to dive into UX research, the person must also be able to put themselves in other people’s shoes in terms of what they would...
Read more