The FAA ground stop and the gap between updates and answers
How to give people useful information while your team is still working on answers.
Nico Ramsey is vice president at ECPR Texas.
An Austin, Texas, traveler trying to get home to South Korea told our Fox affiliate he had been warned of a one-hour delay before leaving for the airport Friday. Hours later, he said, he had no information at all. Another passenger described being taken off a plane after nearly two hours and left in a terminal full of people “just not knowing what to do.”
Not knowing what to do is a different problem from not knowing what happened, and it’s the one communicators can do something about. During a disruption, people have practical decisions to make. Should they stay at the gate? Find a hotel? Call someone to pick them up? They can understand why an answer about the cause might take time. Meanwhile, they need help figuring out what to do with the next few hours.
A telecommunications failure prompted the Federal Aviation Administration to halt departures nationwide for nearly five hours, with more than 10,000 flights delayed or canceled. Grounding the planes was a defensible safety call. The confusion that followed deserves a closer look from those of us who advise organizations on crisis communications.
Start with what people need from you
I would want a communications team reviewing this incident to begin with the questions passengers were asking. It’s easy to spend the first hour working on an explanation of what happened while the people affected are asking whether they should leave home.
The FAA can explain a national flight restriction. An airline can address a passenger’s booking. Airports have their own information to provide. Travelers shouldn’t have to understand those responsibilities to find an answer, so each organization’s message needs to direct them to the next useful source.
Before approving an initial statement, I’d ask:
- What decision does our audience need to make right now?
- What do we know that can help?
- What are we still trying to confirm?
- Where can people get information about their particular situation?
You can answer some of those questions while technicians are still investigating the failure. Waiting for the full explanation can leave people with nothing useful during the period when they’re trying hardest to make sense of what’s happening.
Be careful with estimates, though. Someone may book a hotel, cancel a ride or leave the airport based on what you tell them. If you don’t have a confirmed restoration time, say that plainly.
Keep the next update on the calendar
“We’ll share more as information becomes available” is familiar language. It also leaves people checking their phones over and over.
Give them a time. Then make sure someone on your team is responsible for meeting it.
Every 30 minutes might be appropriate for a fast-moving disruption. Choose an interval your team can maintain, with enough time to verify information. Work out who gathers the facts, who approves the message and who can step in when the usual approver is pulled into another meeting.
If the deadline arrives and nothing has changed, say so. Repeat the guidance that still applies and tell people when you’ll check in again. Explain that service remains suspended if that’s the case; people may otherwise mistake the next update time for an expected reopening.
And if you confirm something useful between updates, publish it then. Nobody needs to wait until 7:30 p.m. to learn something you verified at 7:10 p.m.
Think about the employee getting the questions
Travelers reported receiving conflicting estimates from airline employees during Friday’s disruption. I don’t know what those employees were told. I do know that a gate agent facing a line of frustrated passengers needs more help than a link to a press release.
Give employees language they can use in a conversation:
“We don’t have a confirmed departure time. Our next update is at 7:30 p.m.”
Put a timestamp on every employee briefing so people can tell whether they’re looking at the current version. Include the latest confirmed information, instructions they can give customers and someone to contact when a question goes beyond their guidance.
Getting this to employees before or alongside a public announcement takes coordination, especially across shifts and locations. That work belongs in the plan. So does a way for employees to tell the communications team what people keep asking. They may spot a gap in your message long before anyone in headquarters does.
Walk through the first hour before you need to
A national disruption involves organizations with separate responsibilities. Agree in advance on who explains the overall incident, how partners receive updates and which details each organization will communicate directly.
Then look beyond the statements. Check the app, automated texts, website notices and status displays. If one of those channels can’t be updated quickly, who can flag the outdated information and point customers somewhere reliable?
For the next crisis exercise, give your team an incident with an unknown cause and no confirmed restoration time. Have them work through the first hour, including getting guidance to someone answering phones or working a service counter. Ask that employee to find the latest update and explain what they would tell a customer.
You’ll learn more from that than from another round of edits to a holding statement.
Communicators may have little say over when equipment gets replaced. We have a much more direct role in deciding who approves an update, how employees receive it and where customers can find answers. Those are decisions we can work through now, before someone is standing in a crowded terminal trying to figure out how to get home.