The moment I realized I’d been passing along fiction as fact.

There’s a specific kind of awful that comes from realizing you’ve been repeating someone else’s lie.

Not knowingly. Not maliciously. But you repeated it to a client who trusted you, and now that client is sitting on the other side of a relationship that probably can’t be saved.

Here’s how it went.

My electrical team assured me we’d come in under budget. I passed that along. Then the deadline came and went with nothing to show for it. I followed up, got another confident update, and passed that along, too. A week later? Still nothing. And now, with the project unfinished and the client already frustrated, the team has decided they won’t deliver the drawings until a change order gets signed.

Held hostage. After missing every commitment they’d made.

The invoice might eventually get paid, at least part of it. The relationship is unlikely to recover.

The Big Picture

Engineers are wired to think in deliverables. Scope, schedule, budget, done. But clients don’t experience projects that way. They experience a series of interactions, updates, and moments where they’re deciding whether to trust you.

Every one of those moments is an audition.

My team missed three in a row. Worse, I carried their optimism to the client as if it were my own. When it turned out to be fiction, the client had no one else in the room to be frustrated with. Just me.

Here’s what drives me nuts about this: I’m not the electrical engineer on this project. I can’t audit their hours or second-guess their scope mid-project. My job is to manage the client relationship, and to do that, I need accurate information from my team. When they give me fiction instead, I don’t just have a project problem; I have a reputation problem. And reputation problems don’t get resolved with a change order.

Core Insight

Technical teams often treat honesty as something they can afford to delay. “We’ll deal with the change order at the end.” “We’ll catch up on the timeline.” “No point worrying the client yet.” The logic feels reasonable internally. It’s catastrophic externally.

The reality? The moment your team says “we’re fine” when they aren’t, they’ve started spending relationship capital that isn’t theirs to spend. They’re spending yours.

Protecting your margin at the end of a project by holding deliverables hostage doesn’t just cost the relationship with that client. It costs every future project that client might have sent your way. The referrals. The goodwill that takes years to build and an afternoon to burn. Engineering is a smaller world than most people realize. In a small town, it’s not just costly. It’s fatal.

The invoice is a line item. The relationship was the business.

Why This Matters To You

If you interface with clients, your credibility is only as good as the information you pass along. That’s an uncomfortable position, because it means you’re partially dependent on people you don’t fully control.

Which means when your team’s judgment fails, you’re the last line of defense before it becomes the client’s problem.

“We’re under budget and on track” six weeks into a complicated project deserves a follow-up question, not a forwarded email. I didn’t push hard enough early, and that’s on me. The lesson I’m taking out of this: if an update feels too clean, it probably is.

Here’s the standard I’m holding my teams to going forward: early bad news is a gift. Late bad news is a crisis. The professionals who understand that are the ones worth building a team around.

Practical Steps

First: Build a simple early-warning protocol with every team you rely on. One rule: if anything is trending wrong on budget, timeline, or scope, you want to hear about it before it becomes a client conversation. Make it explicit, not assumed.

Second: Before you pass any internal update to a client, ask yourself one question: “Would I stake my credibility on this?” If the answer is anything less than yes, ask one more question before it leaves your inbox.

Third: Before the next project kicks off, have one honest conversation with yourself: do the people you rely on actually know what you need from them when things go sideways? If you’ve never said it explicitly, assume they don’t.