Oh Capital Metro App… mapping the pain

In our first assignment for Q2 in the Rapid Ideation and Creative Problem Solving class, we were tasked to deconstruct and analyze the current state of the Austin Capital Metro mobile app. The goal of this project is to find the obvious inefficiencies in the system structure, and map them out in a visual “Concept Map” of touch points, or areas of interaction with the app that we personally deemed important to the end goal the user is attempting to create. After mapping our version of the current state of the app’s system design, we then created a new, first iteration, of what we thought would be a good starting point for the optimal system flow for completing the task of 1. planning a trip, and 2. purchasing a ticket to be able to take the trip you need.

Below is my Concept Map of the current system flow of the Capital Metro app on a relatively high level. ConceptMapAsIs-01

The main issues I found with the current app was not only the general confusion in the interface, but the redundancy of information, when things could easily be consolidated for ease of use.

Below is my first iteration of the basic system flow for a re-design of the app. The first screen being an actual geo-located map of where you are in the Austin area, and what bus stops are surrounding you visually represented by clickable icons that give you more info about the bus, the schedule, and the route.

ConceptMapIdeal-01

I also believed it was important to be able to store information about your most valued routes, and easily purchase tickets within the app, both in the constant navigation bar as well as during the establishment of your route choice.