“You didn’t even open the attachment, did you?”

“I saw the notification on my watch while I was in the elevator. It was a standard revision for the G-series housing. I hit ‘Approve’ and got on with the meeting. What’s the problem?”

“The problem is that it wasn’t a standard revision. It was a change to the bore tolerance for the press-fit bearing. We just authorized ten thousand units of scrap before the first shift even finished their coffee.”

That conversation didn’t happen in a vacuum. It happened in the hallway of a tier-two automotive supplier, and the silence that followed was the sound of a very expensive “optimization” hitting a brick wall. We’ve spent the last decade obsessed with removing friction. We want everything to be seamless, instant, and “frictionless”-a word that marketing departments use to describe heaven but that engineers should recognize as a description of a void.

The Biology of Limiters

I cracked my neck just now, a bit too hard, and the sharp twinge reminded me that some things shouldn’t move that fast. My body has these built-in limiters for a reason. If I could whip my head around like an owl without feeling a thing, I’d probably snap something vital without realizing it until the room started spinning.

Business processes are the same. We have engineered out the “stiff neck” of the approval process, and in doing so, we have engineered out the moment where a human being actually stops to think.

The Ghost of the Neon Folder

In the old days-which, let’s be honest, were only about fifteen years ago-an engineering change order or a quality deviation request was a physical object. It was a folder, often neon-colored so it wouldn’t get lost, and it sat on a desk. It sat there for a day. Maybe two.

We called that “lead time,” and we hated it. Lean consultants would walk the floor, see that folder sitting on Mike’s desk, and they’d calculate the “carrying cost of information.” They’d show us charts where that two-day delay was a literal sin against efficiency.

When a document sits on your desk for twenty-four hours, you see it three or four times. You see it when you put your keys down in the morning. You see it when you come back from lunch. You see it as you’re packing up to go home.

That repetitive visual contact creates a “low-resolution” processing in the back of your brain. On the third look, you realize that the part number looks familiar, or the tolerance seems tighter than the last three jobs you ran for that client. That “second look” is where the actual quality happens. It’s the “wait, a minute…” moment.

Now, we have replaced the folder with a push notification. The approval happens in the interstitial spaces of our lives-in the elevator, in the checkout line at the grocery store, or during the three minutes we’re waiting for a Zoom call to start. We have optimized for the click, but we have destroyed the cognition.

I’ve spent most of my career teaching people about financial literacy, and the one thing I always tell them is that the “cost” of a thing is almost never the price tag. It’s the opportunity cost, or the hidden liability attached to it. In manufacturing, the “cost” of a fast approval is the liability of un-deliberated action.

Think of it this way: research into industrial decision-making suggests that for every 20% increase in process speed, we see a corresponding 15% drop in what I call “peripheral detection.” If you read a sentence at 400 words per minute, you recognize the words perfectly. If you read it at 40 words per minute, you feel the tone. In a quality environment, we don’t just need people to recognize the “Approve” button; we need them to feel the risk.

Most software designers think that if they make the “Approve” button easier to hit, they’ve done their job. They’ve “reduced clicks.” But a Quality Manager’s job is not to click. A Quality Manager’s job is to judge. And judgment requires a specific type of temporal space that we are currently vacuuming out of our factories.

When you move to a digital environment, the temptation is to treat the workflow like a hot potato. Pass it on as fast as possible. The system shows a green checkmark next to your name, and your “Average Response Time” metric looks fantastic. You get a gold star on your quarterly review because you’re “responsive.”

I remember a specific instance where a client of mine-a small machine shop doing aerospace work-implemented a very basic document control system. It was basically just a glorified email chain with a digital signature at the end. They cut their ECO (Engineering Change Order) cycle time from six days to four hours. They were thrilled. They celebrated. Six months later, they had their AS9100 audit.

“I probably did it from my phone while I was on the shop floor,” he admitted.

– The Quality Manager, post-audit failure

The auditor didn’t care about the four hours. The auditor cared about the fact that three different people had signed off on a revision that violated the customer’s “frozen process” agreement. When the auditor asked the Quality Manager why he’d signed it, the manager couldn’t even remember seeing the document.

That’s the “responsiveness” trap. It’s the belief that because the data moved, the mind moved with it. It almost never does.

The Architecture of Confirmation

This is why the architecture of a quality system matters so much more than the features. If you are just digitizing a mess, you’re just making the mess happen faster. To truly handle the complexity of modern manufacturing-where you’re juggling ISO 9001, IATF 16949, and maybe some API Spec Q1 requirements-you need a system that understands that “approval” isn’t a gesture. It’s a confirmation of evidence.

A lot of people ask me what is QMS in manufacturing and how it differs from just a folder of PDFs. The difference is the “linkage.” In a true operating system for quality, the approval isn’t just a signature; it’s the closing of a loop.

You aren’t just signing a document; you are confirming that the inspection results trace back to the work order, which traces back to the revision-controlled drawing, which traces back to the calibrated gage.

When a system like QMS2GO handles this, it isn’t just “speeding things up.” It’s actually providing the context that allows the human to think faster without losing the depth of thought. If the system can show me, right there on the same screen as the signature, that the calibration on the micrometer used for that part is still valid, I don’t have to go find that information. My “thinking time” is spent on the actual problem, not on the scavenger hunt for data.

We often confuse “administrative friction” with “cognitive friction.” Administrative friction is the two hours you spend looking for a paper traveler or the day you wait for the inter-office mail. That is waste. We should kill it with fire.

Cognitive friction, however, is the resistance you feel when you’re about to do something important. It’s the pause. It’s the “Are you sure?” that pops up in your head. When we automate the approval chain, we often kill both types of friction at once. We throw the baby out with the bathwater, and then we wonder why the baby is at the bottom of the scrap bin.

I’ve made this mistake myself. I once “optimized” my personal billing system so that invoices went out automatically the moment a project was marked “Done” in my CRM. I saved myself three hours a month. I also accidentally billed a long-term client for a project that was “Done” in the sense that we had finished the work, but wasn’t “Done” in the sense that I’d agreed to give them a 15% discount for a bulk order.

By the time I realized the mistake, the invoice had been paid, the accounting was finalized, and I had to spend six hours of manual labor fixing a three-hour “optimization.”

The irony is that we are building these hyper-fast systems to satisfy auditors who, by their very nature, are slow. An auditor doesn’t care about your “Average Response Time.” An auditor cares about the “trail.” They pick up a finished part, and they walk it backward. They want to see the footprints.

If those footprints look like they were made by someone sprinting at full speed, the auditor starts digging. They know that nobody notices a non-conformance while they’re sprinting.

If you’re running a shop with 50 or 100 people, you can’t afford to let your judgment be a victim of your efficiency. You need the “Genie” in the system-the AI or the logic that does the heavy lifting of data aggregation-so that when you finally do hit that “Approve” button, you’re doing it with the full weight of the evidence behind you. You want the system to answer the boring questions so your brain is free to answer the dangerous ones.

We have to stop treating “delay” as a monolithic evil. Some delays are the sound of a gear catching. Some pauses are the only thing keeping the machine from shaking itself to pieces. If your QMS only focuses on how fast the document moves from Person A to Person B, you haven’t built a quality system. You’ve built a high-speed relay race for liability.

I’m still rubbing my neck. It’s a reminder that speed has a price. In the financial world, we call it the “liquidity trap.” In manufacturing, we should call it the “acceleration trap.” It’s the moment when the system moves faster than the people in charge of it can think.

Next time you see a “pending approval” notification on your phone, don’t hit it in the elevator. Wait until you’re at your desk. Wait until you can see the full picture. Give yourself the “second look” that the software tried to take away from you. The ten minutes of “waste” you incur by waiting might just save you ten thousand units of scrap.

Quality isn’t the absence of mistakes; it’s the presence of the system that makes those mistakes visible before they become history. We don’t buy software to be fast. We buy software to be right. And being right requires the one thing that no algorithm has yet mastered: the ability to look at a perfectly “compliant” screen and realize that something just feels wrong.

It’s the only thing that separates a Quality Manager from an expensive “Approve” button.