Timeline

October – November 2025 / January – February 2026 (10 weeks)

Role

Solo UX Researcher & Designer | MHCID Class

Tools

Figma, Miro

Methods

Observational Field Studies, Ethnography, Interviews, Transcript Coding, Affinity Diagram, User Empathy Maps, User Journey Map. Conceptual Models, Prototyping


problem

Drivers hesitate identifying terminal entrances and park for convenience at curb spaces

Most drivers find trouble in identifying the correct places to go, hesitating on turns and crossing over quickly to lanes. This creates a snowball effect that backs up cars and forces traffic. 

Parking in the first spots that drivers see stems from close range identification of availability and convenience. Crowding cars to park in the first section of Curbside can block up to all lanes of traffic, also affecting outer lanes of travel.


solution

Drivers NEED convenient system guidance

Drivers need easy access to terminal entrance points and curb access to improve the efficiency of the system. Integrating trackers into the structural entrances and syncing with vehicle GPS tracking allows the user to know how far they are from the nearest tracker, greying it out when a sensor is passed.


The Inspiration Quote

“No one knows how to move forward, everyone just stops.”

Upon my second visit, I overheard a ground traffic control worker laughing with one of her co-workers. She looked at a group of us in passing, saying these words, and we all laughed in unison. That was when the lightbulb hit, and I ran to speak with her again.


Interviews + Observational Field Studies

Workers and drivers need a system that supports their actions and guides them

On three seperate days, I drove to SFO Airport Departures level and observed, majorly Terminal 3 and partially Terminal 1 and 2, for a couple hours at a time. One of my interviews with a very kind ground traffic control worker was on the second observational day. The remaining interviews with passengers and drivers were on various days, some on-site and some outside of the area. For convenience, I’ve highlighted the major quotes and where they’ve come from corresponding to 3 out of 5 total insights I gained that contributed to the final UI solutions. For further insights and details, feel free to view the slide decks below.


Affinity Mapping

Interactions snowball into traffic backup, safety hazards, and system delays

Themes of emotional behaviors impacting driver actions, worker versus driver moderation, structural control and pain points, convenience versus system efficiency, rideshare service interference, and traffic causals all reside within the system. Each portion of data interacts with one another under multiple levels of themes. Questions are posed for each section and similarity to help understand how drivers feels and how it correlates to the observations I made during my ethnography and field studies.


Work Models

Perspectives show pain points

Visualizing three work models helped me grasp the perspective from: Passengers, Drivers, and Workers. A physical model laid the architectural system in front of me, mapping out each bus stop and shuttle location that could impact the flow, and visualization, of the system. A sequence model gave me insight into breakdowns when passengers need information to continue their route smoothly, especially in rapid succession. An identity model utilized quotes from my interview and ethnography study with a ground traffic control worker, breaking into how the system runs, how knowledgeable drivers are of the laws, and how the emotional direction of drivers all impacts their duties.

If you’d to see full detailed reasoning and insights for each model, please see this Work Models PDF.


User Empathy Maps

System helps the workers that help the drivers

Synthesizing data from interviews and observations helped formulate a user empathy map for both a driver and a worker. To understand what they hear, feel, think, say, do, and see impacts their goals for a system and the pain points that they currently face. This narrows down the problems we need to solve to account for both sides of the system.


User Journey Map

I broke down the driver’s journey into six parts of a series, utilizing quotes and concepts from each interview to better understand their actions, emotions, pain points, touch points, and opportunities for improvement in accordance to each part. This gives me a better layout to learn the process of the user in full, in accordance with work models, to map out a solution that achieves all aspects of the full experience. I chose to use the perspective of the driver for this user journey map as they interact the most with the system as a whole.


Design Focus Statement

How might we create a navigational system that supports drivers in finding the right terminals and alerts drivers of available curb space through minimal UI and geofencing technology?


Environment System Diagram

Covering three major groups of insights, I forged a system diagram of a potential solution system that would solve for multiple problems, including a seperate zone for rideshare services to not conflict with personal drivers. It creates decision points for the system to determine if a vehicle is near a terminal entrance point and if curb space is available. The system input and output operations change based on real-time data and I’ve added the potential involvement of ground traffic control workers in this new system.


Conceptual Model

Translating the system diagram into a conceptual model helps layout a more specific method to achieve this new system. Entrance sensors and existing vehicle GPS technology help match distance away on map software. Curb sensors are built overhead to track if a car is currently within the space, sending information to the driver once they’ve driven into a terminal to forge a zone that is available and guide them with time estimation.

Availability can also be estimated and this will give information to the driver that a second lane drop-off may be the most viable. A timer system is also implemented within the map software and car dashboard UI to grant five minutes of drop-off time. If time is exceeded, the ground traffic control workers and drivers are both notified, warning the driver and prompting them to exit the SFO Airport.


UI Screens

How can SFO Airport solve this?


Prototype

This is a working Figma prototype of SFO Airport’s potential UI that would integrate into existing car dashboards and navigation mapping software. Most screens are automatic, but some require touch to continue with the process. Please keep in mind not every feature is available. It is primarily designed to test a full process of entering and exiting the departures level terminal experience.


Slidedecks


Reflection

What Did I Learn and What Would I Change?

After completing the first phase of this project, I had ended it off with an opportunity map that I did not list here for storytelling purpose. The opportunities I had listed became more so irrelevant to the digital landscape that I committed to in the second phase of designing. The major lesson I learned from this is utilizing the data that I accumulated and learning to find which path to move forward with. My opportunity map ended with around 20 opportunities to work through with several quotes and observations for each one, narrowing down to 6 main ones that tied to driver visual guidance, AirTrain transportation improvement, and rideshare service relocation.

This project pushed me to trying many new methods including ethnography with a ground traffic control worker and observational field studies of the full location. Most importantly in this, I had learned to understand the most important questions to ask when interviewing another person. I had formulated an interview guide with a list of questions where some drivers did not connect to some of the questions I had asked. Especially during my worker interview, I dropped most of my guide to pursue what they were speaking on rather than to ask from my own perspective, as they were more of an expert in the field. I started to grasp better ways to pay attention to the phrasing or words used and to reply with language that they were familiar with. This led me to much more insight that still related to topics, but answers I had not accounted for when originally creating questions. I learned a lot more about the inter workings of the system, such as groups of flight times being scheduled and waves of traffic forming an hour prior to departure. I also came across an entire subsection of rideshare services who hide their side stickers to appear as usual drivers, working around the laws and rules that were set up for them.

During the second phase where designing started to take place, I had been torn between multiple insights regarding a need for visual guidance on the curb, on the lanes, and a seperate issue regarding rideshare services and other shuttles or bus stops needing to be rellocated according to the ground traffic control worker I interviewed as well as a baggage checker who noticed the traffic delays caused when a passenger XL shuttle is placed at Terminal 3 rather than up in the sky bridge and parking lot structure where the rest of them reside. My decision brought me to addressing vehicle types within my design for a potential area change for these drivers. If the project continued further and I had connected with SFO Airport, the decision to change architecture would fall into their hands, so I learned to focus on only what I could fix now for the time being.


more projects I’ve worked on