Airways NZ

Air Traffic Controller Operational Tool

Private client of Theta - New Zealand

Operational tool / ui/ux and development process

Creating a solution for Airways New Zealand new operation system converting their physical documentation into a digital application.

---

Getting started

Overview

A new operational application was required to support air traffic controllers across New Zealand by replacing physical documentation like maps, charts, manuals, emergency procedures, bezel displays, and notices. The tool was intended to streamline processes in radar centers and, eventually, in control towers.

---

User experience

Problems

Physical documentation that Traffic Controllers used were too specific for their location and they wanted a quicker solution to switch between other tools such as weather, radar screens to assist aircrafts and the application had to be an application which could only connect securely to their network.

Many Air Traffic Controllers were very familiar with the physical documentation and they knew exactly where to look when the coordinates were provided by the pilot, but they needed a faster solution, a digital solution.

The team worked to a tight 7-week deadline to deliver a design solution which would then be tested and functional/usable by Airways.

---

Project

Process

---

Research phase / 2 weeks

Research Phase (Weeks 1–2) We conducted 26 interviews with controllers from seven air traffic sectors in New Zealand and carried out observational studies within radar centers. Previous design concepts were reviewed, and competitive design research was conducted.

Key Deliverables:

• Competitive Design Research Report: Highlights from similar tools and industry benchmarks.
• Observational Analysis Report: Insights from observing controllers in action.
• Interview Summary Document: Key findings from discussions with controllers.

---

Concept phase / 2 weeks

Concept Development (Weeks 3–4) The team created a comprehensive user journey and developed three low-fidelity prototypes. Feedback was gathered from controllers and stakeholders to assess preferences and refine the design direction.

Key Deliverables:

• User Journey Map: Visualized workflows and user interactions.
• Low-Fidelity Prototypes: Three initial concepts for validation.
• Feedback Summary & Design Recommendations: Insights to inform the next iteration.

---

Usability testing and design / 2 weeks

Usability Testing & Design (Weeks 5–7) Using feedback from the concept phase, we developed a detailed prototype and tested it with controllers using task scenarios.

The design was refined into a high-fidelity prototype, which was then showcased to operational and executive stakeholders.

Key Deliverables:

• Medium-Fidelity Prototype & Information Architecture: Initial structured prototype for usability testing.
• Usability Testing Plan & Summary: Moderated testing results.
• Wireframe Document: Detailed design layouts.
• High-Fidelity Prototype: Final polished design.
• Design Guidelines & Assets: Documentation for future development.
• Project Showcases: Presentations to stakeholders at various levels.

---

Contact