Clients Don’t Need Perfect Answers. They Need Clear Communication.

What working in implementation taught me about maintaining trust when things don’t go according to plan.

When everything is going according to plan, communication is fairly easy.

Updates are straightforward.

Timelines stay on track.

Everyone knows what’s happening.

There’s not much uncertainty to manage.

It’s the days when things don’t go according to plan that have made me think differently about communication.

Working in a client-facing implementation role, I’ve realized that delays aren’t always the hardest part of the job.

Sometimes, it’s explaining them.

An issue comes up.

It needs to be investigated.

Maybe another team needs to get involved.

Maybe there’s a dependency that has to be resolved first.

From the client’s perspective, though, most of that is invisible.

What they experience is simple.

Something that was expected to happen… hasn’t happened.

Early on, I found myself thinking that the most valuable thing I could give a client was an answer.

The longer I’ve worked in implementation, the more I’ve realized that’s not always possible.

Sometimes there isn’t an answer yet.

The investigation is still ongoing.

The issue is still being worked on.

Nothing has been resolved.

That doesn’t mean communication should stop.

If anything, that’s when it becomes more important.

I’ve noticed that uncertainty has a way of filling empty spaces.

When people don’t know what’s happening, they naturally start trying to explain it for themselves.

Maybe the issue has been forgotten.

Maybe no one is working on it.

Maybe nobody knows what’s wrong.

Those assumptions usually aren’t fair.

They’re simply what happens when people don’t have enough information.

I’ve found that even a simple update can make a difference.

Not because it fixes the issue.

But because it answers the question that’s often sitting underneath everything else:

“Does someone know what’s going on?”

Keeping clients informed doesn’t make a technical problem disappear.

It doesn’t speed up investigations.

It doesn’t remove dependencies.

What it does is remove unnecessary uncertainty.

It tells the client that the issue is understood, people are working on it, and they’ll continue to hear from you as things develop.

Implementation isn’t just about delivering a solution.

It’s also about guiding people through a process they can’t always see.

Clients don’t have visibility into every internal conversation.

They don’t know which teams are involved.

They don’t know what’s being investigated behind the scenes.

The only part of the process they experience directly is the communication they receive.

That communication shapes how they experience the project just as much as the final outcome.

It’s made me rethink what good client communication looks like.

I used to think it meant having the right answers.

Now I think it often means making sure people aren’t left wondering what’s happening.

Because when plans change, trust isn’t built by pretending everything is fine.

It’s built by being clear about where things stand, what you’re doing next, and what the client can expect from you.

Sometimes, that’s exactly what people need while the solution is still taking shape.