Top Challenges of UX Research & Design and How to Overcome Them
Top Challenges of UX Research & amp; Design and How to Overcome Them Chou Yang March 19, 2020 Chou is a solutions organise gone production vender who loves to connect with ev
Top Challenges of UX Research & amp; Design and How to Overcome Them
UX Stories at mabl - Part 1
UX is something that any product-led team should be concerned about - from engineering to quality assurance to selling. Company and revenue growth comes from delivering first-class experiences at every level in the customer lifecycle, and that ’ s critically true erst the user is in the actual product.
There are general challenge that are present in every redesign labor and some that are unique to the component under work. So we guess we 'd part a bit about how we at mabl centering on providing a great experience to our customers in a series of posts that will introduce some of our upcoming mabl app design updates, our process, the unique challenges faced, and how we approached them. & nbsp;
The first post in this serial will cover how we use UX design and research practices at mabl to yield our customers a outstanding experience. Stay tune for more posts like this coming soon! & nbsp;
Defining end and priorities
The nucleus goal of our coming design updates is to make the mabl app efficient and, above all, approachable. For exemplar, our engineers have execute a outstanding job accumulate a ton of symptomatic information from every pace of every test run, but for new users, the wealth of info may be overwhelming. This gave us an opportunity to, as a squad, work together to rivet on our customers and provide the good experience for them. In future posts, you 'll see updates to our exam output page that we ’ re act on right now which will better direct all of that information. & nbsp;
When we depart new plan work, we focus on evaluating what we get today and then defining what our goals are. This often involves getting feedback from internal and extraneous parties.
Internal folk:
- Product management:Customer usage metrics. Are there any region where we can better drop-off in utilization? Are there areas of the app that seem underused?
- Engineers:What are the goals of the design? Are there various finish? If so, how are they prioritized?
- Customer Success:What are the most frequently asked questions staunch from the design at paw? Are there any opportunities for education that we can accomplish in the app?
- Sales: Are there any chance to clarify how our solvent solves a relevant problem of the prospect?
External folk:
- Competitor analysis.How are competitors designing to solve the same problem? Why do they do it that way? What do they do well? What opportunities for improvement do they get?
- User interviews.Hear directly from the exploiter. Where are their destination misaligned from ours? Do we require to point the user to fit our intended path or are their assumptions the better solution?
- Customer interviews.What job do they hold with the design? Are those major problems or minor nice-to-haves?
Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.
The Testing Part
After thoroughly researching the problem and setting goals, we commence iterating on a solvent and testing it with users. This phase is yet but a lap in a longer race.
Keeping the overarching goal in mind (in our case, want to be as effective as possible, while be as accessible as possible), we design a adaptation, parcel internally, and judge it using the same method as our initial follow-up period. Then we share externally via usability screen sessions, amass multiple users across different companies and roles to get an aggregate sense of how the design under review will hold up.
There are a few thing to look for during these valuation. You might need to validate or even update the original precedency or end of the design. For illustration, you may discover new end the more the pattern is shown to user and as you go along further down the design process. For illustration, when we started thinking about some improvements to our exam output page, we learned that the nucleus goal users get with this page was to gather information about a failing test. We also learned that a secondary user goal was to work collaboratively with their teams.
But don ’ t view new goals as a total miss on you and your squad ’ s part. New destination are a great signal - it could imply that there has been improvement since the last design iteration because the initial problem-set is now less prominent with the new design. The user might be keen on acquire their “ nice to haves ” transmit now that their “ want to haves ” are met.
We also look for whether or not users are able to rapidly chance the chief action on a yield page. In a mabl user study focusing on our test output page, we might be measuring how long it takes a user to diagnose a trial failure. If we start to see user preferences trending toward the new design, so we know thing are heading in the right direction.
The do it all over again part
UX design isn ’ t a project that ’ s e'er complete. There are always new feature under ontogenesis, designs get outdated, new challenge get discovered. At mabl, we focus on continually re-evaluating our experience in order to cater the good possible product to our exploiter:
- Gather goal, priorities, and feedback internally
- Initial blueprint
- Evaluate against priorities and finish
- Test against outside users and client
- Evaluate and/or update priorities and goal
- Iterate on blueprint
- Test again against external users and customers
- Repeat steps 5-7 as needed
- Implement
- Track performance, name betterment for the future
What ’ s coming next?
mabl is fortunate to have a squad dedicated to UX at this growth stage. We follow the processes and principles outlined in this office to provide a great experience to our customers. & nbsp;
We 've got a lot of great design updates to the mabl app draw up and are excited to parcel them with you as presently as we can, along with their unique challenge. Stay tuned for more posts like these coming soon!
In the interim, you can use a tool likemablto continuously ensure that your web apps are working as you intended. mabl is a trial automation solution that enable anyone to createuser-centricend-to-end tests in mo. You can try mabl for 14 years complimentary flop now by signing uphere.
Quality Engineering Resources
Automate This With SUSA
Upload your APK or URL. SUSA explores like 10 real users — finds bugs, accessibility violations, and security issues. No scripts needed.
Try SUSA FreeTest Your App Autonomously
Upload your APK or URL. SUSA explores like 10 real users — finds bugs, accessibility violations, and security issues. No scripts.
Try SUSA Free