Peak travel season pushes TSA officers (TSO*) to their limits, manually verifying thousands of documents while ensuring security. What if there was a way to ease this burden? Learn how I designed the interface for NEC’s self-verification mobile kiosk that streamlines the verification process, enhancing security, and freeing up TSA resources.
*TSOs: In addition to line management, TSOs screen passengers, baggage, and cargo at airports and other transportation hubs to prevent the introduction of prohibited items and potential threats.
> Product Manger
> Solution Architect
> Software Engineer
> UX Designer
> User Personas
> Journey Mapping
> Wire-Framing
> UI Design
6 Months
As the UX Designer on the team, I was challenged with designing the kiosk’s interface in a way that enabled passengers to self-verify. Therefore, freeing-up TSOs to focus on maintaining a safe and secure environment.
Research was immensely supported by the collaboration with the Product Manager (travel industry SME).
Both passengers and TSOs are users and the beneficiaries of the solution. The TSO uses the kiosk to eliminate manual verification and benefits from reduced cognitive strain. While the passenger uses the kiosk to self-verify, resulting in faster lines and increased sense of safety (See Image A).
We outlined the 3-minute verification process (See Image B), where TSOs manually verified up to 80 passengers in a 4hr shift. The repetitive nature of this task, especially during extended shifts and holidays, added cognitive strain and heightened security vulnerabilities.
With a foundational understanding of the current experience, we produced a Journey Map (See Image C). Illustrating how the solution removes the need for TSOs to manually verify passenger identities, closing critical security gaps that come with human error.
With deep user insights, we crafted a problem statement that zeroed in on the core design challenge—ensuring a solution that truly benefits the users.
The kiosk was designed by a 3rd party engineering firm with two separate screens, one for passengers and one for TSOs. The core design elements and user flow needed to be based the existing setup to keep interactions intuitive, avoiding slowdowns and reducing additional workload for TSOs. (See Image D & E)
The user flow expanded on PMs guiding artifacts. This served as reference to ensure the interface design moved users forward in the process while covering error states. (See Image E)
Wireframes facilitated communication with engineering and product. This was instrumental in discussion on functionality, interactions, and capturing any usability concerns (See Image F).
The UI color scheme expanded on the TSA logo’s tints, tones, and shades to create high-contrasting colors for calls-to-actions, status messages, and step indications. (See Image G, H, and I).
Following successive design iterations and validation testing, we approved the final interface for system integration (See Image H).
This project was far from smooth sailing.
Risking passenger queue buildup. My wireframes assumed near-instant verification. This resulted in the introduction of additional status screens (“Verifying…”) to manage wait-time expectations.
1Foundational research (even via SMEs/secondary data) was critical for understanding baseline experience.
2Using familiar UI elements (based on the existing solution) minimized passenger learning curves and TSO retraining.
3Frictionless UX enabled strategic automation freeing up human resources for higher-value tasks (e.g., threat detection) and improves accuracy.
4Aesthetic choices (e.g., status indicators) are instrumental in high-stakes environments where errors have serious consequences.