What Happens When Information Arrives Five Minutes Late

In an industrial company, five minutes rarely seem like a problem. A delayed call, an email that hasn’t been sent yet, or an update that will arrive “in a moment” seldom cause concern. However, when that information is needed for another person to keep working, those five minutes stop being a simple delay. They turn into waiting time for other departments, into decisions that are postponed, and into processes that stop moving forward at the expected pace. In an industrial company, information also has delivery times. And when it arrives late, the delay rarely affects just one person.

A delay almost never stays where it starts

Let’s imagine a simple situation. Production is waiting for confirmation of a change in an order before continuing to manufacture. The validation takes five minutes longer than expected. Seemingly, the impact is minimal. However, during those minutes the machine remains idle, the operator cannot continue with that order, and the schedule begins to shift. When the information finally arrives, work resumes, but the lost time has already forced small parts of the process to be reorganized. The important thing is not those isolated five minutes. The important thing is that the delay begins to ripple out. A small delay in information can turn into a much larger delay in operations.

Information always has someone waiting

Information is often thought of as a passive element. Data is generated, sent, and someone receives it. In reality, behind every piece of data, there are usually people waiting to take action. A manager needs an approval to authorize a purchase. Quality assurance waits for a result before releasing a batch. Shipping needs a confirmation to organize a load. Administration cannot issue specific documentation until they receive certain data. While that information does not arrive, the work does not disappear. It simply stops. Information does not only serve to communicate. It allows other processes to continue.

The real problem appears when it happens every day

An occasional delay is part of any organization. No company manages to make all information arrive at the exact moment every time. The problem appears when those small delays become a habit. Five minutes in one process. Another five in the next one. A validation that always takes a bit longer. A response that usually arrives when a decision should have already been made. Individually, they seem like minor situations. Accumulated over weeks or months, they end up changing the way the entire organization works. Teams begin to assume that certain responses will never arrive on time. They move tasks forward just in case, create parallel checkpoints, or look for information by asking other people directly. When delays become normalized, the company’s way of working changes too.

People end up adapting to the problem

Organizations have a huge capacity to adapt. If information usually arrives late, people find ways to live with that situation. They prepare part of the work before having all the data, make phone calls to confirm information that does not appear in the system yet, or create their own records so they do not depend on a single channel. These solutions allow work to keep moving forward, but they also hide the original problem. From the outside, it may look like everything is running smoothly. In reality, many people are spending time compensating for a workflow that could be much more seamless. When a process functions thanks to people’s ability to adapt, it does not always mean the process is working well.

Not all delays have the same impact

There is information that can wait a few hours without generating major consequences. Other information, however, loses much of its value if it does not arrive at the right time. A modification to a production order sent after manufacturing has started no longer prevents the mistake. An issue reported when the transport has already left will hardly allow the delivery to be reorganized. A material confirmation received too late can disrupt the entire schedule for the day. In these cases, the problem is not solely the content of the information, but the moment it arrives. The value of data depends as much on its accuracy as on its timeliness.

Speed is also part of quality

When a company talks about quality, it usually thinks about products, processes, or results. However, quality is also present in the way information flows. It is not enough for data to be correct. It must also reach the right person, through the right channel, and at a time when it can still be used to make decisions. Perfect information that arrives too late can have the same effect as incorrect information. That is why reviewing how information flows between departments is just as important as reviewing the production processes themselves. The quality of information does not only depend on it being correct. It also depends on it arriving when it is still useful.

A final reflection

Companies usually analyze major incidents, significant delays, or errors that generate an obvious impact. However, efficiency losses are often born from much smaller and repetitive situations. A validation that always takes a few minutes longer. A piece of data that arrives when the next department is already waiting. A decision that is delayed because a single piece of information is missing. Individually, they seem like unimportant details. Together, they end up slowing down the operation of the entire organization. Great inefficiencies do not always appear due to a single big problem. Many times, they are the sum of small delays that repeat every day.

👉 If an important piece of information were to arrive five minutes later than expected today, how many people would have to wait to continue with their work?

👉 How many of those small delays have already become so common that the organization has stopped perceiving them as a problem?