User Testing Wireframes

After getting critiques on our wireframes last Monday, we made edits to our wireframes and did some think-aloud testing with users. This was my first time doing user testing so I wasn’t sure what to expect.

It was my very first test with my very first user and she couldn’t get past the first button! And it wasn’t even a real button, it was a Touch ID button but she wasn’t sure where to press. I immediately saw the flaw in my design. The only clickable part was the bit explaining that it was Touch ID but I should have made the whole screen clickable so that no one got stuck on a “button” that actually requires hardware.

Log In

Luckily her reaction was not the trend for all of my tests (whew!). Two of my other flows went well for all the users with no surprises and no one getting stuck (Access Security Code, Deposit a Check). My Set Alerts & Notifications one was the biggest problem area and I believe it comes down to the fact that Capital One has users leave the app and go to Settings to set all alerts and notifications. Many of the users I tested got stuck here, not knowing what to do, not knowing what the options meant and not sure how to navigate back.

Allow Notifications

 

This is something I want to address in my next iterations. Capital One obviously wants users to turn on notifications (since the alert pops up as soon as you log in) but there needs to be a better way. That’s what I’ll be working on over the next few weeks.

I will also be working on my interview techniques. I did fairly well at letting users self-guide through the app but I definitely need more practice saying, “What did you expect to happen there?”