đŸ”

Tartan Transit


Role

UX Researcher
UX Designer
UI Designer

Team

Hamza Qureshi
Jessica Kwon
Madeline Gardner

Tools & Methods


Contextual Inquiry, Stakeholder Mapping, Affinity Diagramming, Survey, Think Alouds, Storyboarding, Speed Dating, Five Second Testing, Wireframing, Prototyping, and Usability Testing

TL;DR:

CMU provides a shuttle and escort service for students to safely find their way home. Every year, the transit service faced declining ridership.

In order to pinpoint why, we conducted user research on many of the stakeholders in the system and found that students only knew about the service through word of mouth. Those that heard about the service felt that only certain students could use it. I ideated a solution that would make the transportation service information be passively integrated into the study body experience through G Suite, which is integral to the CMU student experience, while showing students how to use the services.

This project was a huge learning experience. I experimented a lot with different ways to conduct usability research on prototypes. For example, we used five second testing for our low fidelity solution to ask the question, “What do you see in our prototype that is new from what you are used to and would this be helpful?” In retrospect and with more wisdom, I would ask, through task analysis instead of five second testing, “How might this help you find your way home?" When we chose a testing method, we wanted to see if the passive influx of information would be noticed but we would have learned more from usability testing if we chose a different method; the nature of five second testing frames the usability test as a 'spot-the-difference' test.






The Problem


At Carnegie Mellon University, students are provided a shuttle/escort service. The goal of the service is to bring students from campus to their desired locations safely. However, the service has been seeing a significant drop in ridership. As a result, the Graduate Student Assembly is examining the transportation needs of the CMU community and trying to find ways to improve options for students to get to and from campus. Their vision is for every student to have access to multiple kinds of reliable transportation that allow for safe, direct commutes to and from campus.

Key guiding questions:

  • Are students satisfied with the services they have now?
  • What improvements could be made?
  • Why do current students not use the existing shuttle and escort services, and what could be done to increase usage?



The Solution

From our research, we found that the users biggest hurdle is understanding how to use the services and easily accessible information that can help them plan their trips. Our solution was to create Tartan Transit, a Google Maps plug-in/extension, that would provide a sense of familiarity due to the context of Google Maps, while quickly disseminating real time information that tracks the bus and procedural information, and provide service with ease and to encourage users to interact with the current system.



Research | Stakeholder Mapping


Background research was done to understand the current ‘ecosystem’ of the transit system at CMU. We were given several contextual inquiries to pull data from. There were several ‘actors’ in the system, each with different goals and motivations. For example, the Director of Parking and Transportation (P&T), who is charge of all parking and transportation at CMU, wants to take the shuttle and escort service under P&T instead of the Police Department at CMU. As a result, the service's information is underneath "University Police" within the CMU website. Confusing categorizations like these, due to conflicting internal structures, lead to hidden information about the service.




Research | Affinity Diagram


We conducted contextual inquiries on target users/actors, such as graduate students who use and didn’t use the escorts and a member of the GSA to further understand how the shuttle/escort system operates. The goal was to understand the users behavior in regards to how to get to and from campus, problems they have had, other services they use, etc
 After the inquiry we created notes from the interview and found patterns within the notes.



We uncovered several themes (the green post-its) of problem areas: information about shuttles, expectations of shuttles, adoption of shuttle, and alternatives to shuttles.

Here are several (blue) notes that were impactful to overall research process:

  • I want to learn more about the service overall.
  • I’m confused while using the shuttles.
  • No one told me about the shuttle service.
  • I think there are problems with the shuttle routes.
  • I hate missing the shuttle.
  • I only use the shuttle for specific needs.
  • I use other methods because I need to.

These revealed and summarized core concerns from students and they were used to guidee us during our ideation process.



Ideation | Contextual Inquiry


After completely understanding the landscape we were operating in, we started diving into understanding user needs. We asked similar questions to the previous contextual inquiry but we added a focus on how users acquired information about the service. Thanks to the research takeaways from our affinity diagram, we realized that focusing on information dissemination would provide the most value for our users and stakeholders.

From the inquiry, many people mentioned that the service felt safe because only CMU students are on the shuttles. We also found out that some students who live off-campus feel that their commute is scary, which shows a need for a safe and reliable method of transportation and highlights the positive aspects of the shuttle and escort services. However, we also found out that the accessibility of the shuttle service information is poor. Most students did not fully understand how to use the shuttle service, even though the shuttle service can be very valuable, as previously stated. Students did not know to learn more about the service because the information is difficult to attain and not well-advertised by the university. One undergraduate even thought that the shuttle service was only for graduate students, even though the shuttles are meant to benefit the entire university population. Some thought the shuttles were only for commuting, when the service offers bus stops around nearby grocery stores, which most of our interviewees usually get to through a rideshare service.



Ideation | Design Artifact/ Low Fidelity



With all those findings, we were on our way to a potential solution. Our team went onto invision and designed different iterations of the same task (showing procedural information). We were fleshing out the idea of integrating the shuttle and escort service into Google Maps. With the design artifact, we conducted several five second tests.



Solution




Finally


This is Tartan Transit.

Our solution focuses on ensuring familiarity and visibility of the CMU transportation services. By exposing CMU transportation options within Google Maps, a commonly used transportation app among students, users can easily choose to use CMU services when appropriate.

Anna is a CMU undergraduate student who lives off campus. She has never used the CMU shuttle or escort services before but decided to give the new Google Maps plug-in a try. Late at night, Anna types in the address to her house and finds that the Yellow Zone shuttle can drop her off near her home.

She clicks on the escort option to view further directions. A pop-up screen shows her how to use the escort system. Anna is relieved to have known this information and now feels more prepared to ride the escort.

After she dismisses the pop-up screen, Anna is able to view real-time information and detailed directions on where she can get on and off the escort. Anna is glad to have found a safe new method to go home late at night.

Clickable prototype with shuttle service example: https://invis.io/MVPFAUOPQY2



Solution | Takeaway


This was the first time I had done so much rigorous user research and user testing. Because of that, I learned a lot about the process. There was a repeat empasis on "you are not the user" and interviewing etiquette (such as making the user feel safe and not judged, avoiding leading questions, and learning to ask the right questions).

If I had a chance to redo this project, I would completely change the final usablity testing method from five second testing to a heuristic evaluation. This method change would allow for a better evaluation on our final solution. Instead of asking "what difference do you see?," I would ask: "how might this help you find your way home?" This change would have given us a better insight on how valuable and usable students this solution would be. This feedback would have pushed us to iterate with a better grasp on the sense of usability in our design.








View All Projects
PPS: Cross Platform Work Management // Tartan Transit: Web Mapping Plug In // DogSpot: IOT Smart Sidewalk Sanctuaries for Dogs // Xfinity: Smart Home Management // JYM: Healthy Meal Planning VUI // Cinemate: Social Streaming for Web