Design of a mobile app to help military service members take advantage of an underutilized benefit
Space Available Travel (Space-A for short) is a benefit provided to US Service members that allows them to take seats on military cargo planes for free as a cheap means of travel during their service leave. During my time at General Assembly's user experience design imersive program I worked on a design for an app that would help to streamline the antiquated process of accessing this benefit.
We began this project with the basic understanding that the process for utilizing Space Available Travel was outdated and difficult, but we still needed to find out what parts of the current system were problematic and how potential users could be better served. In order to accomplish this, we completed two pieces of research:
The purpose of this usability testing was to understand if new users were able to understand the process as it was, and if not, how we might be able to solve their pain points. Essentially, we wanted to validate our problem and to give ourselves a jumping off point for our own work. Testing consisted of 5 participants who were not familiar with Space-A beforehand. We gave them a basic description of what Space-A was and provided them a link to the website where Space-A is managed, which is called Air Mobility Command. They were instructed to learn how apply for travel and to find a flight near them.
Key Insights
We spoke with 7 people during the course of our interviews: 4 active duty service members at recruiting centers, 1 veteran at the USO, and 2 employees at the passenger terminal at Joint Base McGuire in New Jersey. All but one of the people we interviewed had used Space-A in the past. Through these interviews we wanted to find out:
Insights from active duty
We found that all of those we interviewed were quite fond of Space-A and said they would use it again in the future. Despite this, they had some major concerns about the consistency of the service. They mentioned that they routinely wasted their time going to terminals to take flights only to find out that they had been cancelled or had filled without warning. They also mentioned that the process of requesting travel and finding flights was tedious and confusing.
Insights from veteran
The veteran told us he used to use Space-A when he was active duty, but now that he's a veteran his status on Space-A listings is lower than it used to be. Since many active duty soldiers use Space-A to travel home for leave to see family, they're given priority over veterans who typically are using the service for strictly leisure purposes.
Insights from passenger terminal representatives
Before drawing up any sketches, we wanted to first work out some of the technical aspects of how the app would function. Based on our interviews and testing, we already knew that users wanted more details about flights, but the terminal was not allowed to post the details on Facebook because of security. Additionally, we wanted the process for applying for travel to as simple as possible. The solution we found for these issues was to have users sign in with DS Logon, a secure ID provided by the Department of Defense to all service members. This was a convenient way to verify that all of our users would have a military background, thus eliminating the issue of flight information security. As an added bonus, DS Logon also stores a variety of data that can be pulled directly into our app which includes the user's:
One of the most important pieces of this project was streamlining the process of filling out the "Form 140" used for travel requests. This document is essential for users to be able to use the service, so making it as easy as possible to fill out was quite important. Since the user's data can be used from DS Logon and Leave Web, the app will be able to autofill some of the fields as well as skip certain sections. Because of this, we decided to create a user flow diagram to map out the possible screens that could appear during the form depending on the user's leave status, military rank, etc.
The resulting form we created (shown in the gallery below) pulls information from DS Logon, allowing the user to input only a few details. The user's name, rank, leave status, and dependents are auto-populated into the form, allowing for an easy submission. All the user needs to do then is fill out the country of origin, the dependents they will be traveling with, and the relevant passport information. If the user doesn't plan to leave the country or travel with dependents, the form essentially fills itself out.
<
Our goal in creating a process for searching flights was to mimic the look and feel of apps made for commercial airlines while working under the restrictions of the Space-A process. Unfortunately, allowing users to search for a specific route to and from cities like a normal airline would be nearly impossible given the low volume of flights and the distance between terminals. For this reason, it made more sense to allow users to browse flights by terminal rather than by a traditional to-and-from search function.
Our research showed that users of Space-A are already quite knowledgeable about the terminals in the areas they typically travel, so this system makes sense to them. Additionally, they often use Space-A for leisure travel and will choose their location based on departures from the closest few terminals, so this system would allow them to easily see what is available nearby.
In order to get a seat on a Space-A flight, users must request a seat and understand their chances getting aboard based on the standby list. The nature of this service is such that there are no guarantees and nobody is allowed to book a definitive seat. This is a restriction in the system that we could do nothing about. What we could do, however, was provide as much information as possible to users to help them understand their chances.
After developing the major features of the app, we worked on tying it all together with a home screen. We wanted this screen to provide only the most important information for users at a glance. The key elements of this page include:
Previous
Next
TO TOP