The Visibility Problem
When you are responsible for twenty or more active FTTH construction sites spread across multiple cities, the first thing you lose is visibility. Not because the information does not exist — it exists in abundance, often too much of it — but because it is scattered across site managers' notebooks, contractor spreadsheets, permit tracking emails, and quality inspection reports. The programme manager's challenge is not collecting data; it is creating a single, trustworthy picture from data that lives in fifteen different places.
I learned this lesson the hard way during the early months of the STC national FTTH rollout. We had site managers sending daily reports by email, contractors maintaining their own progress spreadsheets, and a quality team producing inspection reports in a separate system. When the programme director asked a simple question — "How many homes passed are we delivering this month, and are we on track?" — it took three days to assemble an answer, and even then, the numbers from different sources did not always agree.
Building the Single Source of Truth
The solution was to build what I call a single source of truth — one system that holds the authoritative status of every site, every work package, and every milestone. This is not a software product; it is a management discipline supported by tools. The principles are simple: every site has one status, reported in one place, updated on one schedule. Discrepancies between sources are resolved by going to the site, not by arguing over email.
The single source of truth does not replace site-level management — it amplifies it. Site managers still run their sites, but they report status into a shared system using a standard format. The standardization is what makes aggregation possible. When every site reports its status using the same work package definitions, the same milestone criteria, and the same quality metrics, the programme team can see patterns that would otherwise be invisible.
The Daily Status Report
The cornerstone of the visibility system is the daily status report. Not a lengthy document — a structured data update that takes a site manager five minutes to produce. The report answers four questions for each site: What work was completed today? What is planned for tomorrow? What issues are blocking progress? What materials are needed?
The power of the daily report is not in any single day's data — it is in the trend. When a site reports the same blocking issue three days in a row, the programme team can see that a pattern is forming and intervene before the issue becomes a week's delay. When material requests spike across multiple sites simultaneously, procurement can anticipate a shortage before it hits.
The Programme Dashboard
The dashboard is the visible face of the single source of truth. It takes the daily status reports and transforms them into a visual picture of the programme's health. The most effective dashboards I have built use a simple traffic-light system: green for sites on track, amber for sites with minor issues being managed, red for sites requiring intervention.
The dashboard must be accessible to everyone — site managers, contractors, quality teams, and executives. When everyone sees the same picture, the conversations change. Instead of debating whose numbers are right, the conversation becomes "what are we going to do about the red sites?" The dashboard creates a shared focus.
Escalation Protocols
Visibility without action is just reporting. The system needs escalation protocols that define what happens when a site goes red. In my experience, the most effective escalation protocols have three levels. Level one is the site manager resolving the issue with their team and the local contractor. Level two is the programme team providing additional resources or intervention — a specialist, a material expedite, a permit escalation. Level three is executive escalation, where the issue is serious enough to require a decision about scope, schedule, or budget.
The key is that escalation is automatic and time-bound. A site that goes red does not sit red for two weeks before someone notices. The dashboard flags it, the programme team reviews it within twenty-four hours, and a decision is made about the level of intervention needed. This sounds bureaucratic, but in practice it is liberating — site managers know that when they flag a problem, help is coming, not blame.
The Weekly Programme Review
The daily report and the dashboard are operational tools. The weekly programme review is the strategic tool. Once a week, the programme team sits down with the dashboard and asks bigger questions: Are we on track for the monthly target? Which sites are trending in the wrong direction? Are there systemic issues — a contractor performing poorly across multiple sites, a material shortage affecting a whole region, a permitting bottleneck in a specific municipality?
The weekly review is where patterns are identified and strategic decisions are made. It is where the programme team shifts resources from sites that are ahead of schedule to sites that are behind. It is where the decision is made to add a contractor or remove one. The daily report tells you what happened today; the weekly review tells you what it means.
When the System Breaks
No system works perfectly all the time. The most common failure mode is when site managers stop reporting accurately — either because they are too busy, or because they are afraid that reporting a problem will get them in trouble. The defense against this is a culture that treats honest reporting as a professional obligation, not a confession of failure. When a site manager reports a problem early, that is good management. When a site manager hides a problem until it explodes, that is a failure.
The second failure mode is dashboard overload — so many metrics, so many colors, so much data that the dashboard becomes noise. The defense is ruthless prioritization. The dashboard should show the few metrics that actually drive programme outcomes: homes passed, sites activated, schedule variance, quality pass rate, and open issues. Everything else is supporting data, not headline data.
The Payoff
When the visibility system works, the programme feels different. Questions get answered quickly. Problems get caught early. Resources get allocated where they are needed, not where they are demanded. Executives trust the numbers because the numbers are consistent. Site managers feel supported because their issues are visible and addressed. Contractors perform better because they know the programme team can see exactly what they are doing.
That is what it means to manage twenty concurrent sites without losing visibility. Not a superhuman effort of multitasking, but a disciplined system that makes the complex manageable.