Artemis II put four humans farther from Earth than anyone has traveled in 50 years. What kept them safe wasn’t bravery. It was the people on the ground who could see everything the crew couldn’t. Your contact center has the same problem, and is still pretending it doesn’t.
On April 1st, four astronauts sealed themselves inside a capsule called Integrity and rode a column of fire into orbit. Over the next nine days they traveled 695,000 miles, looped behind the Moon and became the first humans to venture beyond low Earth orbit in more than half a century. On April 10th, they splashed down in the Pacific off the coast of San Diego, alive and well.
I watched as much of it as I could. Space exploration is a long way from my day job. However, something about the way NASA ran that mission kept pulling at a thread I think about constantly in the context of contact center performance. It wasn’t the technology or the bravery of the crew. It was the structure of who could see what, when and what they were able to do with it.
|
|
The crew flew the spacecraft. The ground understood it.
|
Mission Control at Johnson Space Center had hundreds of flight controllers, each watching a specific slice of the spacecraft’s systems: propulsion, life support, communications, trajectory. Every sensor reading from Orion transmitted continuously to the ground, updated in real time, correlated across disciplines. When something shifted, the people responsible for the mission knew immediately. They did not wait for a report. They did not sample the data. They watched it live.
Now, think about how your contact center learns that something has gone wrong.
For most operations, the answer involves some version of last week’s quality scores, yesterday’s handle time report or an escalation from a supervisor who noticed a pattern three days after it started. The data that would have told you something was wrong existed at the time. It was being generated continuously, by every call on every queue. It was sitting in systems your team does not have direct sight of, in a form that required someone to compile it before it meant anything.
That gap, between when the signal exists and when it reaches someone who can act on it, is where customer experience erodes. Not in dramatic failures that everyone sees. In the slow drift that nobody catches until the numbers arrive.
3 Takeaways from Mission Control
|
01
|
A METRIC WITHOUT A BASELINE IS JUST A NUMBER
NASA knew what Orion should look like under every condition before the crew ever boarded. That knowledge was built over years of testing and instrumentation, not inherited from experience. Most contact centers develop their sense of normal the other way: from what has always been, from gut feel, from the absence of complaints. Which means when handle time creeps up 2% over six weeks, or audio quality degrades on a specific carrier route, or first contact resolution drops on Tuesday mornings, there is no reference point precise enough to make the drift visible. The metric exists. The baseline that would give it meaning does not.
|
|
02
|
SILENCE IS ONLY READABLE IF YOU UNDERSTAND THE SYSTEM
During re-entry, Orion hit the atmosphere at nearly 25,000 miles per hour and the plasma surrounding the capsule cut all communication for approximately six minutes. Mission Control held that silence without panic. They knew exactly what was supposed to happen and exactly when the signal should restore, because nine days of continuous telemetry had given them a model of the system precise enough to make the gap interpretable. Most contact centers have unplanned blackouts every day. A queue that runs long. A call type that spikes. An agent group whose performance has been drifting for a few weeks. None of it breaks a threshold. All of it is signal. However, without a well-understood baseline, silence looks the same as normal.
|
|
03
|
YOUR AGENTS ARE EXTENDING TRUST. THE QUESTION IS WHETHER IT IS WARRANTED.
Commanders Wiseman, Glover, Koch and Hansen had no choice but to trust that the people on the ground could see what they could not. Sealed inside the capsule, doing the most consequential work of their careers, their safety depended entirely on the quality of the visibility behind them. Your agents are in the same position every shift. They are inside the conversation, present with the customer, making real-time decisions with whatever their screen gives them. They cannot see the system around them. They trust that someone can. The question worth sitting with is whether the infrastructure you have built is genuinely worthy of that trust, or whether it is telling you what happened after the moment to act has already passed.
|
If something goes wrong in the next four hours, a configuration issue, a carrier problem, a surge in a specific call type, how long will it take you to know? And when you find out, will it be because your operation surfaced the signal or because a customer already told you?
Artemis II covered 695,000 miles and came home safely because the people responsible for that mission built the visibility before they needed it. That is the only moment it can be built.
Until next time, and as always, Hooroo