A quality hold can be entered correctly in the quality system, appear on a production dashboard, and update inventory status in the ERP. Then a planner calls the floor to find out whether tomorrow’s run can proceed. Customer service asks whether an order can still ship. Procurement wonders whether the next delivery needs to be rescheduled.
The data has moved. The decision has not.
This is a hypothetical situation, but the distinction is familiar in many operations. A September 2026 survey commissioned by Hexagon found that 77% of 511 U.S. manufacturing respondents described their operations as fully or mostly connected. Forty percent reported connection across design, production, quality, and business systems, while 39% reported limited feedback among design, manufacturing, and quality teams. Those responses do not tell us what is happening in any one factory. They do give leaders a reason to look closely at what “connected” means in their own. [1]
Follow the hold beyond the system
Suppose a lot is placed on hold after an unexpected quality result. Recording the hold is essential: it protects the lot from being used or shipped while the issue is assessed. But the operational consequence depends on information beyond the quality record. Is there usable inventory from another lot? Can the production sequence change without creating a different constraint? Is the affected order committed to a customer? When will quality have enough evidence to release, rework, or reject the material?
Each team may have part of the answer. Quality understands the basis for the hold. Planning understands the schedule. Warehouse staff know the physical location and status of available stock. Customer service knows what has been promised. Even if their systems exchange updates, no single update settles the trade-offs among those facts.
The handoff is where it becomes clear whether the operation is connected. A planner who sees “on hold” without an expected decision time may keep the run in place and wait. A warehouse team may know an alternate lot exists, while planning cannot see whether it has cleared inspection. Customer service may continue working from the original ship date because no one has said when that date should change. People compensate with calls and spreadsheets because the formal flow stops at visibility.
The useful question is not whether every person has access to every record. It is whether the hold triggers a shared decision at the point where the business still has options. In this example, that could mean defining who assesses the immediate production and customer impact, which information that person needs, how long the team can wait for a quality disposition, and who communicates a revised plan. The right arrangement depends on the plant, its risk controls, and the authority already assigned to each role. A software workflow can support it once the decision path is understood.
Close the loop after the order ships
Even a well-handled exception may repeat if the organization treats shipment as the end of the story. The hold is released or the schedule changes; the order goes out; everyone moves on. The original cause remains in a different team’s records, and the next production run encounters the same condition.
This is a second test of connectivity: did the information travel back to the place where the problem can be prevented? A supplier-related issue may need a conversation with procurement and the supplier. A process setting may need to be examined with production and quality. An unclear instruction may need to be corrected where work happens. The response depends on what the evidence shows, not on which system first recorded the event.
The Gelden article on Quality Control Circles makes a related point about feedback: when a team brings forward a recommendation, management’s decision and its reasoning need to return to that team. The same principle applies here. People who flag a recurring issue need to see what changed, what did not change, and why. Without that return path, the system may accumulate records while the operation loses the benefit of what people have learned.
One practical way to examine this is to take a recent hold and reconstruct its path. Start with the moment it was identified. Follow the record, the conversations, the schedule decision, the customer commitment, and the final disposition. Then follow the cause after the immediate pressure passed. Where did someone have to chase information? Which decision waited because its owner or required evidence was unclear? Did the people who could prevent a repeat hear the conclusion?
That exercise can reveal a missing system connection. It can also reveal that the systems did exactly what they were configured to do and the unresolved issue was a handoff, an authority decision, or a feedback loop. Those are different problems with different remedies. Understanding which one is present gives the next technology decision a better starting point.
For leadership, the measure of connectivity is not simply that the hold appears in four places. It is whether the business can respond while there is still time to protect the schedule and the customer, then use what it learned to reduce the chance of facing the same decision again.
Sources cited in article
1. Hexagon Manufacturing Intelligence, “77% of manufacturers call their operations connected. Only 40 really are,” September 17, 2026. Dynata survey of 511 U.S. manufacturing professionals conducted July 2026; commissioned by Hexagon.