UNCLESOON'S BLOG

I want to introduce how a network feature including call back ruins our users’ experience today. I bet you may have more than one feature in your product at least, and you may be missing something to make users frustrated. That means your UX is able to be bad somewhere.    1. Prologue These days we can see lots of convenience features in the product like autocomplete, so you don’t need to type the full text keyword. This kind of feature makes it easier to do users’ tasks and also gives an advantage of data regulation.  By the way, when you consider the feature, please check this one.  2. Case 2.1. Successful user scenario Here is a simple case about autocomplete when you enter the keyword in the text field. Mostly it is used for the data of location that can be regulated. When you type the keyword in the first step as below, Text fields in the page You can see the keyword suggestion with the autocomplete feature like this.   Autocomplete in the ...

When I talked about Persona analysis and User journey map, I felt tired of thinking of the goal from this work to the design process in the final stage. I can understand why we need this process to understand our potential users and their needs. However, I am just wondering what is related to the design process for high fidelity design or working prototype from these. 1. Prologue I love to listen to the VOC, the voice of customers, which is kind of raw needs, and also like to guess what they need when they use the product.  Persona analysis and user journey map show what users’ characters are and how they use the product, when we design the product at the very early stage, I could understand why we need this process, but I still have a practical question. ‘What is related to the product design in the final stage from this output?, and how can I approach this process more quantitatively, practically, or scientifically for the design process in the final sta...

When it comes to talking about user flow, I have been thinking about the gap of the output for co-workers in the project. As I am a UX designer or product designer in the team, I should understand what users do in the product and also consider how to deliver them to other co-workers like developers, marketers, or others. 1. Prologue This is my big question about the “User flow” or “Work flow”, whatever people call that in the project.  'How much detailed should I describe it in the document?' By the way, I have seen the situations so much at work. If I don’t care about so much, nobody cares about this as well. Then, can you guess what happens to users? I found out a lot of bugs of the feature, tangled user scenarios. I really can’t believe nobody finds this kind of problems in the product, and they are still there.    2. How to make the output Output of the user flow analysis looks simple, but I can find a lot of errors by itself when I take a look at the outputs by othe...