Why This Matters

I didn’t choose this industry; I was born into it. My father, David Rottmayer, has been in the game for more than 45 years. He’s seen nearly every part of this world: copper, coax, fiber, OSP, ISP, engineering, construction, maintenance. I was raised watching him do the work and make sure everyone around him did it right, too. He wasn’t quiet about it; he believed in doing things the right way and made sure you knew where the line was. There was a standard, and you didn’t cut corners. You didn’t build something you wouldn’t put your own name on. That’s the man who taught me everything I know, and that mindset shaped how I’ve shown up in this industry for over two decades.

While my dad’s experience spans the full arc of telecom, mine has centered around one thing: the design and build side of fiber. And I’ve seen enough, both good and bad, to say this plainly: the way most networks are being built today is not sustainable. That’s not a blanket condemnation. There are good contractors doing solid work. But if we’re being honest and that’s the whole point of this newsletter. The majority of projects being designed and built right now are fragile, short-sighted, and unprepared for the long haul.

We all understand the end product. Everyone gets the promise of fiber: faster speeds, cleaner installs, connected homes, satisfied customers. That part makes sense. But what it actually takes to bring that to life, the engineering, the design, the trenching, the duct placement, the splice logic, the documentation, the quality control, that part is broken. There’s a massive gap between what’s being handed off and what’s actually happening in the field. And if you’ve spent any real time out there, boots on the ground, you’ve seen it, too.

I’ve stayed quiet about it for a long time. It’s easier to keep your head down. Easier to hit deadlines, invoice the work, and move on. But I’ve hit a point where staying quiet feels like complicity. Too much money is being spent. Too many people are involved. Too many bad habits are being buried, literally, and the consequences are starting to show.

That’s why I’m writing this newsletter.

It’s not to rant. It’s not to call anyone out. It’s to call attention to the disconnect between what fiber could be and what we’re actually building. We are laying down the infrastructure that communities will rely on for the next 30, 40, even 50 years. And we’re doing it with systems, standards, and decision-making that weren’t built for the kind of precision fiber demands. The result? We’ve got solid people doing rushed work with incomplete information, and it’s setting everyone up to fail.

This newsletter is called Fiber Done Right because that’s the only thing I’m interested in: what good work looks like, how to do it well, and how to fix what’s broken without burning the whole thing down. I’m writing this for the crews, the project managers, the designers, the contractors, and the city officials who know there’s a better way and want to be part of building it.

The Truth We’re All Feeling

Spend enough years in this industry and patterns start to show themselves. At first, you think it’s just the job, some friction here, some rework there. But over time, you start to notice it’s not isolated. It’s baked in. It’s systemic. And while a lot of people might not be saying it out loud, most of us know the truth: something’s not lining up.

We’re moving fast. Faster than ever. There’s more money in play, more demand, more pressure to get the job done and get it done yesterday. But in that rush, the fundamentals are slipping. Plans are made with assumptions instead of information. Crews are asked to execute things they were never shown. Designs are treated like gospel, right up until they hit rock, or a tree root, or a utility line that was never marked. The response is always the same: “Just make it work.”

And we do. That’s the part no one talks about. We’ve all been making it work for years. Adjusting in the field. Calling audibles. Solving problems we didn’t create. Most of the time, no one even knows how many decisions were made on the fly just to keep the job moving. Because we’re proud of what we do. Because we care about the work. Because we know how to figure things out.

But here’s the problem: when the whole system starts depending on crews to “just figure it out,” we’ve already lost control of the build. At that point, it’s no longer a network, it’s a patchwork. And we all know it.

That’s the tension no one wants to name. It's not just chaos, it's disconnection. The office and the field are rarely on the same page. Engineering sees one thing, the real-world conditions show another. Project managers are juggling schedules, materials, permitting, inspections, reporting, while also trying to keep their crews from burning out. Leadership wants performance metrics, cities want ribbon cuttings, and customers want Wi-Fi. And somewhere in the middle of all of it, the actual build is getting squeezed.

The quality isn’t bad because people don’t care. That’s not it. The quality suffers because the system isn't built to support good work. It’s built to move fast. And when fast becomes the priority, everything else becomes optional: slack loops, splice documentation, test reports, photos, even proper backfill.

That’s what we’re dealing with.

And if we’re honest, most of us have felt it for a while now. The voice in your head that says, “We should slow down and get this right,” usually gets drowned out by the voice that says, “We’ve got to hit the number.” You’re not alone in that. We’ve all been there. Most of us still are.

But here’s the thing: if no one stops to call it what it is, it never changes. The disconnection becomes the culture. The exceptions become the norm. And eventually, the standard for what “good fiber construction” looks like gets watered down to the point that we’re just hoping the signal makes it to the ONT.

This isn’t about pointing fingers. It’s about giving voice to what people in the trenches already know. It’s about naming the real problems so we can start building real solutions. Because you can’t fix what you’re not willing to see. And most of what’s wrong with this industry right now isn’t hidden, it’s just uncomfortable to talk about.

But we’re going to talk about it here. Not with noise or blame, but with honesty. Because if we don’t name what’s broken, we’ll never fix it. This isn’t about tearing anything down. It’s about building something better, something that lasts. And it starts with clarity, with conversation, with calling things what they are so we can begin shaping what they could be.

Crews Are Doing the Best They Can… Blindfolded

If you’ve spent any real time around a crew that takes pride in its work, you know this much is true: most of the guys in the field genuinely want to do it right. No one shows up hoping to cut corners or throw down sloppy work. They arrive early, get the equipment staged, handle the prep, work through the unknowns, and grind out the day. These aren’t people looking for the easy way out. They’re looking to do the job and do it well. The problem is, the system they’re working inside doesn’t always let them.

Crews today are too often being asked to build from incomplete information. They’re handed designs they didn’t see, working off prints that assume perfect terrain and ideal conditions. The duct layout might run straight through dense roots. The trench path might go through land that’s now a poured patio. The bore shot assumes soft soil, but the crew hits rock or worse, a utility line that was never marked. The expectations are built on assumptions, not ground truth. And the timeline doesn’t shift just because the real world doesn’t match the plan.

And yet, they still get it done. Because that’s what good crews do. They adapt. They solve problems. They figure it out. But let’s stop pretending that’s how it’s supposed to work. Solving problems in the field should be the exception, not the entire job description. And when we normalize improvisation, we end up treating crews like laborers instead of trade professionals. They're given a vague scope, a few notes, and told to “make it work.” And when they do call for help, when they try to clarify something, they’re either met with silence or pressure to just get it in the ground.

So they do. And that duct that wasn’t supposed to turn past a 30-degree bend gets kinked around a corner. The slack that was supposed to be looped gets forgotten. The handhole ends up too shallow or dropped into the wrong quadrant. It looks fine at a glance. It might even pass inspection. But when something fails, or someone finally lifts the lid, those shortcuts show up. And guess who gets blamed? The guy in the field. The one who was never told why it mattered. The one who made a decision in real time to keep the job moving. The one who was expected to deliver quality without ever being given the tools or context to understand what “quality” actually looks like.

Now to be fair, not every crew is out there raising the bar. Some don’t know what right looks like because no one ever showed them. That’s not always on them. That’s on the system that trained laborers, not craftsmen. That’s on leadership that prioritized footage over fundamentals. That’s on a culture that has taught people to value speed more than sustainability. But when you give a crew the full picture, when you equip them with context, clarity, and a reason to take ownership, you’d be surprised how often they rise to the occasion. Most of them want to take pride in their work. They just need someone to tell them what the work is really for.

Crews aren’t failing these builds. They’re adapting to builds that were broken before they ever showed up. They’re making decisions in the dark and doing their best with what little visibility they’re given. That’s what I mean by blindfolded, not careless, but stuck in a system where they’re constantly reacting instead of building from a place of clarity.

These guys are working hard. They’re solving problems that started well before they got on-site. They’re carrying the weight of misalignment from upstream decisions, and still getting the job done. But let’s not confuse motion for quality. If leadership, engineering, and project management aren’t willing to own that disconnection, then they’re not really serious about building anything that lasts.

If we want this industry to move forward, we have to start by telling the truth: most crews are doing the best they can with the least amount of clarity. That’s not a field problem. That’s a leadership problem. And it’s one we can fix, if we’re willing to stop burying the disconnect and start building from the same page.

Project Managers Are the Human Buffer Zone

If you’ve ever been a project manager in this industry, especially on the build side, you already know the job title is misleading. You don’t manage projects. You manage pressure. You manage people who need answers and timelines that don’t flex. You’re the human buffer between the office and the field, translating two completely different languages, often in real time, with incomplete information and full accountability. One minute you’re on the phone with a crew about a conflict they didn’t cause. The next, you’re fielding a call from an inspector who says something doesn’t match the plan. Meanwhile, leadership wants to know why progress has slowed, the client wants a clean report, and no one but you sees just how fragile the whole thing really is.

Here’s the part they don’t tell you when you get handed the PM title: you’re going to be the one holding the bag when things don’t line up. If the engineer missed a crossing depth, it’s your issue. If the permit takes longer than expected, it’s your delay to explain. If the crew has to reroute around something that wasn’t on the drawing, it’s your job to clean it up,  in writing, in meetings, in updates. And the hardest part? Most PMs weren’t trained for this. They didn’t come up through the field. They didn’t go to school for fiber design. They’re smart, adaptable, and thrown straight into a blender. So they figure it out. They patch it together. They learn the hard way, because someone has to keep the wheels turning.

And while some PMs hide behind the spreadsheet, the ones who’ve been around long enough carry the weight. They’re the first to see when a job is about to go sideways. They’re the first to spot the cracks in the plan. But they’re also the last to get the credit when it somehow holds together. The burnout doesn’t come from the chaos; it comes from the constant reaction. From knowing a lot of what they’re dealing with could have been prevented if the system were built to support the people doing the work.

Eventually, something gives. Some PMs shut down. Others burn out. Some stay quiet, do their best, and hold everything together with duct tape and calendar invites, fully aware that the build is being held up by guesswork and grit, not structure. And yet, every successful fiber job still hinges on that person. The one absorbing all the fallout from decisions they didn’t make, trying to keep the train on the tracks without the time, tools, or authority to fix the tracks themselves.

We’ve got to stop treating PMs like they’re just pushing paper. They’re holding the build together. Every disconnect, every oversight, every delay flows through them. And if we don’t start supporting them better, we’re not going to fix the build process. We’re just going to keep burning out the only people still trying to make it work.

ISPs and Cities Want Fiber, Not Problems

The people writing the checks aren’t asking for chaos. They’re asking for progress. Internet service providers, city governments, broadband offices, they all want to see maps with coverage areas filled in, headlines that say, “High-Speed Internet Has Arrived,” and ribbon-cutting ceremonies that show the public their tax dollars were put to work. And to be fair, they should. That’s the whole point of these infrastructure efforts: we need more access, better speeds, and stronger networks. But while the intention is right, the execution often goes sideways. Not because people don’t care, but because many of the people making the decisions have no real idea what a quality fiber build looks like.

That’s not a shot. It’s just the truth. Most of the people in these roles have never been down in a trench. They’ve never looked inside a splice tray or walked a route with a marked-up print in one hand and a can of paint in the other. They don’t know what crushed duct does to signal loss or how often a bore path runs into field conditions that don’t match the map. What they see is what’s presented to them: milestone charts, red-yellow-green dashboards, Gantt timelines, and progress bars. They see what gets reported, not what gets buried.

And when you can’t inspect what matters, you end up approving things you shouldn’t. You end up assuming the contractor is “handling it,” when in reality the contractor might be getting pressured to move faster than the job allows. In a perfect world, quality would be baked in. But in the world we’re in, the system rewards speed, not precision. And when speed becomes the priority, the definition of “done” gets blurry fast.

This is how it usually plays out. Funding gets released, and the clock starts ticking. Timelines are aggressive. Contracts get awarded based on price and promises. And once things get rolling, everyone becomes more focused on keeping momentum than questioning whether the build is happening the way it should. The city doesn’t want to announce delays. The ISP doesn’t want to push back the launch. The contractor doesn’t want to get caught in a cycle of change orders. So everyone quietly agrees to keep moving forward. The project gets pushed across the finish line not because it was done right, but because it had to be done.

And that’s where the problems start. Fiber isn’t like copper. You can’t splice it dirty and get away with it for long. You can’t bend it the wrong way or ignore slack and assume it will keep working. A poor fiber build might pass light today, but it won’t hold up. And when it fails, it usually takes years to discover what went wrong. Because the build didn’t match the design. Because the test results weren’t stored. Because the people signing off didn’t know what questions to ask when it mattered most.

To be clear, there are good ISPs, broadband offices, and municipalities out there who are doing it right. They’re asking hard questions, inspecting work thoroughly, and pushing for quality. But right now, they’re the minority. And as long as we keep pretending that good intentions are enough to guarantee good results, we’re going to keep burying bad builds that nobody sees until it’s too late.

So what needs to change? It starts with understanding that fiber construction isn’t just a milestone to check off on a project plan. It’s a craft. And if you don’t know what right looks like, you can’t inspect it. You can’t enforce it. You can’t improve it. The field doesn’t need more pressure from above. It needs more alignment. More education. More conversations between decision-makers and the people doing the actual work. Because until that happens, we’re going to keep building networks that look great on paper but are already failing underground.

And the worst part? Most of those problems won’t show up until after the money is spent, the contractor is long gone, and the customers are calling to ask why their new fiber connection keeps cutting out.

And Engineers?

Let’s talk about the design side, because this is where a lot of the confusion starts, even if no one means for it to.

I’ve worked with engineers who genuinely care about doing it right. They’re sharp, methodical, and intentional. They build out plans, route fiber paths, spec materials, and generate documentation that’s supposed to set the rest of the job up for success. And to their credit, they’re often working with limited information, tight schedules, and vague constraints.

But here's the issue: too many designs are built in isolation from the real world.

They’re drawn from behind a screen, using aerial imagery and GIS data that’s two years old. They reference parcel lines and ROWs that might make sense on paper but haven’t been walked in decades. And while the engineer is drawing a perfectly straight line through an open field, the guy in the field is staring at a new fence, a drainage ditch, or a rock shelf that wasn’t on any map.

When we talk about disconnection in this industry, this is one of the biggest culprits: designs that look flawless in CAD, but fall apart the second they meet reality.

And it’s not the engineer’s fault entirely. Most of them were never trained to build in the field. They’ve never had to hand-dig a bore pit in frozen clay. They’ve never had to explain to a homeowner why a handhole just appeared in their flowerbed. They don’t know what it’s like to get to a site at 7:00 a.m. and find that the route they designed is physically impossible to build without either breaking a rule, rerouting on the fly, or delaying the job.

That disconnect creates friction. The field ends up improvising. The changes don’t make it back into the design package. The records fall out of sync. The documentation gets fuzzy. And then later, when there’s a failure or a repair needed, everyone’s pointing fingers, wondering how it got built so far off-plan.

But here’s what needs to be said: the plan didn’t go off-track. It was never fully connected to the build in the first place.

Now again, not all engineering teams work this way. The best ones collaborate with construction. They walk routes. They account for environmental realities, permitting lead times, constructability concerns, equipment limitations, and restoration requirements. When you see one of those builds go in, it feels different. The field doesn’t have to guess. The work flows. The documentation matches what actually happened. That’s how it should be.

But unfortunately, that’s not the norm. More often, the engineer draws the map, sends it downstream, and hopes it gets built more or less as planned.

And to be fair, a lot of them never find out when it doesn’t, because no one ever tells them. The foreman doesn’t have time to call. The PM is putting out fires. The contractor submits redlines that never get updated. And by the time someone needs to trace that route or troubleshoot a fault, the only person who really understands what happened is long gone.

If we want to fix this, it’s going to take more than just better drawings.
It’s going to take actual communication.

We need engineers who understand what it means to build, and builders who feel empowered to give feedback upstream without it being seen as criticism. Because when design and construction are aligned, the job moves smoother, the product is stronger, and the entire team comes out looking better.

But when they’re disconnected?

It doesn’t matter how sharp the drawing is, if the crew can’t build it, it’s already wrong.

So What Do We Have?

Step back from any single project, and you’ll start to see a pattern. Not a one-off. Not a bad contractor. Not a rogue PM. A pattern. We have an industry made up of good people, skilled trades, sharp engineers, well-meaning cities, and capable managers, but they’re all operating inside a system that was never truly designed to support clarity.

The engineer draws a clean plan. The contractor bids based on it. The PM schedules crews and materials based on what’s expected, not what’s encountered. The city inspects the job based on paperwork, not what actually happened on-site. The crew, more often than not, is handed a partial picture and told to figure it out. And despite every single person doing their job to the best of their ability, the build gets pushed across the finish line without anyone ever asking the most important question: did we actually build what we said we were going to build?

In most cases, the honest answer is no. And it’s not because people don’t care. It’s because the whole process is fragmented. One group doesn’t really know what the other is doing. Each team is focused on its own checklist, its own deadlines, its own metrics. And because there’s no alignment from the beginning, everyone ends up adjusting downstream to make it work.

What we’ve built is a system where success means the job is closed, not that the job was done right. Where the map doesn’t match the ground, but the invoice still goes out. Where redlines get lost, field changes never make it back to engineering, and the as-built record becomes a best guess. Where the schedule, not the condition of the build, determines when it’s “done.”

And the cost of this isn’t just in rework. It’s in the erosion of trust between teams. The field doesn’t trust the plan. The PM doesn’t trust the information coming from either direction. The client doesn’t trust the contractor. And eventually, the end user, the person whose life and work rely on that fiber connection, doesn’t trust the service.

This is what we’ve created: a fast-moving, disconnected build process that too often leaves behind questions no one is in a position to answer.

It’s not chaos. It’s not a lack of effort. It’s a lack of alignment.

And that’s the part we need to start talking about, because it’s not going away. If anything, the pressure is only increasing. More funding. Bigger projects. Tighter timelines. Less tolerance for delay. Which means if we don’t stop and fix this now, we’re going to keep scaling the same broken habits over more miles, more counties, more communities.

Fiber is different. It’s not like what came before. It doesn’t bend the same way. It doesn’t forgive the same way. And it doesn’t fix itself later. Either we build it with precision, or we build something that’s going to fail, and we won’t know until it already has.

So what do we have? We’ve got a chance. A window. A moment in time where we can choose to do this right, or we can keep going and deal with the fallout later. It’s already starting to show. The question is: are we willing to admit it before it’s too late?

What This Disconnection Is Really Costing Us

You can measure the cost of fiber construction in dollars, feet, hours, and milestones, but that’s not where the real damage is happening. The real cost of a disconnected process doesn’t show up on a spreadsheet. It shows up in broken trust, wasted effort, and jobs no one is proud to sign their name to.

We’re not just talking about mistakes. Everyone makes mistakes. We’re talking about systems that make it harder to do the right thing than to just get it done. That’s the cost. When the machine cares more about progress reports than build quality, you create a culture where people stop raising concerns, not because they don’t care, but because they know it won’t change anything.

Over time, that wears on people. Crews start cutting corners, not out of laziness, but because they’ve been trained to believe it doesn’t matter. PMs stop asking questions because they’re tired of chasing answers that don’t exist. Engineers stop requesting field feedback because no one sends it. And leadership stops walking the job because they assume the paperwork matches reality.

You lose trust. Not just between teams, but within them. A foreman stops trusting the plan. A contractor stops trusting the schedule. A city stops trusting the contractor. And in the background, the customer, who doesn’t know anything about splice trays, backfill, or duct integrity, just knows that their service doesn’t work the way it should.

And then there’s the pride. That’s a hard thing to quantify, but anyone who’s worked in the trades long enough knows how important it is. Pride is what makes someone walk back across a site to clean up a detail no one else will notice. It’s what drives a crew to organize their slack just because they know someone will open that handhole one day. It’s what separates “done” from “done right.”

When pride starts to slip, everything else eventually follows. Quality becomes inconsistent. Documentation gets sloppy. Teams stop communicating. The job still gets “completed,” but it doesn’t feel like a win. It feels like survival. That’s the kind of work that burns people out. That’s the kind of culture that pushes good people out of the industry entirely.

And let’s not ignore the long-term impact. What we’re building now is going to live in the ground for decades. If we bury confusion, inconsistency, and guesswork, we’re not just leaving behind a mess. We’re passing the cost on to the next crew, the next contractor, the next city that has to maintain or expand what we’ve built. And they’re going to find themselves staring at undocumented splices, missing slack, mismatched routes, and wondering what we were thinking.

We know what we were thinking. We were thinking about getting it done.

That’s what this disconnection costs us. It costs us the opportunity to build something we can stand behind. It costs us the ability to look a client in the eye and say, “This was built to last.” It costs us the respect this trade deserves, because when the work is compromised, so is the reputation of the people who built it.

Not to complain. Not to point fingers. But to protect what matters. To say the hard things before the damage becomes irreversible. To rebuild pride in this craft by getting back to the clarity that made it a craft in the first place.

Because if we’re not building with clarity, we’re just burying the next problem.

How We Got Here

And if it feels like no one’s in control, it’s because, at a systems level, no one really is. The work is real. The deadlines are real. The money is very real. But the ownership? That’s what went missing somewhere along the way. Everyone involved in these builds owns their part of the process: engineering owns the drawings, construction owns the field, PMs own the schedule, ISPs own the vision. But no one owns the full lifecycle. And it’s in those handoffs, those gaps between responsibilities, where the clarity gets lost and the problems take root.

The engineer designs a route based on aerial imagery and best guesses, then hands it off and rarely sees how it gets built. The crew shows up to a site that doesn’t match the plan and makes it work with what they’ve got. The PM juggles competing priorities while absorbing the fallout from issues they didn’t create. The contractor gets blamed when things go sideways in the field, even though they never had control over the design, permitting, or material delivery timelines. And the owner, trying to keep everything on track, signs off on a completed job without really knowing what’s buried beneath the surface.

The project gets closed. The milestones are marked off. Everyone moves on. But under the lid of that handhole, or beneath the trench that got backfilled in a rush, is a record of how disconnected the process really was. Unlabeled fiber. Slack that’s missing. A splice case no one documented. A bore path that didn’t match the plan, and now never will. It all worked just well enough to pass inspection and meet the light test. But it wasn’t built with the future in mind. And deep down, most of us know it.

That’s how we got here. We didn’t arrive at this point because of one bad decision or one careless contractor. We slid into it over time. Slowly. Quietly. Through a thousand subtle compromises, small delays, and moments where someone looked at a problem and decided, “It’s good enough for now.” And unless something changes, that’s exactly where we’ll stay, spending more money, building with less clarity, and hoping that the next person to open that handhole doesn’t see the confusion we left behind.

This newsletter exists because we need to step back and tell the truth about what’s happening. Not to assign blame, but to reestablish ownership. Because as long as every group only owns their slice of the process, and no one owns the whole, the same breakdowns are going to keep happening in the same places. And they’ll keep costing us more, more time, more trust, more talent, and eventually, more credibility.

If we care about this trade, if we care about the work, and if we care about the people coming up behind us, then we can’t keep patching broken systems with hope and pretending it’s going to hold. It won’t.

Let’s Talk About It

This newsletter didn’t come from frustration alone. It came from a deep respect for this trade, and a growing concern that the things that make it strong are starting to slip. I’ve been in this industry for more than two decades, and I’ve seen what good fiber construction looks like when everything is working: clear designs, aligned teams, honest timelines, well-trained crews, and builds that speak for themselves. I’ve also seen what happens when those things break down, not just once, but over and over, across project after project, until people start to believe that confusion is just “how it is.” That’s the shift I’m pushing back against. Not with noise. Not with blame. But with clarity.

This exists to start the conversations we’re not having often enough. Not just about bad splices or missed slack loops, but about what those things represent. They represent systems that don’t support the people doing the work. They represent a process that’s been hijacked by urgency. They represent a breakdown of ownership, alignment, and professional pride. And unless we’re willing to say that out loud, nothing’s going to change. We’ll keep building networks that pass light but fail the long test. We’ll keep training the next generation to do the job fast instead of doing it right. And we’ll keep losing good people to burnout, disillusionment, or the belief that quality doesn’t matter.

My goal with this is simple: to put words to the things many of us have seen and felt, but haven’t known how or where to talk about. I want to give voice to the experienced PM who’s been holding it all together without support. To the crew member who wants to do it right but keeps getting handed the wrong prints. To the engineer who cares deeply but hasn’t seen what happens when their plan meets real terrain. To the contractor who’s stuck in the middle, trying to deliver good work in a broken system. This is for them. And it’s for anyone who believes that this industry still has room for craftsmanship, ownership, and clarity, even in the middle of all the noise.

We’re not going to fix it overnight. That’s not the promise. But we can start small, by having real conversations. By putting clarity back into the process. By sharing knowledge. By challenging the shortcuts that don’t serve us. And by calling things what they are, with enough honesty to make room for something better.

That’s what Fiber Done Right is about. That’s why this newsletter. Not to be another voice in the chaos, but to be a place where we can step back, see the whole picture, and get to work building something we actually believe in.

If that resonates with you, then stay with it. Share it. Talk about it. Use it. Because better work doesn’t start with more pressure. It starts with more clarity.

And that starts with us.

– Geoff

Fiber Done Right