5:47 AM, Warehouse Rack 3, and Forty Flashing Modems
On a Tuesday morning in January 2024, I was standing in our Phoenix warehouse with a flashlight pointed at forty G310 5G gateways, all with their LED indicators blinking in what looked like synchronized chaos. We were supposed to ship them that afternoon to a regional public safety network buildout in Colorado. The full order was 2,400 units across three vendors, all fitted with Sierra Wireless modules. Ship date was Friday. Field crews were scheduled to start installing Monday morning.
I've been doing quality and brand compliance in the telecom equipment space for a little over six years now. Before that I was on the supplier audit side. These days I review every batch before it reaches a customer—roughly 200+ shipments a year, covering firmware loads, enclosure labeling, and commissioning documentation. We put a formal verification protocol in place back in 2022 after a hardware batch issue that embarrassed us badly. So modem indicator behavior should not have been keeping me up at night.
But that morning, something felt off.
The Sierra Wireless Modem Lights That Started the Whole Mess
Here's what happened. The field integration team had been commissioning the first wave of gateways on-site in Colorado, and they started calling in with what they described as "signal loss" alerts. The Sierra Wireless modem lights on roughly a third of the units were showing a pattern the crews didn't recognize—a slow amber pulse instead of the solid green they'd seen in the training videos. According to the quick-reference card we'd shipped with each unit, slow amber meant "no network registration." So the crews assumed the worst.
They escalated. Our support line got 23 calls in four hours. A supervisor on the customer side asked—reasonably—whether we needed to pause the deployment.
I had about 48 hours to decide whether to halt the remaining shipment or push forward. Normally I'd pull a few units into the lab, run them against a live network simulator, and confirm behavior before making a call. But the sim was booked for another project through Wednesday, and the customer was under their own deadline pressure. So I went with the fastest option available: I pulled the full Sierra Wireless module documentation, cross-referenced the LED behavior tables, and started reading.
That's when I found it. The slow amber pulse wasn't "no network registration." It was "registered on a roaming partner network." The quick-reference card we'd been shipping simplified a 14-state indicator matrix down to six states, and it had collapsed two very different conditions into the same color description. The modem was working exactly as designed. Our documentation was the problem.
A Blood Pressure Monitor Manual Made the Pattern Click
Here's the part that still makes me shake my head. Two nights before the warehouse morning, I was at my mother-in-law's house helping her set up a new blood pressure monitor. She'd been struggling with the symbols on the display—specifically, an irregular heartbeat icon that looked almost identical to the standard measurement-error icon. Both were small, both were roughly circular, and neither had a label in the quick-start guide. She'd been taking readings, seeing the icon, and assuming her readings were invalid. It turned out half of them were fine; she just didn't know which half.
The connection didn't hit me until I was deep in the Sierra Wireless LED tables. Blood pressure monitor symbols, modem indicator lights, TV on-screen setup menus—they all rely on a compressed visual language that assumes the user already knows the distinctions. And when the icon set is ambiguous and the manual is thin, people guess. Sometimes they guess wrong in ways that cost real money.
(Side note: this is also why I now pay attention to where consumer electronics are sourced. We'd recently ordered a batch of 55" displays for a new operations center, and—as often happens—the shipment came from multiple factory locations. Three different countries of origin, three different remote layouts, three subtly different setup menus. Same model number on the box. If you've ever wondered where are TVs made and why setup feels inconsistent between identical units, this is the reason. The country of origin changes the firmware defaults more than most buyers realize.)
What the Mistake Cost Us
In hindsight, I should have pushed back on the ship date the moment the first calls came in. But with the customer's field crews already on-site and our own production schedule locked, I made the call with incomplete information. Even after I confirmed the modems were behaving correctly, I kept second-guessing myself for two days—what if there was a firmware variant issue we hadn't caught? The uncertainty didn't resolve until the first 600 units were live on the customer's network and reporting normally.
We still ate costs. Here's roughly where it landed:
- Rework on documentation inserts: $6,200 (design, print, hand-insert into 2,400 boxes already staged)
- Overnight shipping on corrected reference cards to the Colorado site: $3,400
- Field team idle time during the 11-day partial pause: approximately $7,000
- Customer goodwill—honestly, hard to price. We got lucky that their program manager had worked with us before.
Total: just over $18,000, plus an 11-day partial deployment delay that I had to explain in writing to two levels of management.
After that, I rewrote our commissioning documentation standard. Every indicator state on any device we ship now has to be documented with a distinct visual example, a plain-language description, and a one-line "if you see this" action. No more collapsing multi-state indicators into simplified color ranges. The rejection rate on first-article documentation review dropped from around 14% to under 4% over the following three quarters.
What I'm Still Not Sure About
I want to be honest about the limits of what I learned here. The fix worked for our products and our customers, but I'm not convinced it generalizes cleanly. Some manufacturers deliberately compress indicator states to reduce training burden—and for some product categories, that's a reasonable tradeoff. My mother-in-law's blood pressure monitor, for example, serves a use case where users interact with it twice a day for years. Maybe a tiny icon set is the right design choice there, and a better manual is the actual fix.
What I do know is this: no diagnostic indicator system is self-explanatory. Sierra Wireless modules, blood pressure monitors, consumer TVs—they all compress complex state information into a few colored pixels or symbols, and they all assume a level of familiarity that most end users don't have. If you're specifying equipment for a deployment, budget the time to map every indicator state against the actual user's mental model. If you skip that step, you'll pay for it later. I paid $18,000 to learn that, and I'd rather you didn't have to.
One last thing—check the country of origin on your equipment batches before they ship. If the same SKU arrives from multiple factories, assume the documentation and firmware defaults will differ. Build a verification step for that. It's a small checklist item that saves a very large headache.