CapMetro Redesign Iteration 5
Five weeks into the Rapid Iteration and Creative Problem Solving class, I have worked through another iteration of a redesigned CapMetro App. Seeing this proposed redesign in the form of wireframes continues to allow me to illustrate the interfaces that help bring the proposed redesign to life. The challenge in weeks prior seemed centered largely around having all the screens created. Ironically, I now find myself on the opposite end of that spectrum, considering what screens and controls could actually be eliminated in order to help the user achieve their goal.
In this iteration of the CapMetro app redesign, I made several changes related to buying or using a pass from the Trip Planner.
Trip Planner Changes
- Provided user with option to buy or use pass instead of just being able to see their map.
- Made the pass button is conditional. Depending on whether a user has previously purchased pass in their pass holder or not determines whether the pass-related button says “Use Pass” or “Buy Pass.”
- When you hit “View Route” it will now only show the one route you selected with the Use/Buy Pass option. The second and third route options that populated previously will no longer appear on the screen.
- Buy pass will go to the Buy Pass Flow and Use Pass will go to the Pass Holder.
- Eliminated the calendar. No need for the user to be able to select a date in the future. This is not intended for the user to pick a route and then save that route for a trip in the future.
- Added in a search function.
Buy Pass Changes
- Added a credit card icon to indicate where the CVC is located on a credit card.
- Combined the billing address form with the credit card form together.
Pass Holder Changes
- Omitted the step where you have to tap on the pass to reveal the bus code to be scanned for use.
- When going to the pass holder, the barcode is shown from the first pass holder screen.
- Passes are labeled as to whether it is a bus pass or rail pass.
In this iteration, I also revised the concept map which was used initially to map the existing system. Concept maps are used by a designer to visualize all of the components within a system and understand both the priorities and relationships these components have. The revised concept map shows the re-ordered priority on the home screen. In wanting the user to plan where they’re going first, it makes more sense to give the Trip Planner button first priority and then giving the Buy Pass button second priority. This re-prioritization is reflected below.
I’m continuing to practice an an evaluative user testing method called, Think Aloud Testing. With this testing method, the design researcher can get a glimpse into people’s working memory. I am able to get a glimpse into how people are thinking through each step as they articulate what they’re thinking without affecting the outcome of the task they’re performing. In taking these higher fidelity wires and testing them with potential users, I’m beginning to recognize that the tasks created for users to complete in this method of testing don’t just need to be the most obvious ones. For example, while the user must be able to plan a trip by getting from a starting destination to an ending destination, there are other ways to frame what goes into planning a trip. I could instead ask how they might compare routes in order to get to their destination on time.
For the first tasked, users were to plan a trip from their current location, The University of Texas, to The Domain in North Austin. Having made numerous changes to the trip planner, I wanted to see if these changes were effective at providing the user with a way to purchase their pass once their route was selected. While it was easier for the user to move from the trip planning flow into the pass buying flow, the new search screen that was introduced in this iteration seemed to cause the most confusion.
“Do I have to know the address of where I am? Oh yeah, I’m at UT. I definitely don’t know that address.” – User Testing Participant 1
“Is this where I should type in University of Texas?” – User Testing Participant 2
In the third tasks, users were asked to set up their profile. The problem that surfaced in this task was with the pin code. Users would enter in the initial pin code. On the next screen for re-entering the pin code, users would hit the back button and were not successfully reaching the confirmation screen.
“I’m done now, right?” – User Testing Participant 3
In addition to making changes that address the problems identified above in user testing, I will write tasks that consider trip planning and pass buying in a different context. Instead of focusing on getting to the destination, I will also introduce consideration of having to get somewhere by a certain time, using a pass that is already purchased and in your pass holder and changing your mind about your end location while planning your trip. All screens for my proposed CapMetro Redesign can be seen here.