First week. New company. They handed me a $90M+ public transit project — 2 years in, 4 months left.

Seven transit agencies. Three subcontractors: web, back-office, mobile app. 600,000+ daily riders depending on this system.

The problem: Mobile app vendor delayed for months. Everything had dependencies. If they failed, the whole system missed launch.

Translation: Burning dumpster fire. My job: fix it.

First Attempt: Fix the Plan

I did what any good PM would do.

Step 1: Asked the vendor PM: "What's causing delays?"

Answer: "Scope creep. Customer keeps adding requirements mid-sprint."

Step 2: Created adjusted sprint plan with vendor.

Step 3: Got customer to agree: no more new scope until after launch, de-prioritize scope creep (move to v2), focus only on original scope.

Customer agreed. Monday. New sprint started.

Problem solved.

Friday Morning: Everything Collapses

Friday morning. End of first sprint with new plan.

Me: "Hey! Sprint review this afternoon?"

"Sorry. We can't deliver most of the things in this sprint."

I stared at my screen.

This was a DOUBLE delay.

Customer compromised. We cut scope. Adjusted timeline. Removed blockers.

And they STILL couldn't deliver.

At this point, I almost had a heart attack. Luckily, I was young.

The Phone Call That Changed Everything

First, I emailed the customer:

Subject: Mobile App Development - Issue Identified

There's an issue with the subcontractor. I'm working to understand root cause and will have a solution plan by end of day.

Short. Honest. Professional. No excuses — because I didn't know the real problem yet.

Then I picked up the phone.

I said something I'd never said before:

"Listen. We're on the same boat. We either deliver together, or sink together."

"I need complete honesty. No blame. No consequences. I just need to know what's REALLY going on."

"I can't help if I don't know the truth. So what's really happening?"

Silence.

Then he spoke.

"We lost our iOS developer a while ago. He was our only iOS developer. New person won't start until next month."

Me: "How long ago?"

Six weeks ago.

They'd lied for six weeks. Promising dates they couldn't hit. Blaming scope creep when the real problem was zero iOS capacity.

Most project failures are communication failures, not technical failures.

Why He Lied

I asked why. His answer broke my heart:

"Before you joined, every time we were delayed, we got yelled at. Blamed. Threatened with contract penalties."

"Nobody asked WHY. Nobody tried to help."

"So we were scared to tell the truth. We thought maybe we could fix it before anyone noticed."

And there it was.

The problem was fear.

Fear of truth. Fear of blame. Fear of losing the contract.

So they lied. And lies made everything worse.

The Real Solution: Empathy First

Everyone knows trust and honesty matter.

But trust and honesty aren't the solution. They're the RESULT.

The solution is empathy.

Empathy → Trust → Honesty → Project Success

When I said "We're on the same boat" — that was empathy. Not "you" vs "I." WE.

I told the PM: "Thank you for being honest. Here's what we're going to do together."

Without empathy: "Who's responsible?" / "This is unacceptable!" / "We'll review your contract" — people hide problems.

With empathy: "We're on the same boat" / "What's REALLY going on?" / "Let's fix this together" — people tell the truth.

We replanned together: what needs iOS (pause until new dev), what can run without iOS (start NOW), realistic timeline with 2-week ramp-up.

I went to customer with truth. They agreed.

Because it was a REAL plan based on REAL constraints.

The Results: 0% to 100% in One Month

The project "doomed to fail" shipped on time. Full scope.

Not because I had magic frameworks. But because I created safety. People told the truth.

What I Learned

1. The problem is rarely what people say it is. They said: "Scope creep." Reality: "We lost our only iOS dev and were too scared to tell you."

2. Fear makes people lie. And lies destroy projects. When the culture punished bad news, the vendor learned to hide it. The project spiraled for months.

3. Empathy isn't soft. It's how you unlock truth. "We're on the same boat" created safety. Safety unlocked honesty. Honesty unlocked the real problem. Then we could actually fix it.

Try This In Your Next Project

Instead of: "Why is this delayed?"

Say: "What's really going on? Let's fix this together."

Result: People tell you the truth.

Why This Is the Story I Always Want to Share

Maybe you've been in a similar situation. A vendor hiding problems. A team member too scared to admit they're stuck. A project spiraling because nobody felt safe telling the truth.

The lesson I want you to take away: Projects succeed when people feel safe. And people feel safe when you lead with empathy.

I created safety by saying "We're on the same boat." I asked for honesty without consequences. I got truth. Then we fixed it together. And we shipped successfully.

Projects aren't built by frameworks. They're built by people. And people need trust.

Next time you face a crisis, remember: The problem isn't usually what people say it is. Ask "What's REALLY going on?" Create safety. Get truth. Fix it together.

Why I'm Building TelosFlow

That Friday morning, I spent 8 hours manually replanning a program that was falling apart. Recalculating dependencies. Rebuilding timelines. Preparing a client-ready recovery plan.

The empathy got us the truth. But the replanning still took all day.

I kept thinking: what if that part took 30 seconds instead of 8 hours?

That question is why I left my career and started TelosFlow — to build AI that earns the trust of the people who manage the world's most complex programs.

Written by Margaret Ton, Founder & CEO of TelosFlow. 8+ years as a program manager delivering $100M+ projects across 4 continents for Fortune 500 aerospace, aviation, and enterprise technology companies. PMP-certified, MS in Project Management from GWU. Now building Eva — AI that earns the trust of the people who manage the world's most complex programs.