ENTRY 19 ยท 2026ยท09ยท06 ยท Shift Log

The Cost That Never Gets an Invoice

Electricity was available for forty years before the productivity gain arrived. Nobody blocked it. Ask your crew when a pump last had its motor changed, time the answer, and you are standing in the same gap.

A workaround is paid in hours already on the payroll, so it never becomes a line โ€” and a cost with no line never reaches anyone who could decide about it.

20minutes to answer one question about one pump โ€” and the record existed the whole time

01Forty years of available and unused

Take electricity. It was available from the eighteen eighties. Factories could buy it, wire it, and run it. Then for forty years, almost nothing happened. The productivity gain did not arrive until the nineteen twenties.

Nobody blocked it. Nobody voted against it. There was no meeting where a committee weighed electric power and turned it down. It sat there, available and unused, for four decades โ€” and the reason is the interesting part.

Factories bolted the new motors onto the same overhead shafts, driving the same belts, in the same building, with the same floor plan. What took forty years was not the motors. The gain came when somebody redesigned the floor itself, around the fact that every machine could now have its own motor.

That gap has a shape, and your plant is standing inside it right now.

02We have known the fix for forty years

This is not an unsolved problem. Lean and Six Sigma did it on the factory floor: they separated the time that adds value from the time that does not, and then they attacked the second one.

Armand Feigenbaum, who invented total quality control decades before Six Sigma, had a name for that second kind of time. He called it the hidden organisation โ€” that part of your organization that exists to do bad work โ€” and he put it at anywhere from about twenty to forty percent of the total capacity of many American companies. That was in 1994.

The discipline worked. It never crossed into software.

A tool can now be built in an afternoon. Permission to use it still takes ninety days, and ninety days is the optimistic version โ€” most teams still measure new software in months, sometimes a year. Almost none of that time is spent building. It is scoping, queuing, review, and waiting for a slot.

That waiting leaves no record. It never lands on a line, so it never reaches anyone who decides.

03The picture in people's heads is wrong

There is a second reason nothing moves, and it is not a budget. It is a picture.

Ask most plants what adopting AI looks like and you get robots, drones over the stockpile, an autonomous control room. So it becomes a capital project with a steering committee and a three-year roadmap that needs a budget cycle before it needs an engineer.

Meanwhile the actual win is smaller and duller than that. It is a report that assembles itself. The same number no longer typed into three systems. A handover that writes itself out of what the crew already recorded.

Gartner surveyed the global labour market this year and found that the large majority of employees who already have enterprise AI access use personal AI tools for work anyway. Read that twice. The work is already being done โ€” invisibly, on the wrong tools, by people nobody thought to ask.

04The twenty-minute question

Here is what is different this time, and it is the whole point: that redesign moved steel. This one moves a form.

Ask your floor a simple question. When did this pump last have its motor changed? The system you have right now takes twenty minutes to answer that โ€” because it probably was captured, in a report inside a folder somebody has to find, or an email addressed to somebody else that has to be dug up, or you are tracing permits to see what was open that day. Then you call the person who did it, just to make sure.

The record existed, and you still had to phone someone.

Now ask what the answer was for. Somebody is deciding whether to run that pump or open it up. Twenty minutes late, that decision gets made on memory. Sometimes that is rework. Sometimes it is a shift of lost production.

And sometimes the question is not about a pump at all. On Piper Alpha, in 1988, the record existed too. A pump was down for maintenance and its safety valve had been removed โ€” two permits, for the same pump, on two different decks. The night shift knew the pump was down. They would not have known the valve was gone. A hundred and sixty-seven men died. Lord Cullen asked four questions of that permit-to-work system, and the answer to all four was no. That story is Entry 05.

05Available, and switched off

Those twenty minutes are not the job. They are the bill for a moment nobody captured properly the first time.

Capture it once, as it happens, and that question is answered instantly. That is not a three-year programme. That is this month, with technology that is nearly a decade old. If a change still takes months, you are not paying a team to build. You are paying them to queue.

Which is the same shape as the forty years. The power was there the whole time; what was missing was somebody redesigning the floor around it. Like having electricity, and leaving it switched off.

Only the leaders can switch it on โ€” and only if they notice the technology everyone is supposed to be using already.

Take this onto shift

Pick the question your crew asks most often. Time it once, honestly, from asking to answered. Then count how many times a year it gets asked, work out what the answer was for, and change one thing.

Sources: Armand Feigenbaum, IndustryWeek, 4 July 1994. Paul David, The Dynamo and the Computer, American Economic Review 80(2), 1990. Lord Cullen, The Public Inquiry into the Piper Alpha Disaster, 1990. Delivery-time and AI-adoption findings: Google's DORA 2025 report and Gartner's 2026 global labour-market survey.

A question about one pump opens onto the forty years electricity sat available and unused, the queue that swallows a software change, the robots people picture instead of the report that assembles itself, the four places the answer already sat, and a live conductor feeding machines that are still switched off PUMP โ€” MOTOR CHANGED? ? when did this pump last have its motor changed? twenty minutes to find out 1880s โ€” AVAILABLE 1920s โ€” THE GAIN forty years, available and unused NOBODY BLOCKED IT THE WORK โ€” WHAT LEAN ATTACKED VALUE EVERYTHING ELSE A SOFTWARE CHANGE โ€” NEVER ATTACKED BUILD SCOPING ยท QUEUE ยท REVIEW ยท A SLOT the waiting leaves no record WHAT PEOPLE PICTURE A REPORT THAT ASSEMBLES ITSELF already happening, on the wrong tools THE ANSWER WAS RECORDED โ€” FOUR TIMES REPORT EMAIL PERMIT A PERSON PARTS CONTRACTOR DOWNTIME the twenty minutes WHAT REACHES THE ACCOUNTS OPEN AVAILABLE โ€” AND STILL DARK only the leaders can switch it on

Ask when the pump last had its motor changed. Somebody knows. That is not the same as the plant knowing. Electricity was available from the 1880s. The productivity gain arrived in the 1920s. Nobody blocked it. Lean attacked this waste on the floor forty years ago. The identical shape in software was never touched. People picture robots, so it becomes a capital project. The actual win is a report that assembles itself. Nothing was missing. The answer sat in four places, and none of them reached the accounts. The conductor is live and the machines are dark. The switch is open, and it is above the floor's reach.

Get the next piece.

Get the free field guide โ€” The Handover Gap: three disasters, one lesson, and a checklist for your next shift. Plus the occasional piece worth your shift. No noise, no pitch.

Run a shift somewhere? I compare notes with operators and supervisors on how real floors handle handover and capture โ€” what works, what quietly doesn't. No pitch; I'm not selling anything. Tell me how yours does it: [email protected]