How We Got Here

Coax and copper were thick-skinned. You could bend them. Bury them shallow. Splice them dirty. And nine times out of ten, they still worked. That’s because they moved electricity. And electricity is forgiving. It jumps gaps. It powers through resistance. It survives a little damage.

Fiber doesn’t work that way.

Fiber is light. It has to be contained, directed, and controlled. That means it requires precision. If you kink it, you lose signal. If you get dirt in the splice, you create reflection. If you skip the slack, you lose flexibility. This isn’t about being picky. It’s physics. It only travels clean if the path is clean.

The problem is that we swapped the cable but kept the culture.

We used to build networks that could take a beating. Now we’re building with something that demands respect. Yet we’re still treating it like it’s just another job. On the surface, the process looks the same. We trench, lay, splice, and bury. But underneath, the margin for error has disappeared. And most people never got that memo.

So yes, it might pass light today. It might even go live. But if it wasn’t built with precision, it won’t last. It won’t hold up over seasons. It won’t survive rough weather. And it won’t function properly when someone has to extend or troubleshoot that network down the road.

That’s the difference no one explained.

Copper tolerated shortcuts.
Fiber exposes them.

If we don’t adjust the way we think, not just the way we build, we will keep creating networks that look finished on the surface but are already falling apart underneath.

The Money Moved Faster Than the Knowledge

We funded the finish line before we trained anyone to run the race.

The moment the funding was approved, the clock started ticking. Providers had to show progress. Cities had to prove they were putting money to work. Contractors had to move quickly to win bids and stay busy. Everyone involved, engineers, managers, city officials, broadband offices, was suddenly working inside a system driven by urgency. But while the money moved fast, the knowledge did not. We threw fuel on the fire without ever asking if the foundation was ready.

The industry didn’t pause to build understanding before building networks. There were no widespread training programs rolled out. No mandated standards for construction quality. No deep education on how fiber differs from copper. There was just a surge of cash, a wave of projects, and an unspoken expectation that people would figure it out as they went. Many of them did. They improvised. They asked around. They learned on the fly. But figuring it out under pressure is not the same thing as doing it right with intention.

What we created was a situation where the work got done before the people doing the work were equipped to understand what the job actually demanded. Fiber construction became a checklist, not a craft. The focus was on closing out footage, hitting targets, and turning in reports. That was the system. The funding asked for completions instead of conversations. It measured progress in miles rather than in precision. It rewarded speed instead of clarity. So that’s what we got. Fast builds. Incomplete understanding. Rework that’s quietly buried until it becomes someone else’s problem.

This isn’t a critique of the workforce. This is a failure of the rollout. If you’re going to modernize infrastructure, you have to modernize the way people think about building it. That never happened. We treated this as an expansion when it should have been a transformation. Fiber isn’t just faster internet. It’s a more sensitive, less tolerant, more exact kind of infrastructure. And we dropped it into an environment still wired for coax.

So now we’ve got thousands of miles of fiber in the ground, built by people who were never told what a proper bend radius is, why slack is critical, or how light reacts to dirt inside a splice. The system assumed that information would trickle down. It didn’t. And what’s worse, the deadlines never stopped long enough for anyone to catch up. The builds kept moving, even as the knowledge gap widened.

That’s how we got here.

We poured billions into construction before we poured anything into understanding. We built the racecourse before we trained the runners. And now we’re acting surprised that some of the networks are falling apart before the first billing cycle is up.

The System Taught Us to Prioritize Completion, Not Clarity?

We didn't just build the wrong networks. We built the wrong incentives.

Every system teaches people what to care about. It doesn't matter what the mission statement says. What matters is what gets rewarded, what gets noticed, and what gets pushed. In fiber construction, the message was clear from the start: get it done. Not get it done right, just get it done.

Completion became the north star. Schedules ruled everything. The project plans didn’t track whether the build matched the ground conditions, or whether the test data was clean, or whether the redlines were updated. They tracked footage, milestones, and percent complete. That’s what the spreadsheets were built for. That’s what got discussed on the status calls. And over time, that’s what everyone started optimizing for.

So naturally, the behavior followed the incentives. Crews started skipping steps because they were practical. When you’re told to finish 3,000 feet a day, and no one is asking for labeled slack loops or clean bore logs, you learn what matters. You learn that clarity is optional, and completion is everything. Project managers started planning for velocity instead of accuracy. Engineers stopped fighting for constructability reviews because they slowed things down. Contractors stopped pushing back on unrealistic schedules because that’s how you lose work.

It wasn’t sabotage. It was survival. Everyone just adapted to the environment they were in. They followed the rules of the game as it was set up. And that game was built to move projects forward, not to make sure they were being built with integrity. The problem is that fiber doesn’t bend to that kind of pressure. You can’t outpace its requirements. You can only ignore them temporarily.

The system trained people to chase the ribbon cutting, not the reality under the lid. And now, years later, we’re finding handholes with no documentation, splice trays with no logic, and networks that light up fine one week and fail the next. When we trace the problem back, it almost always starts with someone who was told to get it done quickly, without the information, time, or authority to do it right.

That is what happens when clarity becomes a luxury instead of a requirement. You end up with networks that only look finished on paper. The spreadsheet says complete. The dashboard is green. But in the ground, it’s chaos. It is just organized enough to pass inspection, and just broken enough to collapse under pressure.

And here’s the real danger. The more often we build like this, the more it becomes the norm. The next generation doesn’t inherit craftsmanship. They inherit shortcuts. And those shortcuts don’t show up in reports. They show up in outages, in failed audits, and in networks that need major rework before they ever reach their full capacity.

We got here because the system didn’t just allow it. It encouraged it. And unless we change what gets measured, what gets discussed, and what gets rewarded, we are going to keep getting the same results.

Hand-offs Became Blind Spots

Everyone owns their part. No one owns the whole. That’s the problem.

On paper, the fiber build process looks clean. Engineering designs the network. Project managers schedule the work. Contractors build it. Cities inspect it. Each step is handled by a different group, each with its own tools, timelines, and responsibilities. But when you zoom out, a pattern starts to emerge. Every time the work changes hands, clarity drops off. The baton gets passed, but no one checks if the next runner knows which direction to go.

This is where the real breakdown happens. Not in the individual roles, but in the spaces between them.

The engineer draws a route that looks good on a screen but doesn’t match the field. The PM receives the design and schedules crews without knowing if it is actually buildable. The contractor shows up to a site that doesn’t match the plan and makes changes in real time. The redlines get marked up but never make it back into the design. The inspection gets done using a checklist that doesn’t reflect what was actually built. And just like that, the as-built record becomes a best guess.

At no point did anyone drop the ball entirely. But at every hand-off, something got lost.

This is not a case of bad actors. It is a case of disconnection. The engineer never finds out what changes were made in the field. The crew never gets to ask questions about the design before construction starts. The PM is left chasing updates, trying to manage risk they did not create. The city inspector signs off on what they can see, not what they can verify. Everyone is doing their job, but the jobs are not aligned. And when that happens, the build starts to fracture beneath the surface.

The longer this goes on, the more it becomes embedded. We start accepting incomplete records as normal. We stop expecting field changes to be updated. We treat post-construction documentation as optional cleanup instead of a critical part of the process. And the people who actually try to fix it, the ones asking for context, clarity, or better coordination, get labeled as slowing things down.

So we keep moving. Each group focuses on its own piece. Each team checks its own box. And the network gets built, just not the way anyone originally intended.

That is how you end up with designs that do not reflect the real world, construction that does not reflect the design, documentation that does not reflect the build, and a system where no one can answer a simple question: what exactly did we just install?

We got here because the process was never set up to flow information through the entire lifecycle. It was built for hand-offs, not feedback loops. For transactions, not collaboration. For speed, not visibility. And as long as that is the case, every build will be a patchwork of assumptions, adjustments, and unanswered questions.

The Cost of Speaking Up Got Too High

In a healthy system, feedback makes things better.

In a healthy system, feedback makes things better. People raise concerns, and those concerns lead to fixes. That is how you improve. But in fiber construction, the system was not built to process feedback. It was built to hit deadlines. So when someone raises their hand to say, “This isn’t right,” the most common response is not support. It is resistance.

That is how the silence started.

Crews in the field stopped pointing out bad prints because they knew it would stall the job. Project managers stopped pushing back on impossible schedules because they knew it would not change anything. Contractors stopped asking for clarity because they were tired of being seen as difficult. Even engineers stopped requesting more site data because they knew there was not time for it. Everyone saw the gaps. Everyone felt the friction. But over time, they also learned the same lesson: speaking up does not fix the system. It just puts a target on your back.

So they stopped.

They kept their heads down. They solved what they could. They let things slide. Not because they did not care, but because they had already seen what happens when you try to fight the momentum. You get overruled. You get blamed. Or worse, you get ignored completely. And eventually, you start to believe that silence is just part of the job.

That is how a culture of compliance takes root. Not because people are passive, but because they have been taught that action has no impact. The people who care the most, the ones who want to build it right, are the ones who get worn down first. They burn out. They pull back. They learn to settle for “good enough” because no one is listening when they ask for better.

And here is the real damage. When the people who know what good looks like stop speaking up, the next generation never learns. The standards slip, but no one notices. The shortcuts multiply, but no one challenges them. The mistakes get normalized. What started as one bad decision turns into the baseline for every project that follows.

We did not get here because people stopped caring.
We got here because the system stopped listening.
And when that happens, the best people either go quiet or walk away.

“It Passed” Became the New “It’s Right”

We stopped verifying quality. We just checked boxes and moved on.

Somewhere along the way, we replaced the question “Was it built right?” with “Did it pass?” Once that shift happened, everything downstream changed. The test results became the finish line. The checklist became the standard. The goal became clearance, not confidence.

Fiber networks are being treated like temporary setups, not permanent infrastructure. Crews are told to get it in the ground, clean it up enough to pass inspection, and move on. Project managers are judged by what is closed out, not what is corrected. Inspectors are given limited tools and limited time to verify work that was rushed from the start. Leadership celebrates timelines, not long-term performance. On the surface, it looks like progress. But underneath, it is a gamble. One that keeps getting passed to the next person in line.

The danger is that fiber is deceptive. You can build it wrong and still get a clean light reading. You can skip the slack, mislabel the fiber, splice it dirty, or bend it too tight, and it might still pass signal today. But the issue does not show up now. It shows up when the weather shifts, or when another team tries to extend the route, or when a critical reroute is needed and no one can trace what was actually built.

Passing light is not the same as being ready for the future. One tells you the network is functioning. The other tells you the network is stable. But in most builds, no one is asking about stability. No one is asking whether the route was documented properly, whether the splice trays were clean and labeled, or whether the duct was backfilled with care. They are asking if it is done. If it is closed out. If they can report it as complete and move on to the next one.

And that mindset has consequences.

It creates builds that are only as good as their last test result. It leaves behind networks that no one truly understands, because the people building them were never asked to explain what they did. It creates a future where basic maintenance turns into full-scale excavation, because the last crew skipped the documentation to hit their footage goal. And when it fails, because it will, the cost will not just be dollars. It will be time, credibility, and trust.

The worst part is that everyone in the system knows this is happening. But because it works today, they do not stop to ask if it will work tomorrow. They rely on inspections that are not equipped to verify what matters. They trust test results that only show what light is doing right now, not how fragile the path actually is. And they push everything forward under the assumption that “passing” means “good enough.”

But good enough for today is a liability for tomorrow.

We got here because we trained an entire industry to celebrate speed and overlook the details. We designed systems that move builds forward whether they are right or not. And we created a culture where a signed inspection sheet is more valuable than an accurate as-built.

So now we are sitting on top of miles of fiber that technically passed but was never built to last. That is not quality. That is a countdown.

Everyone Was Working. But No One Was Aligned.

Hard work means nothing when no one is moving in the same direction.

If you walked onto any fiber project right now, you would see people working. Crews are trenching, boring, and placing duct. Project managers are taking calls, updating schedules, and solving conflicts. Engineers are drawing routes and updating sheets. Inspectors are reviewing sites. Vendors are moving materials. On the surface, the machine is moving. People are busy. The problem is, they are all working inside different realities. Everyone is pushing hard, but no one is pulling in the same direction.

That is the part most people do not see. The disconnect is not in the effort. It is in the focus. Each team is doing what they have been told to do, but the goals are not aligned. The engineer is optimizing for design accuracy. The contractor is optimizing for speed. The PM is optimizing for delivery. The city is optimizing for compliance. And the ISP is optimizing for coverage reports and ribbon cuttings. None of those are bad goals. But they were never tied together. So when things fall apart, no one knows where to trace the failure back to. It did not start with a person. It started with a system that never demanded alignment in the first place.

That is how you end up with crews building what they were told, not what was actually designed. That is how you get design redlines that never make it back into the record. That is how you get change orders no one saw coming, because the real-world build conditions were never communicated upstream. Everyone did their part, but no one owned the whole. Without ownership across the process, you cannot have alignment. You can only have activity.

And activity alone is a terrible measure of progress.

Just because the build is moving does not mean it is moving well. Just because the milestones are green does not mean the network will hold up. We have confused motion for momentum. We have mistaken busy teams for effective systems. What we are actually watching is a machine that only works as long as nobody asks the hard questions. The second someone does, like “Where is the documentation for this splice?” or “Why doesn’t this route match the as-built?”, the whole thing starts to unravel. Underneath all the dashboards, reporting tools, and status meetings is a fragile process held together by guesswork, assumptions, and duct tape.

Alignment is not about agreeing on everything. It is about building from the same picture. Right now, that picture is different depending on who you ask. The engineer sees one version. The crew sees another. The PM sees something else entirely. The city sees what is on the permit. And the ISP sees what gets reported back in a slide deck. That is not alignment. That is a relay race where no one met before the handoff.

We got here because no one was responsible for stitching the parts together. Each role was created in isolation. Each team was built to hit its own targets. We assumed that if everyone just did their job, the outcome would be solid. That only works if the jobs are connected. In this industry, they are not. They are siloed, segmented, and stacked on top of each other without any shared accountability.

And when something finally breaks, we do not solve the root issue. We assign blame. We point fingers. We document the problem, close the file, and move on. But the real issue was never the mistake. It was the structure that made that mistake inevitable.

The Real Cost Was Never in the Footage.

We measured everything except what mattered most.

Fiber construction is full of metrics. We measure linear feet installed. We track labor hours and production rates. We color-code progress against milestones and assign percentage values to completion. On paper, it always looks like we know exactly where a project stands. But none of those numbers, no chart, no timeline, and no report tells us the one thing that actually matters: was it built in a way that will last?

That is the disconnect. The real cost of poor builds is not captured in how much we installed. It is hidden in what was lost during the process. And it starts with something almost no one is measuring: the erosion of pride.

When the system rewards speed and overlooks clarity, people begin to cut corners. Not because they are careless, but because they are exhausted. They are tired of working in systems that do not give them the time, tools, or trust to do it right. They are tired of raising red flags only to be ignored. They are tired of being held responsible for problems they did not create. And eventually, they stop trying to build with pride and start trying to survive the day.

Pride is what makes a crew loop slack even when no one is checking. It is what drives a fiber tech to label trays properly, clean the handhole, and double-check test results. Not because someone is watching, but because they know the work matters. But pride does not survive in environments that punish attention to detail. It withers when every task feels rushed, when every decision must bend to a deadline, and when every correction is treated like a delay instead of a safeguard. Over time, the culture shifts. People stop going the extra mile. Then they stop going the extra inch. Eventually, they are just doing enough to not fall behind.

Once pride erodes, the next thing to go is trust. Trust between the field and the office. Between the engineer and the PM. Between the contractor and the client. It disappears slowly, every time a redline gets ignored, every time a change in the field does not make it back into the record, and every time a shortcut gets buried because it passed light. As trust breaks down, so does communication. Crews stop reporting issues. PMs stop escalating concerns. Engineers stop asking for feedback. Everyone goes quiet. Not because the problems went away, but because no one believes anything will change.

The final cost is the one we leave behind. Quietly. Invisibly. Until it surfaces years later. It is the duct that was not bedded properly. It is the splice tray that was labeled wrong. It is the route that was never updated after the bore path changed. These things do not show up on the project closeout. They show up during outages, repairs, and expansions. That is when someone lifts a lid and realizes they have inherited a network built in a rush, with no trail of how it got there.

Fiber is permanent. Once it is in the ground, it stays there. Every decision we make during a build, every shortcut, every compromise, and every missed detail gets sealed in and passed forward to the next crew, the next contractor, and the next city. If we do not build with clarity, we are not just creating confusion. We are burying future problems on a time delay.

That is the fallout. It is not loud. It is not immediate. It does not make headlines. It just lingers quietly. It drains pride from the people doing the work. It slowly breaks down the trust between teams. And it sets traps that will not spring until long after the job is called complete. It is the reason seasoned PMs burn out. It is the reason good crews walk away from the trade. It is the reason so many builds feel like a battle from start to finish. And it is the reason maintenance and emergency response costs quietly double, year after year.

We did not end up here because of one decision. We arrived here through a thousand small choices, each one made under pressure, each one dismissed as a temporary solution. But together, they became the culture. A culture where quality is optional, clarity is rare, and the standard drops a little lower every time speed wins over craftsmanship.

The real cost is not in the footage we install. It is in the systems we create, the trust we break, the pride we lose, and the problems we bury. It is not written in the invoice. It is written in the ground.

And it is waiting.

Geoff

Fiber Done Right