CapMetro Redesign Iteration 6
In this sixth iteration of the CapMetro App redesign for my Rapid Iteration and Creative Problem Solving class, I learned about how you can use scenarios to help you overcome feeling stuck about not being able to come up with solutions for your system. Scenarios are written stories used by designers to articulate how a person will use their system to achieve a goal. With only one last iteration to go this quarter, I decided to focus my time on building out the user flow for what was originally the Schedule.
After crafting a short scenario, I came to the decision that what a user that routinely rides the bus needs is not just a schedule of routes, but a way to know what buses are near them and when. From here, I illustrated the interfaces that help bring the proposed redesign to life by creating wireframes.
These are some of the changes that I made based on replacing the Schedule with Buses Near Me.
Home Screen Changes
- Eliminated the schedule button and replaced it with Buses Near Me
- Eliminated Next Bus because Buses Near Me does the same thing in that it allows a user to see based on the stop closest to them, when the next bus will arrive. It is also not useful for the user to just see the time the bus will arrive without the context of where they will be picked up from.
- Adjusted the size of the Pass Holder to be the same as the other buttons on the screen.
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 changes made to the the home screen. Getting rid of Next Bus means I can make the Pass Holder Button the same size as the others. I also no longer need Buses Near Me.
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. This allows me to hear how people are thinking through each step as they articulate what they’re thinking without affecting the outcome of the task they’re performing.
For user testing this week, I provided the user with the following scenario: You’re a regular bus rider that usually takes the same route at the same time every day. Today is a special day. There’s a major event in town and you have decided to head to work at a later time than usual. How would you use the Buses Near Me feature to find a new route to your job at the Domain. This task revealed several breakdowns in this flow:
“Why would I use Buses Near Me instead of the Trip Planner?”
“Where’s the keyboard?”
“How do I know where I am right now? I don’t know where Century Oaks Terrace is.”
“Maybe I can press the time?”
What user testing revealed for me is that moving into my final iteration, I need to identify the best elements from Trip Planner and Buses Near Me and combine them into one single flow. They are both For example, I think that the Buses Near Me map could help the user visually orient themselves better than the Trip Planner map because it immediately shows you what route is associated with the times displayed on the screen. From the Trip Planner, I think the ability to immediately buy or use your pass. All screens for my proposed CapMetro Redesign can be seen here.