Most of the work happens between the systems

Every company has software. The software handles part of the job. There's always a gap between what the system does and what the operation needs, and someone fills that gap by hand.

The designer opens one program to draw the thing and another to price it. The two don't talk to each other, so the designer types the same dimensions twice - once where the design lives, once where the estimate lives. This happens 30 times a week. The designer knows which fields round differently, which entries the second system rejects if the format isn't right. Speed comes from years of practice.

A production manager arrives at the shop early every morning. Not to run production - to build the spreadsheet that tells everyone else what to run. The scheduling software stopped being accurate a while back. Someone started keeping a parallel version in Excel. The Excel file is the real schedule now. It gets rebuilt from scratch every day, on one machine.

This is what most operations look like up close. Not broken. Running on manual steps that fill the space between what was purchased and what was needed.

The work happens in that space. Building the connection between the two systems so the person doesn't have to carry the numbers by hand. The designer who typed everything twice gets three hours back. The production manager still arrives early, but reads the floor now instead of rebuilding a file.

The story could stop here. That's the version that fits on a slide.

But there's something underneath that keeps surfacing. The gap isn't always waste. Sometimes the manual step exists because the person doing it catches errors the automation wouldn't. The morning spreadsheet isn't just redundant - it's a quality check. A moment where someone who knows the operation looks at the numbers and knows something is off before anyone else could.

When the bridge gets automated, something is lost. Speed increases and a set of eyes disappears. The designer who typed everything twice was also checking it twice. The production manager who rebuilt the file every morning was also reading it every morning.

There's no clean answer for this. The goal is to build the check into the automation. To keep the judgment without keeping the labor. Sometimes it works. Sometimes it doesn't, and the gap shows up later.

The work between the systems isn't all waste. Some of it is judgment that looks like data entry. The hardest part is telling the difference before building the thing that replaces both.