Panel Report — Interaction Design & Usability Test

During our very first panel presentation, I had the privilege of listening to Professor Alan Borning talk about the interaction design process it took to create the mobile application, One Bus Away. I also had the privilege of learning more about the usability test by listening to Laura Barboza on her latest usability test project which was a Nordstrom’s Anniversary Sale UX design.

Take Aways: Interaction Design

From Professor Borning’s presentation of the creation process of One Bus Away, I learned that the current mobile application of One Bus Away was a result of a lot of trial and error. The creators went under multiple testing of the user-interface to see whether users would be easily able to navigate through the application without any difficulties. With the targeted users changing from expert bus commuters to the general public, One Bus Away went through numerous revisions so that the information displayed was simple enough for all users to understand.

One aspect of the project that stood out to me the most was how this project wasn’t just CS Engineers coding the application. It took a collaborative effort from other fields to contribute their knowledge to make the creation of this application possible.

Take Aways: Usability Testing

From Laura Barboza’s presentation I was able to learn that: One is never enough. For the Nordstrom Anniversary Sale UX design, usability testing for each improved UX design of the website. In terms of results, it’s very crucial to make changes directly from the feedbacks from the participants. Also, when presenting the results it is more encouraging to talk about the positives of the design before the negative.

One aspect of the project that stood out to me was how frequently the usability test was conducted after every upgraded design. It allowed me to realize that you cannot just assume the design improved after the a changed has happened. It is important conduct a usability test after the change to see whether there are any more improvements that can be made.

Improvements on my own sprints:

Knowing that one is never enough. I would improve on my personal sprint projects by creating multiple prototypes and having usability tests on those prototypes and revising my projects based off of the feedback I get from the usability test. Then, revising my project so it meets the satisfaction requirements of my potential users.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.