The 18:04 from Leeds is late, and Gary is sitting in his Peugeot Partner in a gravel yard in Horsforth, staring at a screen that says everything is perfect. The tablet, mounted with a suction cup that leaves a circular ghost on the glass, glows with the neon efficiency of a job-management app.

It shows tomorrow as a series of neat, interlocking colored blocks. Mrs. Okafor’s bathroom is a bright teal rectangle scheduled for 08:00. The plumber is green. The tiler is yellow. The delivery of the anthracite heated rail is a small, triumphant checkmark in the corner.

Gary knows the rail hasn’t arrived because he saw Mike, the delivery driver, three hours ago at a junction near Headingley. Mike looked like he’d been pulled through a hedge backwards; his eyes were glassy with the kind of flu that makes a man want to drive his van into a ditch and sleep for three days.

Mike didn’t have the rail because the warehouse in the Midlands had a “picking discrepancy.” This means someone, somewhere, looked at a shelf and saw air where a box should be.

Messy, Loud, and Human

In 1981, when Gary started as an apprentice, coordination was a series of frantic scribbles in a Filofax and a pocketful of ten-pence pieces for the phone box. It was messy, it was loud, and it was human.

If the rail wasn’t there, Gary would have spent his evening on the landline, pushing the tiler back a day and telling the plumber to go to the other job in Bramley instead. But today, the system has “optimized” the human out of the loop. The app has already sent a cheerful, automated SMS to Mrs. Okafor: *Great news! Your fitter is on the way!*

We digitize the visible workflow-the hours, the locations, the names-and we inadvertently delete the invisible workflow that actually makes the visible one possible.

A Specific Kind of Humiliation

I am particularly sensitive to these gaps today. I spent the better part of four hours this morning delivering a workshop on “Professional Integrity and Systemic Oversight,” only to realize, upon returning to my car, that my fly had been wide open for the entire duration.

It is a specific kind of humiliation: to stand before an audience and preach about the importance of checking details while a fundamental, physical detail is flapping in the breeze. We assume the system-the belt, the zipper, the social contract-is holding, while reality is quietly exposing us.

Modernization is the pursuit of a frictionless world. But friction is often what keeps the wheels from sliding off the road.

Every organization runs on informal coordination that no system diagram ever captures. It is the foreman knowing that the tiler, Dave, is going through a divorce and will be twenty minutes late every Tuesday. It is the plumber knowing that the water pressure in this particular terrace in Leeds is temperamental and will add an hour to the job.

When we replace Gary’s evening phone calls with an automated “logic” engine, we aren’t just saving time. We are dissolving the social tissue that holds the project together.

“The dog doesn’t care about the command. The dog cares about the truth.”

– Kai A., Therapy Animal Trainer

Kai A. once told me that dogs never look at what you’re doing with your hands. They look at your pupils and your breath. They see the “invisible schedule” of your nervous system. Software, by design, cannot see the truth of a warehouse discrepancy or a driver’s flu. It only cares about the command.

The Phantom Friction

The result is the specific modern misery of the homeowner who has cleared their morning, moved the kids to the neighbors, and sat down to wait, only to have a plumber arrive at 08:00 and realize he has nothing to plumb. The homeowner then enters the digital abyss, searching for “bathroom fitter turned up without parts,” hoping for a human answer in a sea of SEO-optimized forums.

The cost of this dislocation is hidden. On a balance sheet, the app looks like a miracle. But it has also increased the “phantom friction”-the 19-minute window for every 11 jobs where a tradesman stands in a hallway staring at a wall because the system failed to account for a flu-ridden driver in Headingley. This is a 7% drag on total productivity that never shows up as a line item because it is categorized as “on-site troubleshooting.”

When homeowners look into radiator sales, they are participating in a fantasy of completion. They see a finished room, a warm towel, a sleek anthracite finish that matches the taps. They are not buying a box of metal; they are buying the end of a process.

The failure of modern job-management is that it treats the process as a math problem rather than a logistical ballet. The logic of the app is the logic of the spreadsheet. It assumes that if Part A and Person B are assigned to Time C, then Result D is inevitable.

In my workshop this morning, I was technically “optimizing” my delivery. I had my slides in order. I had my statistics ready. I had my reframed human insights (like the fact that for every 27 minutes of labor, there are 4 minutes of “unrecorded adjustment”-the silent shim that makes the job fit).

The irony of the digital age is that we have more ways to communicate and fewer ways to coordinate. We send more messages, but we convey less truth. Mrs. Okafor’s phone pings with an update, and she feels a sense of security that is entirely unearned.

But the automated logic doesn’t know about Mike. It doesn’t know about the Midlands warehouse. It doesn’t know that Mrs. Okafor is a nervous person who has been saving for this bathroom for three years and will burst into tears if a plumber arrives and tells her he can’t start.

Gary Sighed.

Gary sighs. He turns the key in the ignition. The Peugeot rumbles to life, a mechanical relic in a digital world. He ignores the tablet. He ignores the “data silos.” He calls Mrs. Okafor.

“Evening, Mrs. Okafor. It’s Gary. Look, the system says we’re coming tomorrow, but the rail has been delayed. I’m going to move the tiler to Wednesday so we don’t have him standing around on your carpet for no reason. Is that okay?”

There is a pause on the other end. Then, a long exhale. “Oh, thank you, Gary. I was so worried about the tiler. How did you know?”

“I just knew,” Gary says.

He hangs up. The tablet glows, still showing the teal block at 08:00. In the eyes of the software, Gary has just committed an error. He has disrupted the optimization. He has created a discrepancy in the data. But in the real world-the world of anthracite rails and leaky valves and human anxiety-he has just saved the job.

We are currently obsessed with the “what” of our systems. We want to know what the app can do, what the data says, what the efficiency gain will be. We rarely ask about the “how”-the messy, unquantifiable way that people actually get things done. When we strip away the informal, we are left with a skeletal version of reality that looks good on a screen but collapses under the weight of a single flu-ridden driver.

The bathroom company’s app is a masterpiece of engineering that lacks a soul. It is a map of a city that has been demolished. It is a zipper that stays closed only when you don’t move.

Gary drives out of the yard, the gravel crunching under his tires. He has twenty-two years of experience in his head and a tablet on his dashboard that thinks he’s a unit of labor. Tomorrow, the app will flag him for a “scheduling conflict,” and he will have to explain to a twenty-four-year-old manager in a glass office why he went “off-script.”

He will try to explain about Mike and the warehouse and the “invisible schedule.” He will try to explain that the plan is just a guess, and the phone call is the reality. But he knows they won’t understand.