Did you know that you can actually drop the entire basket into the self check-out kiosk instead of putting the items one by one. The system can read all the items in the basket in one go.
This should be adapted at local level grocery stores, so ppl will jump out of their couches at lest have an experience in buying groceries as the amount of time will be same as waiting for the delivery guy to pick and deliver it.
I have 2 questions: 1. What if users do ot really use your product and simply digress by just using the billing counter where the employee would help the customer(User). Then the product we built would go to waste, isn't it? I just want to how do we even understad how the user eve behaves at that very moment and if they behave i the same way i mentioned above, then the company would have invested a lot of time and money in it. 2. If I am building a product, and I am unable to idnetify certain pain points in the beginning and I am in the last stages of the project, themn can i still work on those pain points and what should i keep in mind?
Which is why you do testing in a small scale first. If people are not using it then you find out why. Maybe they are not aware of it. Maybe it needs some marketing. UX is always experimental. If the results are as desired, then you scale it up. Otherwise you iterate. You might gather some new insights that were previously unknown. Now you would have more information than what you started with to help you make better decisions. There will be surprises. So prepare yourself to expect the unexpected. And anyways remember that it's not about you, it's about your design implementation which was based on the information that you had at that time. They can always be improved based on new information.
Hey amazing questions! 1. What you said is one individual behaviour. Obviously there is no use of the product that particular customer. But when you design products, you don’t stop building them because someone might not use it. You build them so that someone can use it and find out more people who would ultimately use it. We call this as acquisition. But the pain points which you pointed out can also act as ways to understand the behaviour for the reason behind the behaviour of the customers and think of how we can make sure more people are acquired.
2. You can always work on pain points. But we don’t design solutions for point to point spot fixing. I’ll give you an analogy. We don’t fix tyre punctures as a designer, our job is to redesign the tyre in such a way that it will have lesser number of punctures.
Did you know that you can actually drop the entire basket into the self check-out kiosk instead of putting the items one by one. The system can read all the items in the basket in one go.
Thats so cool
Thats so cool
This should be adapted at local level grocery stores, so ppl will jump out of their couches at lest have an experience in buying groceries as the amount of time will be same as waiting for the delivery guy to pick and deliver it.
I have 2 questions:
1. What if users do ot really use your product and simply digress by just using the billing counter where the employee would help the customer(User). Then the product we built would go to waste, isn't it? I just want to how do we even understad how the user eve behaves at that very moment and if they behave i the same way i mentioned above, then the company would have invested a lot of time and money in it.
2. If I am building a product, and I am unable to idnetify certain pain points in the beginning and I am in the last stages of the project, themn can i still work on those pain points and what should i keep in mind?
Which is why you do testing in a small scale first. If people are not using it then you find out why. Maybe they are not aware of it. Maybe it needs some marketing. UX is always experimental. If the results are as desired, then you scale it up. Otherwise you iterate. You might gather some new insights that were previously unknown. Now you would have more information than what you started with to help you make better decisions. There will be surprises. So prepare yourself to expect the unexpected. And anyways remember that it's not about you, it's about your design implementation which was based on the information that you had at that time. They can always be improved based on new information.
Hey amazing questions!
1. What you said is one individual behaviour. Obviously there is no use of the product that particular customer. But when you design products, you don’t stop building them because someone might not use it. You build them so that someone can use it and find out more people who would ultimately use it. We call this as acquisition. But the pain points which you pointed out can also act as ways to understand the behaviour for the reason behind the behaviour of the customers and think of how we can make sure more people are acquired.
2. You can always work on pain points. But we don’t design solutions for point to point spot fixing. I’ll give you an analogy. We don’t fix tyre punctures as a designer, our job is to redesign the tyre in such a way that it will have lesser number of punctures.
awesome
Nice vlog