A $15 barcode scanner saved my company $70,000 in two days. But this isn’t really a story about a scanner. It’s a story about what happens when everyone accepts a broken process — and one person decides not to.
I was working for a company that manufactured electronic devices when a recall hit. Fifteen thousand circuit boards were defective. The problem was, we had 250,000 units out in the wild. So customer support couldn’t just swap every return with a new device — they had to verify that each board coming back was actually part of the bad batch.
The process they came up with was brutal. A manager would pull a number off the returned board, open the first spreadsheet, match the part number, find the corresponding batch number in a second spreadsheet, then cross-reference that batch number against a third spreadsheet of known defective components. Three spreadsheets. Every single time.
After two weeks of this, they’d processed 30 units.
Thirty.
Meanwhile, about 1,500 returns were already sitting in a pile, and more were arriving daily. The managers were buried. Their actual teams — the people they were supposed to be leading — were on their own.
That’s when the customer support managers came to me. They knew it was broken. They just didn’t know how to fix it.
So I went over to their area and watched the process. Three spreadsheets doing what one lookup should do.
So I wrote a quick VBA script. Nothing fancy — just software that automated the cross-referencing so they could type in a part number and get an answer immediately instead of hunting through files.
The next day they processed 100 units. That was a real improvement. But I kept watching.
That’s when I noticed the barcode.
Every single board that came in had a barcode printed right on it. They’d been reading the numbers off by hand and typing them in, one at a time, while the answer was literally scannable.
I knew the hardware engineering team had a barcode scanner, so I borrowed it. I needed to prove the concept — could I scan the barcode and feed it straight into the VBA script? It worked. But engineering wanted their scanner back, and I understood why. It was a 3D scanner, a $300 piece of equipment. Probably worth buying one, but then I looked more closely at the barcode on the circuit boards. It was a 2D barcode. I didn’t need a $300 scanner — I needed a $15 one.
I found a basic 2D scanner on Amazon. It arrived the next day.
I plugged it in, integrated it with the script, and handed it to the team. That day they cleared 2,000 units in a single shift.
Let me put that progression in perspective:
- Week 1–2 (manual process): 30 units total
- Day 1 with the script: 100 units
- Day 1 with the scanner: 2,000 units
If they’d kept going with the original process, I estimated it would have cost the company about $70,000 in labor just to work through the backlog. Instead, it cost $15 and a few hours of writing code.
Here’s the thing that still sticks with me about this story. Nobody was doing anything wrong. The managers were working hard. They were doing exactly what they’d been asked to do. The process just had so much friction baked into it that hard work couldn’t overcome it.
The fix wasn’t some genius engineering breakthrough. It was noticing. Watching a process long enough to see where the friction actually lived — and then refusing to accept it.
Most of the expensive problems I’ve seen in my career weren’t technology problems. They were friction problems that nobody stopped long enough to look at.
The same pattern shows up in every medical practice I’ve walked into. The double data entry, the three-click workaround, the “that’s just how we do it here.” The fix is almost never the technology. It’s someone deciding to stop and look. If you’re ready to stop and look, let’s talk.
Leave a Reply