The way or what methods did you use all are what I am looking for.
When I arrived, our payment flow was a mess. It would only be 1/3 of the screen, with a lot of distracting elements. We redesigned the whole thing, so that everything that was distracting was removed. And also just made it look nicer (white background instead of black for instance). Conversion rate at this stage went up by 400%.
@Donovan, What were the methods you used to determine the best UI or UX for your product.?
@AhmadBashir, Not sure we used any specific methods. I just looked at the product, and thought: “I guess our users hate this part”. Then looked at the data which confirmed this. Me and the designer talked about what we could do better, and looked at other sites for inspiration. Then we came up with the current design after some discussion.
@DonovanOkang, What was the data that confirmed this?
@JesusRojas, We looked at our funnel, and could see a lot of people dropped off at this stage.
And on HotJar we could see that a lot of people started filling out the form, but then went on to do something else.
So we decided that when people have decided to make a purchase, we should make it really easy to complete this task, without trying to make them look at other products and stuff like that.
There are certain rules of thumb in UI that help to improve the user experience overall.
Like Fitts’ law, the “novice experience” that makes sure the context is always clear if the person was distracted for 15 minutes, no modal windows, etc.
I always remember about it when I work on a prototype, so nobody complained so far. In fact, users call our app intuitive even though we’ve never invested in proper “sleek” UI.
Some of the teams I’ve worked with have spent a good portion of their time looking at or building user journey maps for the entire path the customer takes, start to finish. Doing this process they learned:
- where the customers spent the majority of their time in the flows
- whether or not the customer ever made it to the valuable parts of the experience
- if customers were getting stuck or lost
- if the experience, as a whole, worked or failed for various customer groups
From this up-front work the team was able to determine where to focus their efforts so that users more quickly got to the “stuff that mattered.” At one company this reduced the steps necessary to do a core activity from 12+ steps to less than 4, which led directly to more feature use, leading to more retention and then more revenue from customers.
Customer journey maps, if done correctly, are your friends.
A lot of our UX/UIhelps alleviate customer support requests, so I would say our general work mentality is often to reduce those incoming requests.
As someone said: work with your designers, use quantitative data from analytics, HotJar, amplitude, PBI and do moderated sessions with users.
There’s a lot of assumptions behind the question. It also suggests a PM could/should solve design problems. My question to this question is where does the product designer come in? If this is another assumption on managing designers with certain methods than it’s probably not a question worth answering.
What you should do is work with designers on this.
I have never suggested anything like that. I don’t know where you got that idea from a simple question like this.