Posts on Twitter:

Building usable conversations: conversational | Conversational testing is a relatively unexplored and misunderstood area, partially because of the diversity of conversational interfaces available today – via




Our next happens on 27th Feb! We're delving into a hot topic – remote and techniques & tools (with some tips on the side) with the help of from . Register here 👉




.'s next happens on 27th Feb and it's all about remote and techniques and tools (with some useful tips on the side) with the help of from . Register here 👉




Our friend Jake from recently had his website tested and went away with valuable insights as to how his customers think.




PFR's shares some tips on how to create a successful participant recruitment brief, one of the key ingredients to successful and
















I would like to share my results from yesterday. I have designed two prototypes using and tested. I have used 12 participants. What are your thoughts? Please comment below. 🙏


















Retweet Retweeted Like Liked



How to celebrate Valentine’s Day when you’re in a full day of usability testing 🌹

This media may contain sensitive material. Learn more View











Posts on Tumblr:

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.