UpTrajectory Review

Pam Didner's piece for Inc. opens with a scenario every small business operator will recognize: the internet is slow, the team is frustrated, and the obvious fixes keep failing. She upgraded to fiber, added a WiFi booster, and tinkered with software settings. None of it worked. The actual culprit was a single aging Ethernet cable hiding somewhere in the office infrastructure, and swapping it out tripled her connection speed. It reads like a parable, and that is exactly why it is useful. The available text is thin, but the headline and framing tell us this is a first-person diagnostic story — the kind of operational post-mortem that rarely makes it into business media because it is too small, too unglamorous, and too embarrassingly simple.

For a small business operator, this is not a story about cables. It is a story about how operational problems get misdiagnosed at the small-business scale, where nobody has a dedicated IT department and the person making technology decisions is also running payroll, managing vendors, and answering customer emails. When something breaks, the instinct is to reach for the visible, expensive fix — a faster plan, a new device, a software subscription. Didner's experience is a reminder that the cheapest component in the chain can silently cap the performance of everything downstream, and that you can spend real money upgrading around a problem without ever touching it.

What is genuinely valuable here is the diagnostic discipline, not the plot twist. The lesson is not 'check your cables' — though you should — it is that when a fix does not work, the right move is to question the entire signal path, not just the parts you already suspect. Didner tried three reasonable interventions before finding the real bottleneck. That is three rounds of wasted time and money that a methodical audit of the physical layer would have prevented. We are fully on board with the piece's implicit argument: before you spend another dollar on bandwidth or hardware, trace the actual path your data takes and test each link in isolation.

The second-order effect worth sitting with is what this pattern costs beyond the line item. Slow networks tax productivity in ways that are easy to normalize — files take longer to sync, video calls stutter, cloud tools lag, and employees develop workarounds that introduce their own inefficiencies and security risks. Multiply that across a five- or ten-person team for months and the hidden cost dwarfs the price of a cable. There is also a vendor-incentive problem: your ISP wants to sell you more bandwidth, and hardware makers want to sell you new devices. Nobody profits from telling you to inspect the $8 cable behind the desk, which is precisely why nobody does.

The practical takeaway is straightforward. If your office network underperforms, map every physical connection between the wall and the workstation before you spend anything. Replace any cable you cannot date, especially ones that predate your current internet plan, since older cables may not be rated for the speeds you are now paying for. Test speed at the router, then at each desk, and note where the drop-off happens. And if you are about to sign a contract for faster service, run that audit first — you may discover you are already paying for speed you cannot reach.

“Replacing one old Ethernet cable tripled the connection speed.” — Inc. Magazine

Takeaway: Audit every physical cable in your network before spending on upgrades — one outdated component can silently cap everything downstream.