Communication fails when employees learn after the consequences have already started.

I have sat through more than one post-mortem where management concluded, “The communication was clear.”

And technically, it was.

The email had a subject line. The instructions were numbered. The deadline was bold. Nobody could reasonably argue that the words were confusing.

There was just one small problem.

The employees received it after they had already done the work.

A message can be perfectly clear and still be operationally useless.

Consider an Application Management Support team billing time to a project code. They were told which code to use, so they used it. Week after week, people submitted their hours, managers approved them, and the financial reports absorbed the entries.

Meanwhile, a decision had been made to move the work to another code.

The people doing the work did not know.

When the update finally arrived, the instruction itself was very clear: reverse the previous entries and rebill the hours elsewhere.

Now employees had to reopen timesheets, correct old records, chase approvals, and explain why previously accepted entries were suddenly wrong. Project financials were temporarily distorted. Managers spent time reconciling reports. Delivery work paused while everyone repaired an administrative problem they did not create.

Then somebody asked why the team had used the wrong code.

They had not ignored the process. They had followed the last instruction management gave them.

That distinction matters.

When employees repeatedly discover changes after acting, communication stops feeling like guidance. It starts feeling like evidence management uses afterward to show that people were told.

The date on the email may protect the sender. It does not recover the wasted hours.

Timing is not a delivery detail. Timing is part of the message.

This is where employee experience connects to first-line management systems.

The problem is rarely solved by telling managers to “communicate more.” More messages can create more noise. The real questions are operational: Who owns notifying affected employees? What event triggers the update? Which channel is authoritative? How do we confirm people received it before the new rule changes their work? What happens when finance, delivery, HR, or another function changes something the frontline must execute?

That is process design, meeting discipline, reporting, and role clarity—not merely writing skill.

Employees also carry responsibility. They should ask when instructions conflict, read agreed channels, and avoid treating uncertainty as permission to improvise. But they cannot respond to a decision they have not received.

Leaders sometimes focus on whether a message was sent.

Employees experience whether it arrived in time to help.

The better test is not, “Was the communication clear?”

It is, “Could the employee still act on it without undoing yesterday?”

Discussion question: Where in your organization does important information consistently arrive one step behind the work?

If late communication keeps creating rework, the underlying problem may sit in the management systems around roles, process triggers, meetings, and reporting—not in the wording of another email. My book, The 7 Essential First-Line Management Systems, explores how that operating architecture shapes clarity, execution, and the employee experience: imadlodhi.com/flm1.