Stress-free Parking @ Virginia Tech: VT Intelligent Parking System
🅿️

Stress-free Parking @ Virginia Tech: VT Intelligent Parking System

Skills
User ResearchUX DesignUsability
Tool
Balsamiq

At-a-glance

VIPS is a mobile app that communicates real-time parking lot availability to Virginia Tech students, faculty, staff, and visitors.

image

Current situation

Virginia Tech has 37,000+ total enrolled students, and 1,000+ full-time instructional faculties. Virginia Tech also has a Top 20 College Football team and welcomes 400,000+ fans at Lane Stadium per season. A good parking experience on the VT campus is important to students, faculty, and visitors. However, there is not an easy-to-use information system that communicates all the information users need. Virginia Tech Parking and Transportation (VTTI) is seeking to retain customers with better service to the end-users.

HOW MIGHT WE...

create a friction-free parking experience for everyone who parks at Virginia Tech campus?

I came across the project's initial idea when I went to the school library on a football game day at Virginia Tech. What I remembered more than the notes I reviewed that night was the terrible parking experience - some of the lots I usually went to were either closed or became unavailable for my parking permit type due to this special event, and I wasn't aware: Where can I park on campus now?

With my frustration as a user and passion as a UX designer, I reached out to the Virginia Tech Parking and Transportation (VTTI) and teamed up with 3 other teammates. VTTI became our client and worked with us on improving the current system.

What we did

We designed a mobile app, VIPS, that serves as an integrated information-gathering system to improve user experience in space finding on VT campus. We conducted 10+ user research (evaluations, interviews, and observations) to discover insights that re-defined product direction and re-prioritized features. A mid-fidelity prototype and usability testing scripts were delivered on time to the client.

EMPATHIZE

Although I already had an initial “personal pain point” as an end-user, I knew in order to reduce my own bias and find the right problem to solve, I needed to hear what the other actual users had to say.

What I wanted to learn:
  • How do users utilize and interact with the current VT parking system?
  • How are their experience and opinions regarding parking on VT campus?
  • What are the actual pain points the users have that we can act on?

01 Evaluation of the current system

We decided to start by evaluating the current system to help us scope the project and design further user research plans.

Key learnings:

  • Information is scattered through different websites and maps
  • There are conflicting or obsolete information exists on the websites

02 Interviews

Interviews were conducted with 10 participants who were current students or faculty and staff of Virginia Tech who had experienced parking on campus. In a 30-min moderated interview, they reviewed their behavior, habits, attitude, and experience of their daily commuting and parking around VT campus.

Our team also interviewed and observed 5 parking assistants of VTTI regarding their direct communication with the customers.

🕸️
“I hate going back and forth between websites, zooming in and out a lot on the map. ”
🤔
“There were emails telling me which road and lot are closed? I didn’t know, or maybe I didn’t check. ”
🏈
“I don’t follow the sports schedule, sometimes I don’t even know it’s game day but the lot is closed. ”
😕
“I don’t trust VT parking websites because I saw conflicting or out-dated information there before.”

03 Observations

In order to further understand users’ thinking processes and behavior, we performed 5 user workplace observations by setting up a simulation scenario and employing Think Aloud protocol. The observations revealed more hidden details of pain points that interviews didn’t tell us.

Key Takeaways from observations

  • Having to look at multiple web pages for information needed is “frustrating” to the users.
  • It requires an excessive number of steps/clicks on each website to obtain the information.
  • When users could find available spots in the parking lot, they would either “shark” (driving around over and over in the currently filled parking lot to find a spot), or do the cumbersome information gathering again to try another parking lot.
⬅️ CLICK TO SEE Screenshots from observation recordings
image

DEFINE

The research notes were broken down into 200+ atomic sticky notes and synthesized using Affinity Mapping.

Organizing these notes from the bottom up, common behavior, pain points, themes, and shared requirements of features were revealed and generalized from individual instances to broader usage themes.

Affinity map of interview responses
Affinity map of interview responses

Key findings overview

My initial personal pain point is consistent with our research finding, but we definitely learned a lot more and were able to empathize with our users better. These key learnings were then transformed into actionable insights for design.

  1. Most of the frustrations happen during Information Gathering:
  2. Which lot am I allowed to park (considering: current day of the week and time; my permit type; the special event and/or construction going on) ? ”
  3. A lot of the participants mentioned real-time parking spot availability
  4. Metered parking is helpful, but paying and trying to remember the time limit is causing more trouble
image

Keywords of the requirements

🕰️
Real-time information

1. All the information about route and lot closure, construction, and game day regulation are displayed up-to-date.

2. Provide real-time parking spot availability

🦾
Integrated system

Instead of looking for information on multiple web pages and through various medium, one integrated system streamlines the process, increases efficiency, and eliminate confusion caused by inconsistency.

🔍
Tailored information

Users don’t need to process and filter all those information by themselves:

🚘
Safe to use when in the vehicle

Minimize the steps and clicks required

IDEATE & PROTOTYPE

We did paper wireframing first and built our prototype using Balsamiq.

The pandemic suddenly disrupted our timeline and plans for testing and iterations - we had limited time and couldn’t do testing. We still created usability testing scripts and managed to perform pilot testing with 2 users to make modifications.

image

Features highlight & Design decisions

0. [Pivot] Why a mobile app?

Initially we wanted to redesign the current system, i.e. a set of web pages. However, our research shows that users utilize their mobile phones much more often than desktop devices when looking for parking information, especially when they’re in the vehicle/driving.

Moreover, although the websites are responsive, the inherent characteristics of this info-gathering process make it even more difficult to navigate on a smaller screen.

Referring to our interviews and especially observations, web pages are not the best approach here. Thus, we decided to pivot from redesigning the current websites to designing a mobile app instead.

image

1. Integrated system with tailored information for each user

Instead of having to navigate between multiple web pages or checking emails, VIPS is an integrated system that provides up-to-date information and tailor that for each user. User can also access upcoming parking changes of their saved parking lots fast and easily.

image

2. [Cost constraint] Real-time parking spot availability estimation

HMW... provide information on real-time parking spot availability?

We first thought of the use of technology like Internet of Things (IoT) sensors for precise real-time information of parking space availability. However, considering the limited budget, it was not feasible due to the high cost of the system and sensors. We had to brainstorm alternative solutions to fulfill the user’s needs while considering the client’s constraints.

Our solution is to determine and show average popularity by collecting aggregated data from users over time. Each time VIPS navigates the user to the destined parking lot, it asks the user if they were able to find a parking spot. The feedback collected is analyzed to generate trends on estimated availability to inform other users.

image

3. Upgraded metered parking experience

Users can pay with VT campus wallet (Hokie Passport) or credit card if they run out of coins. VIPS also help the user set notifications before metered parking expired so they would never forget again!

image

4. Other Highlights

Signing in with Virginia Tech account would be convenient to users because VIPs can recognize the permit type, recommend parking lots based on that, and link to the campus wallet to be paid with (Hokie Passport).

However, since finding parking is often urgent, we also provide the option to skip sign-in so that it won’t be an obstacle when the user needs immediate access to the information: they can still manually use filter and search settings to find where they can park.

Visitors can also utilize VIPs to see the parking lot information quickly, or get directions to the visitor center and purchase a parking pass.

image

Next Steps

  • (More) Testing and iterations
  • Refine Driving Mode
  • Design for accessibility
  • In-App Tutorials to increase product adoption

Lessons Learned and reflection

  • Detachment from my own bias & find the right problem to solve

The project started initially with my personal pain points, however, I cannot stand for all the actual users. Conducting various research let me truly emphasize with the users and find the right problems to solve - there were so much more than my initial opinion! Those insights learned from user research made sure we have a smooth process and were the cornerstone of an evidence-driven design.

image
  • Time management & adapt to changes

Our project’s initial timeline and plans for testing, evaluation and iterations were significantly disrupted by the pandemic, but we still managed to finish it and deliver on time. We talked to our client and mentor to make appropriate modifications on the timeline and deliverable details. Although we couldn’t do testing, we still design the usability testing and managed to perform pilot testing at least. I’m glad that we act on the changes quickly and successfully finished on time

  • Explore possibilities aligning end-user's needs and business vision

Collaborating with our client, it was both challenging and fun to work with the constraints. I learned to think backwards from the seemingly unfeasible user needs to find the fundamental pain points. We then explored various ideas and found alternative solutions that solve user pain points with limited resources and budget.

What would I do differently?

Don’t skip Lo-Fi prototype

Although our client only asked us to provide wireframe or lo-fi prototype due to the timeline change, we still wanted to deliver a higher fidelity one. We skipped Lo-Fi prototype and rushed in order to finish before the deadline, and didn’t have the chance to check and test functionality before diving into the visual appearance design.

Spend more time building design system

Creating a comprehensive design system beforehand would save us hours of time and make it easier to stay consistent as a team of four. Also, we could’ve spent more time exploring visual design possibilities including color schemes, fonts and more modern UI that accords with iOS&Android guidelines.

Be more agile and do small chunks of testing early on

Being more agile from the beginning would help us do more iterations and quickly identify issues even with the disrupted timeline. If we planed ahead, some quick A/B testings and usability testings would reveal room for improvement on both functionality and interactions that contributes to a better design overall.