Trust Doesn’t Run on Apologies: It Runs on Proof

I’d just taken over several projects when a project’s lead engineer stopped me in the hallway. He didn’t shake my hand. In a low, urgent voice, he said, “I need to talk to you.” Now.

We found a conference room. “We’re almost out of money,” he said. I thought I’d misheard him. I asked him to repeat it. He did. I asked how much he needed — thinking maybe $10,000, a rounding error. “About another $100,000,” he said.

My head snapped back like I’d been hit. The project was only half finished.

For a second, every defensive thought I had lined up: I just got here. I didn’t set this budget. Someone else built this mess. All of it true. None of it useful. I told him to look into it from his side. I’d look into it from mine.

What I Found

Digging into the financials, I didn’t find a missing system — I found an unused one. The tools to track spending and prevent exactly this kind of shortfall were already there. Charges had been accumulating with no one reviewing them, no one watching the burn rate. The tool existed. The discipline to use it didn’t. We rebuilt the discipline: I asked for full documentation of who was charging to the project and why, and for the first time, someone actually pulled it together.

The Room I Didn’t Want to Walk Into

I could have called the airport executives the moment I found the problem. But calling with no answers would have only added confusion to a conversation that already needed clarity. I wanted the problem identified and real answers in hand before I said a word. The project was due for a periodic site visit, so I used it. Standing in the airport parking lot beforehand, I had to make myself actually walk in.

I felt sick. Outnumbered. The conference room I’d sat in a dozen times before suddenly felt like the size of a broom closet.

“How can we trust you with $15 million in other work,” one of them asked, “if you can’t manage this?”

Internally, I wanted to say it wasn’t me — I’d inherited this. I said none of that. Instead: “You’re right. We made a mistake, and I’m sorry. I’m working to correct it and put measures in place so it doesn’t happen again.”

They didn’t hand me relief or reassurance. They handed me a list: documented charges, a real burn-rate analysis, a plan for making sure this didn’t happen again.

The accounting only explained the hole. What actually released the funds was the plan — a burn-rate review built into every reporting cycle going forward, with someone accountable for watching it. We could show them not just what went wrong, but why it wouldn’t happen again. They released the funds.

What Actually Rebuilds Trust

I could have spent that meeting defending myself. Technically, I’d have been right. But leadership under pressure isn’t about being technically right — it’s about who’s willing to own the outcome, whether or not they created the problem.

The apology got me back in the room. The plan — built from a system that had been available the whole time, finally put to use — is what actually got the funds released. We didn’t need new tools. We needed someone to insist the ones we had actually got used, and prove it wouldn’t happen twice.

Gary Alexander is a Federal Aviation Administration program manager and retired Marine Corps Company First Sergeant with more than 40 years of leadership experience spanning the military, private industry, and federal service. Across his work with OPM’s Federal Executive Board and nearly two decades at the FAA, he has stood up four first-of-kind enterprise programs, rescued initiatives others had written off, and coached leaders across multiple federal agencies. A Distinguished Toastmaster, Certified Kaizen Instructor, and AAFEA Fellow, Gary writes about leadership, trust, and what it actually takes to build something from nothing. He believes vision without relationship is just potential with no circuit to complete.

Photo Credit: Moe Magners, Pexels