IBM Mobile Quality Assurance

Mobile Quality Assurance (MQA) is a QA feedback tool for developers and testers. It allows developers to deploy new app versions to testers and in turn allows testers to leave feedback and submit bug reports on the app. It also displays metrics for user sentiment sourced from app store reviews and comments from social media.

My Role

One of my first projects at IBM looked at a near term restyling of the existing UI for Mobile Quality Assurance as well as a longer term redesign of the entire product. By working with the established information architecture my team looked to improve the product with an updated dashboard and improved visuals for analytics and user sentiment.

Long Term Vision

Our strategy for a long term vision began with trying out the beta version of the product and talking with internal subject matter experts. We also spent time mapping the competitor landscape and benchmarking.

Our research concluded with the following insights:

  • QA is a community effort.
  • Automation is essential to the QA process.
  • Multiple environments and contexts make mobile QA different.
  • MQA should fit in with existing systems so users can work efficiently.
  • QA needs to occur throughout the software development process.

Interview Clustering Activity

We interviewed QA testers and developers from 5 different companies to get a better understanding of their processes and needs. 

Whiteboard Concepts

We explored hierarchy and navigation in the application to create multiple design directions that could be shared with our stakeholders.

Concept Wireframes

This concept explored a new menu that clearly separated different activities within the product. Development teams are able to address device distribution, bugs, crashes, and sentiment in dedicated areas giving the product focus.