The 15-Minute Airline: From Lost Time to Capacity

What would happen if every process in an airline took 15 minutes less? It is an interesting question because 15 minutes does not sound particularly significant when looking at one task. In an airline, however, processes are repeated continuously across maintenance, engineering, operations, ground handling, administration and passenger services. A small amount of unnecessary time, repeated often enough, can become a significant source of lost capacity.

The idea is not to make people work faster or to reduce the time required for safety-critical activities. It is about identifying the time that exists around the work: waiting for information, searching for tools or documents, waiting for approvals, repeating information, correcting errors or dealing with unnecessary handoffs. These are often the minutes that are overlooked because they do not belong to one specific task. In Lean, these are forms of waste.

Where Are the 15 Minutes?

Consider a maintenance task. The technician may need 30 minutes to complete the work, but the overall process can take much longer. The technician may wait for a component, search for technical information, wait for another activity to be completed or discover that something required for the job has not been prepared.

The work itself may be efficient. The flow is not.

The same pattern appears across an airline. An engineer may be waiting for an approval. A planner may be waiting for information from another department. A turnaround team may be ready to work but waiting for equipment. A document may pass through several people before it can be released.

These delays are easy to overlook because the time is not always attached to a specific task. Nobody may be actively working during those minutes, but the process is still consuming time.

Waiting Is Part of the Process

One of the useful principles of Lean is to look at the complete flow rather than only at the time spent doing the work.

A task that takes 30 minutes does not necessarily mean the process takes 30 minutes. If the task is followed by 15 minutes waiting for an inspection, another 10 minutes waiting for information and another 5 minutes resolving an error, the process has taken an hour.

The waiting time is real, even though no productive work is taking place.

This is why simply asking people to work faster often has limited impact. If a technician spends 15 minutes looking for information, working faster will not remove the search. If an engineer is waiting for an approval, increasing their pace will not make the approval arrive sooner. If a turnaround team is waiting for equipment, asking them to move faster cannot compensate for equipment that is not available.

The better question is: why is the work waiting?

Fifteen Minutes in Aircraft Turnaround

Aircraft turnaround provides a good example because many activities have to come together at the right time. Cleaning, catering, fuelling, baggage, cargo, passenger boarding, maintenance and flight preparation all contribute to getting the aircraft ready for departure.

Making one activity faster does not necessarily make the turnaround faster. A team can finish its work early and still have no effect on departure if another activity is holding up the aircraft.

The same applies to maintenance. Reducing the time of one task may have little effect if the aircraft then waits for another activity, a component, an inspection or an approval.

Lean therefore looks at the flow between activities, not just the efficiency of each activity in isolation.

Finding the Waste

Finding the 15 minutes requires observing the process as it actually happens.

Choose a process that occurs frequently and follow it from beginning to end. Measure not only the time spent performing the work, but also the time spent waiting between activities.

Look for the less obvious forms of waste: searching for information, moving unnecessarily, requesting clarification, waiting for decisions, entering the same information more than once, correcting mistakes or handing work from one department to another without adding value.

The 15 minutes may not exist as one obvious block of waiting time. It may be spread across several small delays.

This is where process observation becomes important. What looks like a five-minute delay to one department may be the result of a much earlier problem somewhere else in the process.

Not Every Minute Should Be Removed

There is an important distinction between removing unnecessary time and simply making a process shorter.

A safety inspection should take the time required to perform it correctly. A regulatory requirement should not be shortened because it affects a performance measure. A maintenance task should never be rushed to meet an arbitrary target.

The objective is to remove time that does not contribute to the purpose of the process while protecting safety, quality and compliance.

Sometimes the solution is simple: prepare tools before the work starts, make information easier to find or ensure that the next person has everything needed to continue. In other cases, it may require changing the sequence of activities, removing an unnecessary approval or improving the way departments hand work to each other.

The improvement comes from changing the process, not from putting more pressure on the person doing the work.

From Lost Time to Capacity

The 15-minute question is not really about 15 minutes. It is about making hidden waste visible.

When a process is repeated every day, the time lost to small delays becomes part of the normal operation. Because it is familiar, it can be difficult to see.

The opportunity is to identify where work waits, understand why it waits and remove the causes where it makes sense to do so.

That is how lost time can become capacity. Not by asking people to work faster, but by designing processes that allow them to spend more of their time doing the work that actually needs to be done.

Learn how to identify waste, reduce waiting time, and improve airline processe→