The Day We Got the Forklifts Out of the Break Room

There’s a moment in every manufacturing operation where you realize a process that works isn’t the same as a process that’s working well.

At a brick manufacturer I worked with — four plant locations spread across North Carolina and into Texas — that moment was watching a truck driver walk across a brick yard looking for a forklift operator.

Here’s how it worked before. A truck would pull into the yard. The driver would walk into the front office, check in with staff, and get handed a ticket and a bill of lading. Physical paper. Then they’d walk back to the truck, drive around to the loading area, and start looking for someone on a forklift.

Sometimes the operator was right there. Sometimes they were in the break room. Sometimes they were somewhere in a three-acre brick yard. The driver waited. The truck sat. The clock ran.

It wasn’t chaos. It worked. But in manufacturing, “it works” is the floor, not the ceiling.

The fix wasn’t complicated. The execution was.

The solution was straightforward in concept: get the order information to the forklift operator before the truck arrives, so when the driver pulls in, someone is already moving brick.

What that required in practice was less straightforward. We needed WiFi coverage across an outdoor brick yard — not a climate-controlled office, a working industrial yard with dust, heavy equipment, and zero existing wireless infrastructure. We needed a device that could survive that environment and mount securely to a forklift. We needed that device to talk to the ERP system that already held all the order data. And we needed the front office check-in process to trigger all of it automatically.

iPad Minis. Custom mounts. Industrial-grade cases. A wireless network built out into the yard. And an integration between the check-in workflow and the ERP that pushed order details directly to the floor the moment a driver signed in.

None of those individual pieces were complicated. Getting them to work together, reliably, in an environment that wasn’t designed for any of them — that was the job.

What changed.

After the buildout, a driver pulls in and checks in at the front office — same as before. That’s where the similarity ends.

The moment they sign in, the order details appear on the iPad mounted in the forklift. The operator sees what’s needed, where it is, and when to expect the truck. They’re already moving before the driver gets back behind the wheel.

No paper changing hands on the yard. No driver wandering around looking for a human. No forklift operator waiting to find out what the next job is.

The truck gets loaded faster. The driver gets out faster. The yard runs cleaner. And the forklift operators spend their time moving brick instead of waiting for instructions.

The larger point.

This wasn’t a technology project. It was a workflow project that required technology to solve it.

The ERP system already had all the information. The forklift operators already knew how to do the job. The gap was the twelve minutes between “order exists in the system” and “forklift operator knows about it.”

That gap cost money every day. Not dramatically. Not in a way that showed up on a single line of a P&L. But multiplied across every truck, every shift, every day of the year — it added up.

Most manufacturing operations have a version of this. A process that works, built around a constraint that no longer has to exist. The constraint just never got removed because nobody stopped to ask why it was still there.

That’s the question worth asking.