- Fiber Done Right
- Posts
- Where It's Going (If We Keep Going Down This Road)
Where It's Going (If We Keep Going Down This Road)
We’re not heading toward a future failure. We’re living in the early stages of it right now. If you’ve been around long enough, you don’t need a report to tell you something’s off. You’ve seen it. You’ve felt it. Maybe you’ve even worked around it. The shortcuts. The misalignments. The unexplained test failures that get chalked up to “weird weather” or “bad glass” when everyone knows the real issue is buried somewhere between poor documentation and rushed construction. The future we’re talking about isn’t hypothetical. It’s already built into the system. We’re just waiting for the timeline to catch up.
No one wants to admit it because admitting it means we might have to slow down. It means we might have to hold someone accountable. It means someone might have to say, “This isn’t working,” and back that up with action, not just another meeting. But the signs are everywhere. Jobs are passing inspection but failing in the field. Routes are marked complete, but no one can explain the logic behind the splices. Test results look fine one day, then show massive losses the next. And the worst part? Everyone sees it, and no one wants to stop long enough to fix it.
Because stopping feels like failure. Admitting a mistake feels like weakness. And in an industry built on deadlines and pressure, weakness gets punished. So we keep moving. We keep closing out jobs that aren’t truly complete. We keep pretending that “it passed” means “it’s solid.” But deep down, the ones who’ve been through a few cycles know the truth: we’re building something that looks strong but is structurally unstable. The cracks didn’t come from one major failure. They came from the slow buildup of quiet decisions no one had the time, or the backing, to challenge.
Look, fiber won’t scream when it starts to fail. It won’t send out an alert saying, “The way you built me was flawed.” It’ll just degrade. Quietly. Slowly. First a little latency. Then a few drops. Then a full segment outage. By the time the damage is obvious, the contractor is gone, the documentation is missing, and the city is stuck wondering what went wrong.
So no, this isn’t a warning. It’s a mirror. We’re not forecasting a storm. We’re already walking in the rain. The question isn’t whether the current road leads to problems. The question is how long we’re going to pretend we don’t see them coming.
Fiber doesn’t fail dramatically. It fails quietly. That’s the problem. When a splice is dirty or a bend radius is too tight, it doesn’t explode. It doesn’t send out sparks or trigger a shutdown. It just introduces loss. Maybe a little at first. Enough to be invisible to a quick test. But it’s there. And it’s not going anywhere. That one decision, whether it was a rushed cut, a lazy backfill, or a splice that wasn’t cleaned properly, starts the clock on future failure. And the worst part? Nobody will connect it to the moment it happened. By the time the service degrades, it’ll be months or years down the road. The original crew is long gone. The prints are outdated. And everyone’s left trying to diagnose a ghost.
That’s what’s so dangerous about the kind of infrastructure we’re laying right now. It doesn’t break in the moment. It breaks over time. And because of that delay, no one feels the urgency to correct it. If you rush a copper install and something goes wrong, you get sparks, heat, or immediate failure. You know where to look. You know what to fix. But fiber lets you believe you got away with it. You bent it too tight? It passed. You buried it shallow? It passed. You skipped the slack or ran conduit through rock without proper bedding? Still passed. But passing doesn’t mean permanent. It means postponed failure.
And what’s really happening is this: we are burying problems beneath layers of silence. Handholes are getting closed with undocumented splices. Duct runs are getting sealed with foam and hope instead of proper mechanical couplers. Restoration is being faked for photos and forgotten in reality. The infrastructure is literally decaying from the moment it’s installed. The materials are solid. The technology is proven. The failure comes from the part no one wants to look at, the rushed, compromised labor that was never given the time or support to do it right.
Here’s an example that should hit home. A bore crew hit rock on a rural build. Instead of logging it and adjusting the depth, shoved the duct through a jagged path, and marked it done. Six months later, the duct was compromised. Not on day one. Not during inspection. But during a freeze-thaw cycle that shifted the soil just enough to put pressure on a stress point that had no business existing. The repair cost five times what the initial correction would have. And no one paid for that delay except the local provider and the customers who went without service.
And this isn’t isolated. This is happening everywhere. The only difference is that most of it hasn’t surfaced yet. But it will. Every shallow duct run, every splice thrown together on a tailgate, every missing slack loop and misaligned bore path, they’re all time bombs. And we’re building miles of them.
We talk about broadband like it’s the future of communication. But what we’re really laying is a silent record of the decisions we made in the field. And when those decisions are made under pressure instead of principle, what we leave behind is not infrastructure, it’s decay. It just hasn’t shown itself yet.
The Cost Curve Is Inverted
Most people think the expensive part of fiber is the construction. The trenching. The boring. The splicing. The manpower. They believe the cost curve peaks during the build, and then flattens out once the network goes live. That’s not true. That’s a dangerous illusion. Because in fiber, the most expensive problems don’t show up until the job is already closed. And by then, it’s too late to fix them without tearing up what you already buried.
This is the part no one budgets for. Rework. Emergency response. Trouble tickets that can’t be resolved with software because the issue is physical. Misplaced ducts. Broken fibers. Failed splice trays. It’s not the material that costs the most. It’s the time it takes to uncover, inspect, repair, and restore something that should have been done right the first time. The backhoe costs the same. The truck roll costs the same. But when you’re doing it in reverse, under pressure, with a customer on the line and a team scrambling to find something that was never documented, the cost multiplies. And the blame multiplies with it.
You can build a bad network cheap. But you can’t maintain one cheap. That’s where this entire model breaks down. The cost curve is backward. You save a few thousand dollars on the front end, only to pay hundreds of thousands later in rework, complaints, and damage to your reputation. And none of that shows up on the balance sheet until it's already costing you revenue.
When a fiber segment fails in the middle of winter, the response isn’t technical, it’s physical. A crew has to be dispatched. A route has to be located. Snow has to be moved. Frozen ground has to be dug. And the entire team has to work from assumptions because the original records are either missing, incomplete, or wrong. That’s not a minor inconvenience. That’s a complete collapse of efficiency. And every one of those hours burns dollars faster than any trench ever did.
And who pays for that? Not the contractor who left early. Not the engineer who drew it wrong. Not the PM who got overruled. The owner does. The provider does. The city does. The customer does. The cost doesn’t disappear. It just shifts. From the build to the future. From today to tomorrow. And if you’re not measuring that, you’re not seeing the full picture.
This is the lie that’s baked into most bids. The promise that a fast, cheap build is a smart financial decision. It’s not. It’s a delay tactic. And if you’ve ever had to troubleshoot a bad splice tray three feet underground, with no slack, no markings, and no documentation, you already know exactly how expensive that shortcut becomes. It’s not just frustrating. It’s punishing.
The industry talks about efficiency like it’s a speed game. But real efficiency is about reducing the total cost of ownership. Not just what it costs to install the network, but what it costs to live with it, maintain it, and expand it. Right now, most of the networks being built are optimized for invoices, not for infrastructure. That’s why they’re falling apart before they even get fully loaded with traffic.
If the goal is short-term savings, then yes, cut corners, move fast, bury the problem. But if the goal is long-term value, then every shortcut costs more than it saves. Every missed detail becomes a bill with interest. And every mistake you don’t see now becomes a crisis you’ll pay for later.
The Workforce Will Erode
Fiber doesn’t just demand precision from the equipment. It demands pride from the people. You can’t build lasting infrastructure with burned-out workers, ignored feedback, and a revolving door of undertrained crews. But that’s where we’re headed. The labor exists. The talent is out there. What’s missing is a system that values them. One that builds people up instead of grinding them down and discarding them when the pressure hits.
Start with the crews. The guys out there every morning, rain or shine, moving dirt, pulling duct, placing handholes. These aren’t incapable workers. These are people who show up early, stay late, and solve problems in real time. But they’re working inside a system that constantly tells them: speed first, everything else second. And that message wears them down. It chips away at their pride. The guy who used to loop slack because he cared about doing it right eventually skips it because no one ever checked. The tech who used to label trays with precision eventually stops because the prints were never updated anyway. The message is clear: quality is optional, completion is mandatory.
That is how pride dies. Not all at once. Not with a big betrayal. But slowly. Silently. Through a thousand little compromises that make people stop caring. And once pride starts to slip, the work starts to slip. And when the work slips, leadership starts to blame the workers. It’s backwards. Crews aren’t failing the system. The system is failing the crews.
Now look at the project managers. These are smart, capable people thrown into a pressure cooker and told to manage chaos. They’re supposed to translate between engineering, construction, permitting, material delivery, inspections, and client expectations, all while tracking paperwork, holding schedules together, and cleaning up everyone else’s mess. And they do it. Every day. But it costs them. The stress, the reactivity, the lack of support, the constant pressure to move faster without asking questions, it grinds them down. Good PMs don’t leave because they can’t do the job. They leave because they know the job shouldn’t be this broken.
Engineers feel it too. The ones who actually care, the ones who want to build it right, keep getting overruled by schedule demands and scope creep. They design something smart, buildable, aligned with real-world conditions, only to have it get cut up, value-engineered, or ignored in the field because no one had time to review the prints. After a few cycles of that, they stop fighting. They stop asking questions. They draw what they’re told, send it downstream, and check the box. Caring hasn’t disappeared. It’s just been worn down by a system that rewards quiet compliance over thoughtful resistance.
And what happens next is the slow death of expertise. The good people, the ones who know what right looks like, the ones who care about the work, they start looking for something else. Some of them leave the industry altogether. Others stay but go quiet. And the next generation? They come into a culture that stopped teaching. A culture that rewards silence and punishes standards. A culture where the only thing that matters is whether it passed inspection, not whether it was built with integrity.
That’s how you lose a workforce. Not in one big moment. But over time, through erosion. You lose the voice of the guy who used to speak up. You lose the extra effort from the woman who used to double-check everything before signing off. You lose the wisdom of the engineer who used to walk routes and explain things to the crew. You lose the leadership of the PM who used to hold the line. And what you’re left with is people just doing what they’re told, even when they know it’s wrong.
And once that happens, it’s hard to get back. Pride doesn’t bounce back with a memo. Trust doesn’t rebuild with an email. It takes time, clarity, leadership, and a system that values the people doing the work, not just the work getting done. If we keep going down this road, the builds won’t just suffer. The people will. And when they’re gone, so is the chance to build this right.
The Reputation Collapse
Fiber networks don’t just carry data. They carry trust. Every install, every splice, every foot of duct in the ground is a promise. A promise to the customer that this will work. A promise to the city that this will last. A promise to the provider that this was built the right way. And right now, we are breaking that promise, one bad build at a time.
Most ISPs and municipalities won’t see the failure coming until it hits their front porch. While the network is going in, it all looks like progress. Footage is getting installed. On paper, everything looks fine. The metrics say it’s complete. The photos say it’s progress. But then the complaints start. Slowly. Quietly. A few service tickets. Some repeat calls. An outage no one can trace. A contractor who disappears when a repair is needed. A splice tray that makes no sense. And all of a sudden, that good press flips.
Because customers don’t care how much fiber you buried. They care about what works. And when it doesn’t work, they don’t blame the shortcut. They blame the provider. They blame the city. They blame the brand that put their name on something that’s falling apart. It doesn’t matter who built it. It matters who owns it. And when it starts to fail, there is nowhere to hide.
I’ve seen it happen more than once. A city proud to announce fiber expansion, only to get hammered by the public a year later because connections are unstable, restoration was sloppy, and outages keep piling up. Leadership starts scrambling for answers. Engineers start digging through old files. Nobody can find the documentation. Nobody can explain the design. The build is a mystery. And now, the trust is gone.
And here is what most people miss. The collapse doesn’t start with bad intentions. It starts with blind spots. Decision-makers assuming the job is done because the paperwork says so. Leaders trusting contractors without understanding the work. Cities approving pay apps without walking the site. Everyone thinks someone else is watching the details. But no one is. And once the network fails publicly, it’s too late. You don’t get a second chance to prove you did it right. You only get one shot. And if the service breaks before the ribbon fades, people remember.
This industry does not run on goodwill. It runs on performance. You either deliver what you promised, or people stop listening. You either hold the standard, or the market finds someone who will. And when word gets around that your builds are failing, it spreads fast. Contractors won’t say it outright. Crews won’t put it in writing. But they know which companies care about quality and which ones are just checking boxes. They talk. They compare. They share photos. And eventually, that reputation trickles back up the chain.
Here is the most dangerous part. A failed build is easy to fix. A failed reputation is not. Once trust is broken, every future project becomes harder. You have to work twice as hard to prove you’ll do it right. Every bid gets more scrutiny. Every meeting gets more defensive. Every contract gets more complicated. Because no one wants to be the next one holding the bag when it falls apart again.
And let’s not pretend the public doesn’t notice. They may not understand bend radius or slack loops. But they understand buffering. They understand missed appointments. They understand paying for a premium service that barely works. And once the customer loses trust, it takes years to earn it back, if you ever do.
So when we talk about cutting corners and rushing installs, it’s not just about a bad handhole or a mislabeled tray. It’s about eroding the one thing this industry cannot survive without, credibility. And if we keep building with our eyes closed, our names are going to be on the networks that fail. Not just physically, but publicly.
The Trap of “Scalable Mistakes”
The most dangerous thing in fiber construction isn’t the mistake. It’s the fact that we’ve built a system that scales those mistakes across hundreds of miles without ever stopping to fix them. Everyone talks about scalability like it’s a good thing. Like it means we’re doing something right. But scalability just means you get more of what you’ve already built. So if you’re doing it wrong, faster, you’re not progressing. You’re compounding failure.
This is the trap. You build one job fast. You hit your footage goal. You hit the light test. You move on. And nobody checks whether the handholes were set right. Nobody verifies if the bore logs match the print. Nobody cares if the slack was looped or just coiled like an afterthought. It passed. The report was clean. The city signed off. So now that becomes the blueprint. That’s how the next one gets built. And the next. And the next.
Before long, you’ve got ten crews, four counties, and multiple contractors all copying a process that was never built to last. What started as a one-off compromise becomes standard practice. It gets written into scopes. It gets baked into estimates. It becomes “how we do things.” And nobody stops to ask whether any of it actually works when something goes wrong.
I’ve seen jobs where every handhole in the project was placed two inches too shallow. Not enough to catch the inspector’s eye, but enough to create frost heave issues, restoration problems, and future damage when the lids pop in winter. And guess what happened? They used the same depth spec on the next ten projects because nobody logged the issue. Nobody reported the long-term consequence. The mistake didn’t just repeat. It multiplied.
Or take splicing. One tech uses a shortcut because the schedule is tight and the weather is bad. He skips cleaning the fiber. It still passes. So the next guy picks up the habit. And the next. Now you’ve got thousands of splices with hidden reflection points, all scattered across a network that looks perfect in the report but is already degrading underground. No one sees it. Until later. Until it matters.
That’s how mistakes scale. Quietly. Efficiently. Under the radar. And every layer of the process reinforces it. The engineer never hears what happened in the field. The PM never sees the final build. The contractor is too busy chasing the next project to revisit the last one. And the people writing the checks assume progress equals performance.
What we’ve done is build a machine that replicates errors with increasing efficiency. That’s not just a technical problem. It’s a leadership failure. Because if you’re in charge of the process and you don’t stop to inspect the pattern, you’re not scaling quality. You’re just scaling consequences.
And the worst part is that no one will see the full impact until years later. Not when the job closes. Not when the lights come on. But when the network starts failing in places no one can explain. And someone has to pull up a route, pop a lid, and ask the question nobody wants to answer: “Why is every single one of these built like this?”
This is why feedback loops matter. This is why redlines matter. This is why construction needs to talk to design, and PMs need to be empowered to stop bad patterns, not just move the work forward. Because if we don’t build in correction, the system will just keep doing what it’s already doing, replicating a version of the build that works on paper but breaks in reality.
Mistakes will always happen. That’s part of the work. But when the mistake becomes the model, and nobody speaks up, what you’re building isn’t a network. It’s a countdown.
The Missed Opportunity for Legacy
This was never supposed to be just another job. What we are doing right now, laying fiber across cities, counties, and rural America, is the biggest infrastructure upgrade of our generation. It is the foundation of every smart city, every remote classroom, every digital healthcare system, every connected home. Fiber is not just faster internet. It is the physical backbone of how the future will work. And we are burying it with a level of care that says none of that matters.
If we step back and look at the scale of what is happening, this should be legacy work. The kind of work that crews talk about twenty years from now. The kind of builds that get referenced in training manuals. The kind of installs that people are proud to point at and say, “We did that. And it’s still working.” But that is not where we’re headed. Right now, most of the work being done is transactional. Get it in. Get it passed. Get it paid. Move on. And if we keep working like that, we are going to miss the whole point of what this moment was supposed to be.
Because legacy does not come from size. It does not come from footage or budget or how many states your company operates in. Legacy comes from quality. From integrity. From people making decisions in the dark and choosing to do it right anyway. From leaders who hold the line even when nobody’s looking. From field techs who still take pride in clean slack loops, even when the schedule says they do not have time. That is what lasts.
What we are doing right now could have defined a generation of builders. We could have trained thousands of new workers in a trade that actually meant something. We could have built a culture around craftsmanship, ownership, and clarity. We could have taken this funding and used it not just to close coverage gaps, but to raise the standard for how broadband gets built in this country. That was the opportunity. It still is. But we’re not treating it that way.
Instead, we are burning through money, burning out workers, and burying problems that the next crew will have to dig up. We are acting like this is a sprint. Like the only thing that matters is getting across the finish line first. But if you have been around long enough, you know the finish line is a lie. Because the second that network goes live, the real work begins. Maintenance. Expansion. Troubleshooting. The legacy is not how fast you built it. It is how well it holds up.
I have seen the difference. I have seen the jobs where everything was aligned. Clear design. Solid install. Clean records. Pride in the work. You walk that route two years later, and it still feels tight. Still feels solid. Still feels like the people who built it gave a damn. And I have seen the opposite. Miles of duct that no one can trace. Handholes that do not match the prints. Splice trays that look like a rat’s nest. Those builds do not just fail, they embarrass the people who signed off on them.
So let’s be honest. Right now, we are choosing speed over substance. And in doing that, we are trading legacy for momentum. We are spending the chance to build something that lasts in exchange for a clean report at the next status meeting. That is the kind of decision people regret. Not today. But five years from now, when the work starts coming apart and someone asks, “Who built this?”
You can’t fake legacy. You either build it with intention or leave it behind completely.
What Happens If We Don’t Change
If nothing changes, the failure will not be sudden. It will be slow, silent, and predictable. Fiber networks will start to rot from the inside out. The technology works. The crews are doing their best. The problem is the process, a process never designed to carry the weight of real, long-term infrastructure. And the longer we pretend it will hold, the harder it’s going to break.
We will see more outages. Not isolated incidents. Not freak accidents. Systemic failures. Ducts will collapse because they were buried too shallow and unbedded. Splice trays will corrode because the seals were never checked. Signal loss will creep in from reflection points that were invisible during testing but obvious to anyone who looked closely at how the fibers were handled. And when these things start to surface, the people left to deal with them will not be the ones who created the problems. They will be the ones holding the network now. And they will be furious.
We will burn through talent. Field crews will walk. They are not walking away from hard work, they’re walking away from a system that makes good work feel pointless. Good PMs will stop raising their hands because every time they do, they are ignored, blamed, or told to “make it work.” Engineers will stop caring because their designs are being treated like templates, not tools. And the next generation of workers will inherit a trade stripped of pride, where no one bothers to explain the why behind the work. That is how you lose the future before it even starts.
We will lose trust. Cities will start questioning the providers they once championed. ISPs will scramble to defend networks they cannot explain. Contractors will get blacklisted. Inspections will tighten. Reports will pile up. And the same providers who were once praised for rapid deployment will find themselves buried in lawsuits, complaints, and clawbacks. The words “fiber ready” will lose meaning if the networks behind them keep failing.
We will lose money. Not just in repairs and rework. But in opportunity. Expansion plans will slow. Maintenance budgets will spike. Insurance premiums will rise. Contract terms will change. Funding will come with new restrictions. And the companies who kept cutting corners will suddenly find themselves boxed in by requirements they never had to deal with before. You can run fast for a while. But when the work starts collapsing behind you, the road narrows real quick.
And worst of all, we will normalize dysfunction. We will start to believe this is just how it works. That builds always fall apart. That nobody documents. That crews are replaceable. That shortcuts are necessary. And when that becomes the culture, quality doesn’t disappear because it can’t be done, it disappears because no one is asking for it anymore.
This is the future we are choosing every time we say “just get it done” instead of “get it right.” Every time we close a job with open questions. Every time we pretend that passing light means long-term performance. Every time we reward speed over clarity. This is not theoretical. This is cause and effect. And if we don’t have the courage to admit it now, we’re going to be dealing with it later, at ten times the cost.
Because the system will keep running. The contracts will keep going. The installs will keep happening. But the quality will keep dropping. The pressure will keep rising. And the margin for error will eventually collapse under the weight of everything we refused to fix.
You want to know what happens if we don’t change?
We lose the one thing this industry cannot function without: belief. Belief that the work matters. Belief that it’s worth doing right. Belief that the people in it can still build something that lasts.
What’s Still Possible
The damage is real. But it is not final. The good news is that we are not past the point of no return. Not yet. There is still a window to turn this around. And it does not start with massive funding or sweeping reform. It starts with people telling the truth. On the job site. In the office. In the boardroom. Saying, “This is broken. And we can do better.”
Because here’s the truth no one wants to admit. The fix is not complicated. It is not easy, but it is simple. We do not need better dashboards. We do not need more software. We do not need another round of marketing about how fast we are deploying broadband. What we need is clarity. Real clarity. From the first design meeting to the final walkthrough. From engineering to installation to inspection to turnover. Everyone on the same page. Everyone seeing the same picture.
We need crews that are trained not just to move dirt, but to build with purpose. Crews that understand the why behind slack loops, bend radii, and duct bedding. Crews that know a shortcut today becomes a failure tomorrow. You give those workers clarity and ownership, and they will surprise you every time. They are not the problem. They are the ones holding this industry together.
We need project managers who are not just chasing schedules, but enforcing standards. PMs who can push back on chaos without fear of being blamed. PMs who are given the tools, the authority, and the support to say, “No, we’re not burying this problem. We’re fixing it now.”
We need engineers who do not just draft lines, but build solutions. Engineers who walk the route. Who ask questions. Who understand construction and design are not two departments, they are two halves of the same process. And when those two halves are connected, everything downstream gets better.
We need owners, ISPs, and city officials who stop treating fiber like a tech upgrade and start treating it like infrastructure. You do not get another shot at this. You do not get to tear it up and start over in five years. If you want to build networks that serve your communities, support your growth, and stand the test of time, then you have to care how they’re built today. Not just how they perform tomorrow.
And most of all, we need to stop acting like good work is a luxury. It is not. It is the minimum requirement for a system that’s supposed to last decades. We cannot keep pretending that quality is optional. That craftsmanship is extra. That field feedback is noise. Those beliefs are killing the very thing we are trying to build.
The opportunity is still here. We still have projects underway. We still have money being spent. We still have people on the ground who care. But that will not last forever. Every time we let a bad build slide, we lose a little more trust. A little more pride. A little more belief that this can be different.
So what is still possible?
Alignment. Real alignment. Between teams, between roles, between what is drawn and what is built.
Pride. Not the empty kind. The kind that comes from doing the work right even when nobody is watching.
Clarity. The kind that shows up in the documentation, in the field conditions, in the way the build holds together years after the ribbon cutting.
And legacy. Not the kind you print on marketing banners. The kind you bury under a handhole cover that still looks clean ten years later.
That is what is still possible. But only if we stop running and start building with intention.
