We had designers buried in a backlog they couldn’t escape. Down the hall, permit techs had almost nothing to do. Same company. Same projects. Same deadline pressure. Nobody was sharing resources because nobody was looking at the whole picture.
That’s not a workload problem. That’s a structure problem.
I’ve spent a lot of time thinking about project management methodology — agile, waterfall, hybrid — and I’ve come to believe that most teams in telecom engineering get stuck debating the wrong thing. The methodology isn’t the problem. The visibility is.
Here’s what I mean.
Waterfall makes sense on paper — until the field happens
Broadband builds are sequenced by nature. Permits before construction. Design before permits. Survey before design. That’s waterfall logic, and it’s not wrong. The problem is that waterfall assumes each phase completes cleanly before the next one starts. In telecom, it almost never does. Pole conditions change. ROW gets denied. A design that looked clean in GIS falls apart when someone actually drives the route. Pure waterfall doesn’t handle that gracefully — it just creates bottlenecks.
Agile sounds appealing — but it wasn’t built for this
Agile is a great framework. In software. In a construction and engineering environment, “sprint to deliver a working increment” doesn’t map cleanly to pulling fiber through conduit or managing a make-ready backlog across 12 counties. Teams that try to force-fit pure agile into field engineering usually end up with a lot of standups and not a lot of structure. That’s frustrating for everyone.
Hybrid is what actually works — but only if you can see the whole board
Back to those permit techs sitting idle while designers drowned. The managers running each team weren’t doing anything wrong — they were heads-down, focused on what was in front of them. That’s what happens when workloads pile up. Nobody had time to look up and ask: “What does the whole portfolio need right now?”
When we started building a centralized resource model — pulling people out of siloed teams and managing them against the full project portfolio — things started shifting. Not because we picked a better methodology, but because we finally had visibility into where the work actually was and where the capacity actually was.
That’s hybrid in practice. Structured sequencing where the work demands it. Flexibility to move people and reprioritize where it doesn’t. And a PMO function that can see across the whole system instead of just managing up from individual project lanes.
The results showed up before the theory caught up
We didn’t roll out a new methodology with a big announcement. We just started making changes — centralizing resources, building cross-functional capability, getting better tools for capacity visibility. The backlog started moving. Utilization evened out. The designers could breathe. The permit techs were actually growing their skills instead of waiting for work to come to them.
No methodology saves you if you can’t see the whole picture. But when you can — the methodology almost figures itself out.
Curious if others in telecom or broadband construction have run into the same structural challenges. What worked for you?
