What happens when the process breaks?
Operational resilience comes down to leadership choices about how information moves, where authority sits, and whether people on the front lines are trusted to use their judgment.
Those choices often go unnoticed when operations run smoothly. They become glaringly obvious the moment a process fails and staff have to figure out what to do next.
A recent trip to Baltimore offered three very different examples.
When our flight was delayed by nearly four and a half hours, my wife and I had to choose between waiting it out or rebooking for the next morning. The airline agents were courteous and genuinely wanted to help. But every time we spoke to someone new, we had to start from scratch. None of our information carried over, forcing us to catch each representative up to speed while making a time-sensitive decision. Customers are left to bridge the gaps between disconnected internal silos.
Later, I mistakenly entered the wrong rental car return lot, requiring several cars to be moved to clear the path.
The first employee explained the disruption and laid out how long it might take to sort out. Then his manager stepped in.
“We’ll move this one car, hold this group for a moment, and you’ll be out of here in less than five minutes.”
Both faced the exact same situation. One explained the problem; the other made a decision and fixed it.
When we finally reached the Avis return area, another employee noticed I was trying to arrange a ride to our hotel. When he heard it was only a few miles away, he said, “I’ll take you.” He saw an opportunity to help and acted on it, filling the drive with restaurant recommendations and stories about the city.
That ride was a small gesture, but it stood out because he took personal responsibility for our immediate experience. Small moments like that, when scaled across a company, shape overall operating performance.
When information doesn't follow an issue, employees waste time rebuilding context instead of solving problems. Handling times go up, consistency drops, and departmental seams are exposed directly to the customer. If routine choices require endless escalation, resolution slows down, and management gets bogged down fixing things that should have been handled on the floor.
When employees see initiative backed up by leadership, they use better judgment the next time.
The front line is where leadership philosophy becomes operational reality. Leaders decide whether their people have the context to understand issues and whether decision-making power is close enough to the customer. Their reactions to judgment calls signal whether initiative is welcomed or discouraged.
Those choices are made long before disruptions happen, but their impact only shows up when the standard playbook fails. A resilient organization maintains context, pushes authority closer to the work, and backs up sound judgment. Executives are ultimately responsible for building systems that respond effectively when reality diverges from the plan.
The Pebble
Identify a handoff in your customer or employee experience where issues frequently stall or require escalation.
Ask the people closest to it: What information or authority is missing when the standard process stops working?
Their answers will point straight to systems that lose context, decisions made too far from the ground, or management habits that quietly discourage action.
The Ripple
Eliminate one recurring constraint. Make sure information follows the issue, or give decision-making power to the people actually handling it.
Watch what happens. Does resolution get faster? Do fewer issues land on management's desk?
A small fix at a frustrating handoff cuts costs and builds real trust in change.
The Question
When the process no longer fits the situation, do your people have the context and authority to figure out what comes next?
Be Safe. Be Inspired. Be You.
-Joe Morgan
