Case study 03

SmartGate

Zone-based gate seating for Phoenix Sky Harbor International Airport, built around traveler choice.

Bottom line up front

The problem
  • Phoenix Sky Harbor Airport serves about 50 million passengers a year, and its gate seating is rows of identical chairs.
  • So travelers make their own boundaries: headphones on, eyes down on a phone, and a bag on the seat next to them.
  • My field research found that bags alone held about a quarter of all seats, and the empty seats between strangers went unused too.
  • People stand along the walls while the room looks full, worn down by a wait spent guarding their space.
  • For the airport, that is seating it already paid for, sitting idle at the hours it matters most.
The solution I designed
  • SmartGate, a gate split into Quiet, Standard and Social zones, so each traveler picks the kind of space they want without negotiating with strangers.
  • Sensors can tell when a seat is taken, but they cannot tell who is in it.
  • The room’s signage and lighting show how full each zone is.
  • An optional phone app adds detail.
My role
Solo designer, on a self-initiated concept
Timeline
Fall 2025 to March 2026
Team
Just me, with Claude as an AI design partner
  • Took it from field research to a designed gate and app
  • Field research inside Terminal 4: observing gates and interviewing travelers
  • Research models built from it: two empathy maps, a journey map and nine traveler identities
  • The gate environment, the system behind it and its companion app
Key decisions, and the evidence behind them
  1. 01Physical first, app optional
    From the passenger empathy mapAnxiety spikes the moment a crowded gate comes into view.

    So the room answers first, through seating, lighting and signage. The app stays optional: a traveler with a dead phone still needs a seat.

  2. 02Designed for the gate agents too
    Inferred from my seat countsAgents have no data on the gate’s own seats, so they judge crowding by eye.

    So the system gives gate agents a dashboard showing how full each zone really is.

  3. 03Left out seat reservations, social matching, pods and a quiet terminal
    The rule I designed byDesign for choice, not control.

    Each one excluded travelers, edged toward surveillance, or cost more than zones that do the same job.

ToolsFigma · Claude Opus 4.6 · Google Gemini · Nano Banana
01
Introduction

The smart IoT gate environment that turns empty seats into available ones

Design targets
  • Free up the roughly 25% of seats held by a bag
  • Remove the 6-step claiming sequence travelers perform today
  • The gate reads at a glance in person, with the app strictly optional
The claiming sequence, reconstructed step by step from field observation. Every step is work the environment could be doing instead.
Read the diagram as text
  1. Enter the seating area, to find seats that meet their need for space and comfort: scan the seating, spot the empty seats that are socially available, look for end seats and buffer seats.
  2. Finish scanning, to pick a seat by personal space and safety, or decide to stand.
  3. Sit down, to set up a personal space zone: the main bag on the next seat, smaller bags between the legs.
  4. Bags in place, to get as much space and comfort as the seat allows: turn toward the view, settle in.
  5. Body in place, to signal they’re not open to talk: phone out, headphones in, eyes on the screen.
  6. Boundary set, to stay unavailable for the whole wait: avoid eye contact, stay absorbed, listen for boarding.

Choosing a zone before walking in, and saving it for next time

When a zone fills, the app says so, then walks the traveler to boarding

Try the prototype yourself.

Open the prototype in Figma (opens in a new tab)
02
Video

Introducing SmartGate.

A quick walkthrough of the gate in action: the three zones, the sensing that reads them, and the companion app that follows a traveler from choosing a space to boarding.

Read the transcript

Hi, my name is Jarel. If you’ve ever flown, you already know this feeling. You get to your gate, you scan the room, and you’re looking for the one seat that isn’t next to anybody. You put your bag on the seat beside you, you put your headphones on, and you hold that little bit of bubble space until they can call your group. Here’s what I found when I actually studied this: at a busy gate, roughly 40% of the seats sit empty, not because there’s not enough seats, but because people are protecting space with their bags and their bodies while others stand along walls. Everyone’s doing the same quiet work of managing boundaries alone, with no help from the space itself. So I designed SmartGate, and the idea is really simple: move that boundary work out of the traveler’s head and into the environment. Instead of one anonymous room, the gate becomes zones. The app reads the room and tells you where to go. So let’s go ahead and dive in. So this is Gate B22, my flight from Phoenix to New York. Instead of one wall of identical seats, you can actually see there’s three different zones.

A quiet zone, high back seating, subdued lighting, showing 12 of 28 seats available. You have a social zone of communal clusters and charging hubs, and a standard zone. Each one shows live availability, so I’m not guessing. Today I want some peace and quiet, so I’m gonna go ahead and choose the quiet zone. And here you can see what actually makes it quiet: cool dim lighting, white noise, high back pods, and a live seat map.

Now this is important. It’s actually a zone-level estimate. It’s not assigned seating. The sensors count how full the space is. They never track individual people. An environment that reads a room to tell you what it senses and what it ignores. So let’s go ahead and set this as my preference. And SmartGate remembers. Next time I fly from Sky Harbor, the app will actually tell me when the quiet zone has some space. So we’ll go ahead and go back to the zone.

Now watch what happens over time. I step away and the quiet zone fills up, zero seats available, and the app proactively tells me and points me to the social zone, which now has some room. The space is actually responding in real time, and this actually works for boarding as well. Five minutes out, I get everything I need on my lock screen. I get my gate, group, seat, and live zone availability, and when I open it, real-time boarding status shows up: which group is up, how many passengers have boarded, and my estimated board time. When boarding ends, the zones reset for the next flight. So that is SmartGate. This project taught me that the best way to fix a stressful space isn’t a better sign. It’s actually an environment that senses what people need and responds to those needs. Thanks for your time. Thanks for watching.

03
Research

The gate creates the boundary problem, so the gate should absorb it

I ran observation sessions and traveler interviews inside Terminal 4, then open-coded the notes into 40+ topics. Not one of the three findings put the problem in the traveler.

  • 80%Devices as Social ShieldsTravelers observed heads-down in a phone while they waited
  • 40+Coded TopicsFrom open coding of the field notes
  • 9Traveler ArchetypesFrom the Anti-Social to the People Person
The physical model
Gates B5 and B7, mapped seat by seat during observation: about 60% of seats occupied, about 40% of those claiming extra space with bags, and most social activity clustered at the charging station.
Read the diagram as text
  • About 60% of seats were occupied.
  • About 40% of occupied seats had a bag on the seat beside them or between the traveler’s legs.
  • Open seats sat between occupied ones, where nobody would take them.
  • About 80% of people were on a device.
  • Three sustained conversations, most of them around the charging station.
  • Both gates were moderately crowded, with room for both privacy and conversation.
  1. 01

    Social seat scarcity is a design failure.

    About 40% of seated travelers claimed the seat beside them with a bag, which held about a quarter of all seats, and seats between strangers went constantly unused. Travelers judge whether a seat is available by the people around it, and an empty seat between two strangers does not count.

  2. 02

    One layout can’t serve nine kinds of traveler.

    The research surfaced nine distinct traveler identities with opposing needs, from the Anti-Social to the People Person, so no single uniform layout works for every passenger.

  3. 03

    Crowding pushes travelers further apart.

    The fuller a gate gets, the harder travelers work to avoid each other. The moment someone walks into a crowded gate and scans for a seat is where a connected system can help most.

The nine identities
Nine archetypes, grouped by how travelers describe themselves. Each one asks the gate for something different, and several of those asks contradict each other, which is the whole argument against one uniform layout.
Read the diagram as text

I value

  • Spatial Awareness: back-to-the-wall seating, a view of every approach, an easy way out
  • Control > Experience: respect for “closed” signals, choosing when to be social, no forced interaction
  • Every Moment: ways to be productive, time filled meaningfully, no wasted downtime

I travel

  • The Efficiency Expert: minimal wasted time, no reason to arrive early
  • The Comfort Seeker: comfortable seats without armrests, control over temperature, somewhere to actually relax
  • The Helper: seeing who might need help, approaching without intruding

I am

  • The People Person: ways to offer help, connection with other friendly travelers
  • The Observer: clear sightlines, keeping an eye on the surroundings and the gate
  • The Anti-Social: do-not-disturb signals that work, respected boundaries, privacy in public

“Me and the rest of the world are uncomfortable sitting here together.”

A passenger describing an ordinary wait at an ordinary gate. Nobody in that sentence is doing anything wrong, which is why the fix belongs to the room.
04
Process

Every decision was checked against one sentence: move the work off the traveler and into the room

I mapped two people: the passenger and the gate agent. The passenger’s empathy map found the anxiety under the claiming ritual. I didn’t interview a gate agent, so I built theirs from my seat counts and airline-employee forums: agents have no data on the gate’s own seats, so they judge crowding by eye and absorb the frustration when the room overflows.

A journey map put the worst of it in one stretch, from surveying the room to holding a seat until boarding, and that is where SmartGate spends everything it has.

Design focus

Travelers at Sky Harbor gates spend real effort negotiating who sits where, so move that work off the traveler and into the environment.

05
Design

Three zones let travelers choose the kind of space they need

The design focus applied three times: to the room, to the signals the room gives off, and to the app that reads them. I generated the renders with Nano Banana to illustrate the layout.

  • 3ZonesEach tuned to a different cluster of identities
  • 9Identities ServedEvery archetype has a zone that fits it
  • 8App ScreensOptional detail, for travelers who want it

The room explains itself before anyone opens an app

Three zones, each tuned to a cluster of the nine identities. Seating geometry, lighting and sightlines carry the meaning, so a traveler can pick a zone just by looking at the room. The archetypes under each zone are the ones whose asks that geometry answers.

Quiet Zone

  • High-back modular seating
  • 45° angled orientation
  • Integrated side panels
  • Built-in power + subdued lighting

Designed for: Anti-Social · Observer · Comfort Seeker · Control > Experience

Standard Zone

  • Improved buffer spacing
  • End seats maximized
  • Wall positions prioritized
  • Clear sightlines to gate

Designed for: Efficiency Expert · I Value Every Moment

Social Zone

  • Communal seating clusters
  • Shared charging hubs
  • Destination displays
  • Conversation-friendly layout

Designed for: People Person · Helper · Spatial Awareness

As the gate fills, the room says so

The zones are legible when the gate is calm. The harder case is a gate filling up, which is exactly when a traveler is scanning and least able to judge. Sensors read occupancy, and the signage and lighting update so the room reports its own state.

The environment went through three passes: the full system mapped onto the gate, a clean render, then a revision after design feedback, which added white noise over the Quiet Zone, an acoustic wall, and charging in every zone.

V2, revised after design feedback: white noise emitters over the Quiet Zone, a soft-surface acoustic wall, and charging towers added to every zone.

A step back from the renders, this is the logic that runs the gate. The room works for everyone by default, and the app adds optional detail. Sensors count occupied seats and identify nobody. The environment shifts with the crowd: it stays passive while a zone is quiet, turns active as the zone fills, and converts the zones into boarding groups once boarding is called. The same feed powers three tiers: the physical room for everyone, the app for travelers who opt in, and a gate-agent dashboard passengers never see.

The system behind the room: what the gate senses, the density-responsive logic that decides when to step in, and the three output tiers, physical for everyone, the app for those who opt in, and a gate-agent dashboard passengers never see.

The app adds detail, and is never required

Everything above works with a dead phone. An earlier draft had no app at all: “No apps. No wearables. No profiles.” The final design added one only as optional detail, for travelers who want more than the room can say at a glance: which zone has space now, and when to move for boarding.

Design for choice, not control, so four ideas didn’t make it

  1. 01

    Full-enclosure pods.

    They would cut the gate’s capacity and block sightlines to the boarding door.

  2. 02

    App-based seat reservations.

    They add friction, and they shut out travelers who don’t use the app.

  3. 03

    Gamified social matching.

    It edges toward surveillance, which contradicts a system people opt into.

  4. 04

    A separate quiet terminal.

    It would take a major build-out to do what zones do inside an existing gate.

06
Reflect

What a gate taught me about designing environments

  1. 01

    The environment was the user problem.

    Every pain in the research traced back to the space itself: fixed forward-facing rows, clustered outlets, zero wayfinding for social availability. The whole concept came together once I treated the gate itself as the thing being designed.

  2. 02

    Design for the gate agent too, or the system fails.

    I never interviewed a gate agent, but my seat counts made their side plain: no data on the gate’s own seats, and the frustration that lands on whoever is at the podium. The gate-agent dashboard exists because an environment that helps passengers while leaving agents guessing solves half the problem.

  3. 03

    Ambient first, screens second.

    The zones are designed to speak for themselves. The app adds detail only for travelers who want it. In a space where many people never open an app, the room itself has to be the primary interface.

What I would do differently

  1. 01

    Prototype the room before the app.

    The clickable prototype covers the companion app, but the core bet is spatial. I’d test zone legibility with a scaled physical mockup before touching another screen. A pilot gate would then answer the airport’s question: how many more seats fill at peak than at the gate next door.

  2. 02

    Validate the archetype-to-zone mapping.

    Each zone serves named archetypes from the research, and that mapping is a hypothesis. I’d recruit travelers across the 9 identities and watch which zone they actually choose.

  3. 03

    Count the seats people will actually take.

    The system design already calculates socially available seats, but the app screens show exact empty-seat counts. They should show the socially available number, or travelers will distrust it for the same reason the room fails today.

  4. 04

    Say the privacy story out loud.

    The system is built not to know who anyone is, but the environment never tells travelers that. A system reading a room full of people should say what it senses and what it never stores.

Contact

Open to product design roles and relocation
Phoenix time
--:-- MST
33.45° N, 112.07° W
Built with
Figma, Next.js, three.js, Claude
WCAG 2.2 AA, light and dark
Changelog
Sonoran Ops v1
Nov 18, 2026