Role: UX Researcher for YouTube

UX Research Project Lead:

Eileen Ellis

UX Research Support:

Katie Belleville

Product Team:

Ben Kendall

Engineering Team:

Steve Warner,

Data Engineering Team:

Peter Situ,

Design Team:

Ritwik Deshpande

Clients:

YouTube is the world’s largest online video sharing platform owned by Google. The YouTube Living Room Team specifically focuses on the YouTube app on the TV, and frequently collaborates and aligns with other YouTube teams such as Mobile and Web, Music, Youth, and Premium, as well as other TV-focused teams such as GTV. The YouTube Living Room User Research Team has different divisions assigned to each researcher: Search and Discovery, Identity and Connected Experiences, Watch and Shorts, and Creator experiences.

www.youtube.com

Research Prior to Travel

• The Penske Dash Launch Team Manager and Customer Success Manager were interviewed to learn what feedback had already been received from the client pertaining to the research subject.

• A remote workshop with the Penske Dash client team was conducted to:

  • Understand Penske Dash’s current damage reporting process including types of damage (including cleaning), how Penske Dash does reporting internally, how they manage and resolve issues, what data needs to be stored, what information they need to access periodically (analytics), and applications for different types of services.

  • Review information Ridecell has already received from Penske Dash about damage reporting, to receive clarification, if needed.

  • Bring up use cases and test hypotheses with the customer according to the conversation.

  • Understand Penske Dash goals for damage and condition reporting, including what they are aiming to do in the future i.e. plans or processes that are already underway.

  • Prioritize Pain Points/Proposed Changes brought up through the workshop.

  • Develop criteria about what Penske Dash needs Ridecell to consider when designing the solution.

• Stakeholder interviews were conducted with different Ridecell internal teams including Product, Design, Engineering, Launch, and Customer Success, to understand what they would like to learn from the user research trip and to gain buy-in for the process and results.

• Cognitive walkthroughs were conducted with the main Penske Dash product designer to locate gaps and pain point areas in the flows the research team would test, according to different scenarios such as: different travel methods to the garage location, during and outside of garage business hours, whether the user was registered or not, whether the user was signed in or not, if the user was away from the vehicle being reserved vs. at the vehicle, etc.

• Since Ridecell was not allowed to use the actual Penske Dash consumer app and service (vehicles, Colonial partner parking garages) for testing, I needed to coordinate with engineering team to reserve and learn how to set up our in-vehicle carsharing hardware product, identify Ridecell white label apps to test with, reserve a QA environment to ensure that the service would not be disrupted while in use, and gain buy in and support when the research team traveled onsite in case we needed to troubleshoot stability issues.

• Other scoping and research was conducted to set up the research trip, including:

  • Scoping and managing the research budget including: travel costs, recruiter costs, respondent incentives, vehicle rental, office space rental, parking garage payment.

  • Worked with the Ridecell legal, insurance, and procurement teams to ensure regulatory, client, and company compliance.

  • Recruiting Ridecell team members to support the research work in-field.

  • Identifying, selecting, and managing research recruiting vendors, and developing user research assets such as screeners, discussion guides, legal documents (NDA and recording releases), and incentive payment receipts.

  • Other research and setup for the research project, including renting a similar vehicle through Turo, selecting a comparative parking garage in an area near to a Penske Dash partner garage, reserving a nearby Breather office space for part of the testing.

Research In-Market

• Conducted 17 user research in-person interviews with in-field usability research tests, at 2 hours per respondent.

  • Respondents were limited to the markets of Penske Dash in Washington D.C. and Arlington, Virginia, and were segmented according to 4 main types:

    • Intender (previous car renter from a traditional car rental agency like Hertz, Enterprise, etc., but not a current carsharing user)

    • Current Penske Dash Users

    • Competitor Users (does not use client product Penske Dash, but does use competitive products like Car2Go, Free2Move, Zipcar, etc.)

    • Former Penske Dash Users (have used it at least one time before but have not used it in the past month or longer)

  • The research structure was as follows:

    • User Research Interview. The respondents met the Ridecell user research team at the Breather office location and were interviewed to gain insights about their background, vehicle rental and carsharing experience, etc.

    • Simulated Lab Usability Testing including Task-Based Analysis. The respondents were asked to complete a series of tasks while in the office space, including registering for the service, reserving the vehicle, and reporting damage on the vehicle via the in-app damage reporting flow. Respondents were also prompted to gain feedback on specific features, placement of buttons, terminology, etc.

    • In-Field Usability Testing including Task-Based Analysis. Respondents were asked to locate the test vehicle on foot using the Ridecell white label app. The test vehicle was parked in a nearby parking garage that mimicked the Colonial partner parking garages with barrier arms. During this process, the Ridecell research team asked the respondent a list of questions, and asked them to complete tasks including beginning and ending the rental.

Offering the Service in High Vehicle and Foot Traffic Areas May Not Be Ideal

While it seemed like offering the service in high traffic areas close to multiple modes of public transportation made sense, our research found that these areas in D.C. were often hectic due to the urban design of the area, the types of parking that were available in the area, and the high foot and vehicle traffic. Therefore, there was a high chance that the service may not be utilized if located in those areas.

User Experience Implications

For a user with little driving experience, who may be using the service for the first time, or who may be familiar with the locality on foot but not necessarily via driving, having the service in a high traffic location may cause stress and result in a negative view of the Penske Dash service and brand.

Business Implications

Since the Penske Dash partnership with Colonial entailed that Penske Dash would need to pay for the parking spaces it uses at Colonial locations, it was important that locations with a high probability of utilization were selected, especially during the first phases of the service launch. If the service was launched in a low utilization area, the money paid to Colonial for the ability to park there would be a sunk cost.

Locating the Vehicle is One of the Most Important Parts of the User Journey

Through the research, the team found that one of the biggest pain points the user may encounter upon use of the Penske Dash service was having to locate the vehicle when parked in a parking lot/ garage/ structure.

An example of this was with the Union Station Parking Garage (shown above). It took the research team so long to locate the Getaround vehicle that was reserved for the research test (it took over 30 minutes), that the team was almost forced to cancel the reservation. Despite the fact that Union Station offered both Maven and Getaround services, complications arose because there were multiple parking garages, multiple entrances to the parking garage containing the Getaround cars, lack of knowledge from the staff that the carsharing service even existed in their facilities, lack of signage leading to and within the garage, etc. In the end, it was decided that the Union Square Parking Garage should be excluded from the Penske Dash service due to the difficulty in being able to find the vehicle.

User Experience Implications

By clearly communicating the positive points and pitfalls of competitor services across different types of Colonial parking, we were able to give details to the client, outside of the Ridecell products, as to some recommendations to make it easier for users to get over the initial hurdle of finding their car.

Business Implications

Since the business revenue is driven by vehicle rentals, if a vehicle is not rented because it is difficult to locate, the ROI on that particular vehicle would be low. At worst, the underutilized vehicle may in fact cause the service to lose money as no money would be generated to offset costs, and more costs would need to be incurred to have someone come to rebalance the vehicle (move the vehicle to a more desirable location) and/or have to pay parking fines as there are often limits on how long a vehicle can be parked at a particular location on the street. By putting focus on these initial steps of the user journey, the possibility of low vehicle utilization because the renter simply couldn’t find their car would be greatly reduced.

The Driving and Parking Experience Should be Considered

In addition to the physical location of the Colonial parking garage/ lot/ structure, the user experience of actually driving the car in and out of the space, as well as finding where to park, needed to be considered when considering partner locations for launch. This not only means that the size and placement of the parking spot needed to be evaluated, but also the surrounding architecture of the parking space, wayfinding for driving within and exiting/entering the garage, and instructions and availability of support staff when confusion arises.

User Experience Implications

A feeling of intimidation may arise from just the prospect of conducting difficult driving maneuvers to get in and out of tight parking spaces, and may cause a user to cancel the reservation. In the future, a user with minimal driving experience may be intimidated with the prospect of driving out of or parking within a tight parking spot and so this may impact their decision to rent vehicles in specific parking lots/ garages/ structures with these features.

For example, during the research trip, one Colonial garage that was evaluated had parking spots aligned in such a way that it took a 5-point turn just to drive out of the spot, even though the driver was highly experienced. The vehicle that was rented had a large dent in the side from a previous driver who had damaged the car trying to get out of the spot, which had a large column to one side (shown above).

Business Implications

Since each parking space had to be paid for by Penske Dash to Colonial, it was important that the spaces be used not to park a single vehicle for long lengths of time (which pointed to low utilization) but for numerous shorter lengths of time (high utilization).

Additionally, a difficult parking and driving situation meant that the Penske Dash vehicle was more likely to end up damage, thereby increasing the maintenance cost of the vehicle if it was repaired, and damaging the brand image if left unrepaired but still available for public use.

The Registration Flow is OK and Doesn’t Need to be Revamped

6 months before the Penske Dash post-launch research project with consumers, I conducted internal Ridecell interviews where I spoke to 32 people from every department within Ridecell to scope out potential research work for the UX research roadmap for the following year. A common theme that came up during these interviews was the idea that the Registration flow of our white label mobile app (and therefore the registration flows for all of our consumer user-facing mobile apps) needed to be updated in a big way. I decided to take the opportunity of the consumer user research trip to test the usability of the Registration flow and understand what target consumers thought about aspects like terminology, features, etc.

We found that aside from certain terms that needed to be changed due to confusion about their meanings, and concerns about privacy and verification (as driver’s licenses and faces needed to be scanned, and driver information needed to be verified by a third party), not much actually needed to be changed about the registration process.

Company refocus

As the client was wary in terms of anything that would negatively impact the brand, especially in terms of car damage and the overall user experience, the findings from the research impacted the selection of specific parking garages, especially for use cases like when overflow parking is needed.

On-Site Penske Dash Parking Signage

Designated parking spots and clear Penske Dash signage at each spot were being discussed, but the need for them was made clear through the on-the-ground research and creation of deliverables such as this journey map and presentation.

New Penske Dash App Feature: Parking Pin

For Ridecell, the research findings meant that new features needed to be developed to aid in the wayfinding of the vehicle.

A Parking Pin was created to indicate the location of the particular parking lot where the vehicle was located. On the technical side, since the service was not station-based (meaning that the vehicles were not associated with one Colonial garage/lot/structure but can be parked at any Colonial parking locations), the Ridecell team was limited in their ability to show the vehicle pin as “absorbed” into the parking pin at this time.

In-App Parking Information Sheet

As the comfort level and perceived convenience of different parking lots/garages/structures is largely subjective, the way the Ridecell team addressed these issues was through the provision of more detail in terms of parking location information. This way, the user would have key pieces of information they would need when it came time to find a place to park.

These included:

• Parking location photos on the Parking Information Sheet

• Wayfinding information with directions to the lot/ garage/ structure entrance

• Icons indicating parking features such as:

  • Hours with Attendant or Valet presence

  • Wheelchair Accessibility

  • After Hours Access

• Usability Instrumentation

UX Research Project Leader

I led UX Research for the Penske Dash service, which included the scoping and planning of the research projects, Ridecell team training, research findings synthesis, research materials and deliverables creation, findings communication, and represented the user in product, business, and design meetings.

Research Project Creation and Planning

I worked with the Customer Success Manager and Launch Manager to identify the scope of the Colonial parking lots/ garages/ structures, as this information came directly from the client. I identified the variations of the different parking types and cross-checked them with existing competitor carsharing services that would be available during the times of our research trip to create the research itinerary. I also created the in-field data collection and filing method.

Research Team Training

I had created a research training document that included clear guidelines as to the roles that each person on the team had to fill, what needed to be recorded and how, what the itinerary for the week was, and where to upload the research findings files. The people on the team were myself, a Customer Success Manager, and Launch Manager. The other team members were not trained in design research, so more emphasis was put on how to think through the experience of the competitor services from the viewpoint of multiple personas.

In-Field Research and Contextual Interviews

I led the team in conducting in-field research where we evaluated carsharing competitor services at different Colonial parking lots/ garages/ structures and did intercept studies with Colonial parking attendants and valets while on duty at their parking locations.