Posts on Twitter:

Seven Common Usability Testing Mistakes โ€” UX Articles by UIE




























Quick test of visual : a reflection of what I have learned from over 100 tests | It all starts with recruiting the right participants โ€“ by




: our 5 golden rules for ethical growth & management | From inclusion to , these are top tips to help you successfully recruit for and maintain a healthy panel of users ๐Ÿ‘ฉโ€๐Ÿ‘ฉโ€๐Ÿ‘งโ€๐Ÿ‘ง๐Ÿ‘จโ€๐Ÿ‘จโ€๐Ÿ‘ฆโ€๐Ÿ‘ฆ







Are you in ? Take part in remote to try out new features of our tool. There are still a few time slots available! Apply now:










There are several techniques you can use to increase the conversion rate of your site: , , , video recording analysis e.t.c But what about spying on your competitors?



Retweet Retweeted Like Liked











Posts on Tumblr:

instagram

This is why Usability testing and designing for a context is so very important.

A simple thing that hurts a customers User Experience. Ordering something from box8 and want to make a payment using PayTM.

Just trying.. unable to make a payment!

Simple design plan for any app
1. Know the user
2. Know the context of use
3. Design
4. Test

#ux #uxdesign #userexperiencedesign #userexperience #uxdesigner #uix #uxui #uxd #prototype #userinterfacedesign #usability #usabilityfail #usabilitytesting #sketchapp #cx #b2c #uxcritique #design #digitaldesign #creative #appdesign #dribbble #paymentpage #behance #instafood #principleapp #designinspiration #uitrends #uimobile #uiux

Please note, this is not my design and views include constructive criticism! I still completed the order and love the food, as always!
https://www.instagram.com/p/B0xhA3_Asgo/?igshid=1k8x0jelz8ugt

Made with Instagram
instagram

Working on my another project since long time.
It’s a concept app of mine and I’m currently doing #Userresearch(mostly Qualitative) on this project.
While designing the #prototype for #UsabilityTesting, I decided NOT to go with just the “Pretty Pixels” NOR “Paper prototypes”.
So, being from a technical background, I always loved the real working screens so that I can get a clear picture of ‘User behaviors’.
Thanks, to the @uxpin it’s pretty much possible to design(or should I say “Implement” a complete design) using Advance interactions, Variables and more.

Here I’m sharing a concept from one of the core modules.
It’ll help you add your expenses more quickly with lesser clicks.
(A complete case study/app is on the way, stay tuned!)

Ignore the tags:
#userexperiencedesign #uxtrends #usabilitytesting #usability #userexperience #research #concept #uxui #usertesting #html #uxpin #userresearch #uxdesign #ux #prototype #wireframe #uxdesigner #sketch #adobexd #invision (at UXPin HQ)
https://www.instagram.com/p/BxT-Qt9niAl/?utm_source=ig_tumblr_share&igshid=13kjknq82zh4g

Made with Instagram

When to do usability testing?

1. The basic answer: any and every time during the product cycle.
2. When forming a concept (you can even test low-effort paper prototypes or competitors’ sites or apps)
3. Beginning of a project — test the current solution you want to improve or rethink
4. UX design or redesign phase
5. During development
6. Follow up
7. Backing up some strange quantitative data

Aim to have usability testing as a recurring activity in your UX design process. Do it as often as you can, in all stages of the product cycle.

When to do usability testing?

1. The basic answer: any and every time during the product cycle.
2. When forming a concept (you can even test low-effort paper prototypes or competitors’ sites or apps)
3. Beginning of a project — test the current solution you want to improve or rethink
4. UX design or redesign phase
5. During development
6. Follow up
7. Backing up some strange quantitative data

Aim to have usability testing as a recurring activity in your UX design process. Do it as often as you can, in all stages of the product cycle.

Questions to ask before planning a usability test round:

1. What’s the product to test: Are you onboarding a mobile app, a website filtering system, or a kiosk interface prototype?
2. What’s the platform? When testing a mobile app, determine if the OS matters and if it might bias the study. If so, let participants choose the OS to test on. This approach works best since, for example, a back button on Android devices can matter a lot in the user experience.
3. What are the research objectives? One objective can be to check if users understand the passwordless registration and login. Another sees if they can easily navigate to the product detail page. Turn your high-level objectives into concrete research questions.
4. Who’s the target audience?
5. How many participants do you need?
6. How are you going to reach them? How do you make sure they come from the target audience?
7. What will you give as a gratuity? (money, gift card, discount, tickets, lifetime access to your product, etc.)
8. Remote or in-person: Base your decision on the type of product, project scope, objectives and target audience. Choose the one that proves more feasible (technically and financially).

When you’ve cleared up all the above, you can go on to write a detailed test plan. Good luck!

NEW YORK PUBLIC RADIO 

As a Product & UX Consultant for a period of 5 months, I worked on the WNYC mobile app to take a new leap in on-demand listening, to Improve the engagement and to maximize the local listening audience. I was involved in the entire life cycle of the product ideation process, beginning with various research methodologies to experiment new product directions, to designing them in high-fidelity after validating multiple iterations with users. 

Here is the full design process that I was responsible for.

Here is the test script and objectives for one of the usability sessions that I conducted.

Usability testing - an important tool to measure progress

As mentioned in my previous posts, my next task at work was to do usability testing for an app that is currently in the App store and the dev team is working on a new release. Luckily, the higher-ups in the company I work with, understand the significance of usability testing, so I didn’t have to do much convincing in this area. But, they were not going to just ask me to go ahead and do the tests. They were looking for concrete reasons from me to prove how and why I will be choosing which usability testing method.

At school, we focused on qualitative usability testing which yields a better return on investment for a few reasons. Essentially many research studies done by different UX experts including Don Norman and Jacob Nielsen have shown that when doing usability testing, it has been observed that testing 5 users seems to be enough. But, it doesn’t stop there, doing 5 usability tests is enough provided you do several such small tests in the future to test your iterations as you incorporate the feedback from the previous set of tests. According to Norman/Nielsen, the first set of 5 tests will not reveal 100% of the usability problems, but it can reveal most of the glaring problems. And as you do more and more tests by improving on older versions, the problems that are missed in the previous sets of tests (and which are still there) are revealed eventually.  Norman/Nielsen’s study goes on to say that after 15 users what one learns of the usability problems gets plateaued out.

Other than the above reasoning, recruiting 5 test users is less-time consuming and is budget-friendly (which is important to keep in mind as we will be doing more usability tests in the future). Armed with all this information, I presented it to my supervisors, who seemed to be convinced (though a bit skeptical) that we should go ahead with 5.

But, just doing the qualitative usability test was not going to be enough. My company wanted me to come up with usability metrics as the goal of the testing was to be able to measure and track progress of the usability performance of the app between releases. They wanted me to adopt quantitative methods of testing too. Since we hadn’t done this in school, this was a good learning experience for me. As not only did I have to learn how to do it, I also had to prove to my supervisors why I am choosing to adopt one method over the other. Luckily, I had the blessings of the Senior UX Consultant for the company with whom I was checking all my findings so I knew I was on the right track.

To measure usability quantitatively, I chose to go with the System Usability Scale - a ‘quick and dirty’ (not so dirty) method of measuring usability and getting some numbers that help when comparing usability performance over different versions/releases of the app.

More on that, in my next post.

youtube

Update: Waiting to make sure it is okay with my company to share this…

Previously on my blog: Example of one of the many prototypes I built using Hype 2.0 by Tumult. This allowed for a quick and dirty prototype to be placed into users hands after a day of work. This was a huge win for MINDBODY Online because the devs knew exactly what to build and the UX team was confident in this first live phase 1 of the booking process. 

Check out the app: MINDBODY Connect via the Google Play Store. And look for the refreshed and refined Connect coming out soon.