CASE 03: JFK T4

INTRODUCTION

JFK Terminal 4 asked Ronik to redesign its digital experience. As the agency’s co-founder and Managing Director, I led the work across three channels (the website, the main arrivals board, and in-terminal kiosks) for the largest terminal at JFK and the only privately owned one, which serves over 21 million travelers a year. The brief was anchored in the terminal’s mission to “Guide & Delight.” Early in discovery, their team told us that “once someone enters an airport, their reasoning skills go out the window.” That line shaped everything that followed.

Environmental photography of the terminal

The terminal had just completed a rebrand. Our job was to carry that new identity into a digital experience that worked for every audience in the building, from departing passengers to the staff who publish updates.

DISCOVERY & STRATEGY

Terminal 4 is a mile long. That physical fact shaped every part of the digital strategy.

Five Borough Food Hall, JFKT4

Research Approach

Discovery covered both the physical terminal and its existing digital systems. The research included:

• 100+ passenger intercept interviews and surveys
• Stakeholder interviews with terminal operations, airlines, and retail tenants
• Multiple site visits during peak and off-peak hours
• Analysis of existing digital infrastructure and security protocols
• Review of passenger flow data and common pain points

A wall displays our organized user research notes.

The research surfaced distinct needs for travelers and for terminal staff.

Key Findings

Physical Context:

• Terminal’s mile-long layout created distinct zones with different user needs
• Security checkpoints created natural bottlenecks affecting passenger behavior

User Segments & Needs:

1. Departing Passengers
   • Primary concern: Time management through security and to gate
   • Need: Real-time wait times and gate information
   • Context: High stress, limited attention span
2. Arriving Passengers
   • Primary concern: Ground transportation and exit routing
   • Need: Clear wayfinding and transportation options
   • Context: Fatigue, unfamiliar environment
3. Meeters/Greeters
   • Primary concern: Accurate arrival timing
   • Need: Real-time flight status updates
   • Context: Extended waiting periods, need for amenity information
4. Terminal Staff
   • Primary concern: General communications
   • Need: A content management system for rapid updates
   • Context: Various technical skill levels

Technical Constraints

The terminal’s existing infrastructure set the boundaries. Security sensors exposed real-time wait times through an API, but security policy required on-premise hosting behind the terminal’s firewalls, so our usual cloud-based approach was out.

• Security requirements mandated on-premise hosting
• Custom API integration for legacy systems
• Fault-tolerant handling for real-time data
• Multiple display technologies with different capabilities

Pulling It All Together

These findings guided the UX, design, copywriting, content, and development work that followed. The solution had to do three jobs at once:

• For travelers, give clear guidance in the terminal’s warm, helpful voice and its bright new visual brand
• For staff, provide a tool they can update quickly as messaging changes
• For operations, connect the channels so one system carries both marketing and customer service

Multi-Channel Implementation

The solution covered three channels, each with its own context:

Design Brief document created after the project's research phase. Used as a design bible for the remainder of the project.

Web Platform

Strategy:

• Mobile-first design approach
• Progressive enhancement for feature phones
• Offline capabilities for limited connectivity
• Multi-language support framework

jfkt4.nyc homepage hero visual design

jfkt4.nyc homepage hero wireframe

jfkt4.nyc sitemap

Results:

• 25% reduction in customer service calls about basic terminal information
• 3x increase in mobile engagement
• Successful handling of peak traffic during holiday seasons

In-Terminal Kiosks

We designed and built touch-screen directory kiosks for the terminal floor, reusing the website’s design language and codebase. Content and interaction were cut down for travelers on the move, who want one answer and then want to keep walking.

Kiosk interface screens

Strategy:

• Location-aware content prioritization
• Simplified touch interfaces for stress contexts
• Real-time synchronization with central systems
• Fault-tolerant offline operation

Implementation:

• Custom touch-optimized interface
• Cached data architecture
• Hardware-specific optimizations

Arrivals Hall Flight Information Display

The main flight information board in the arrivals hall was the centerpiece. Thousands of people stand under it every day waiting for arriving passengers. We rebuilt it around a clear visual hierarchy so flight statuses can be read at a glance from across the hall, while keeping the terminal’s brand identity. The layout had to hold international flight tracking, many airlines, and real-time updates at once. Typography, color, and contrast were chosen for distance legibility first, and then for some of the “Guide & Delight” warmth.

The video wall in the arrivals hall

Strategy:

• Modular display system supporting multiple layouts:

  • Standard flight information displays
  • Weather updates and alerts
  • Terminal messaging and announcements
  • Custom layout configurations for different operational needs
• Real-time data integration from multiple airlines
• Emergency override capabilities

Implementation:

• Custom layout engine for complex flight data
• Fault-tolerant data handling
• Remote management system

Results:

• A board people can read from across the hall that still carries the “Guide & Delight” brand

The redesigned arrivals board in use

Design System Development

Designers, developers, and content strategists built one design system for every terminal touchpoint. The work meant balancing stakeholder requests, technical limits, and how the terminal actually operates, without slowing the team down.

Strategic Leadership

Team Structure & Development:

• Led 8-person core team (4 designers, 4 developers)
• Established early engineering involvement for feasibility validation
• Set documentation standards so knowledge survived handoffs

Stakeholder Management:

• Conducted bi-weekly executive reviews with terminal leadership
• Coordinated with terminal technical teams for data integration
• Managed relationships with third-party vendors
• Facilitated workshops between client and design teams

Brand Integration & Typography

Early on we found a gap. The custom typefaces from the rebrand were not web-ready. Rather than fall back to a substitute font, we made the case for commissioning a complete web typeface system.

The argument was operational. Without web fonts, every heading change would need someone in Adobe Illustrator. Once we showed what that would cost per content update, the terminal approved the investment. The web fonts also brought the digital channels and the printed marketing into line with each other.

Component Architecture

The system adapted to each channel without losing its identity. The icon set became the most recognizable piece, with a playful illustrated style. The loading animation on the flight information screen, for example, is a smiling plane flying over clouds.

Technical Implementation

I ran the technical side at Ronik. I started with interviews with the terminal’s technology stakeholders to pin down requirements, then ran a series of architecture planning sessions with the T4 IT team. Together we wrote a development roadmap that fit how the terminal operates.

Real-Time Data Integration

The system integrated two real-time data feeds:

1. Vendor-provided API supplying wait time information from sensors throughout the terminal
2. Internal API maintained by terminal flight operations

Each channel shows the data differently:

• Website: Prominent wait times for arrival planning
• Arrivals board: Focus on arrival information with optional taxi wait times
• Kiosks: Default to departure information for airside passengers

Project Management

Team Structure & Communication

Clear expectations came first. Each person on the team knew what they owned and where their work fit.

Setting Clear Expectations

• Implemented structured code review process
• Set documentation standards
• Mapped roles and responsibilities

Communication & Meeting Rhythm

Internal

• Daily engineering standups
• Weekly progress reviews to catch problems early
• Weekly design reviews with engineering in the room
• Mentoring for junior developers on the harder integrations

Client

• Bi-weekly stakeholder sessions
• Regular progress demos
• Ongoing feedback
• Scope adjusted as the terminal’s needs changed

The part of the job I liked most was mentoring the junior developers through the integration work, which was the hardest part of the build.

Future Direction

Terminal 4 is exploring AI chat assistance across its channels. The groundwork from this project carries over:

Diagram of AI Agent architecture for JFK Terminal 4

• Unified web platform for consistent deployment
• Location-aware kiosks for contextual assistance
• Structured content management
• Established security protocols

Validation would follow the same steps we used on the original build:

1. Expert evaluation
2. Internal testing
3. Limited deployment with observation
4. Iteration
5. Full rollout with continuous monitoring

Key Learnings

RECOGNITION

Terminal exterior, with tarmac