To further build on the persona I created, I put myself into the perspective of what a rider would think and feel when looking for the bus schedule. I mapped out the pain points so we can see what to expect from a target user.
From there, I created 5 user stories that align with building the MVP:
The MVP was going to an app that displays bus schedules that run through Washington and State. So I created a user flow, combining the pathways of each user story, to visualize how the app will function.
Now that I had the research done, the next step of this project was to create a set of wireframes. I started out by sketching a couple screens to see which layout may be best, keeping in mind that the design should be user friendly, convenient, and easy to look at. I wanted users to be able to navigate the app easily without having to learn how to use the app as a first-time user.
While I sat with each user, I took note of where each user tapped on the screen and what their thought process was to get to the end goal. I discovered that users seemed to first tap on the bus stop icon on the map screen, assuming it would lead them to the bus schedule for that stop. However, it was not tappable in the prototype, which unfortunately was inconvenient to the user. I also had the users verbalize what they felt were obstacles when navigating through the app. One feedback I received was to add an on-time/delay symbol so users can visually see which buses are late. The same person also suggested seeing close-by bus stops on the homepage so that accessing the bus schedule takes less taps. After thanking my volunteers for their input, I reorganized what I had to adjust before finalizing the project.