Divided We Fall: The Dangerous Fragmentation at the Heart of America's Infrastructure Governance
America's infrastructure is, in many respects, a marvel of accumulated engineering ambition. Its highways knit together a continent, its pipelines carry energy across mountain ranges, and its water systems serve hundreds of millions of people daily. What is far less impressive — and considerably more dangerous — is the governance architecture sitting behind all of it. Across federal, state, and local levels, the agencies responsible for keeping these systems operational often struggle to share even the most fundamental operational data with one another. The result is a patchwork of institutional blind spots that, under the right conditions, can transform a manageable disruption into a cascading catastrophe.
The problem is not new, nor is it unrecognized. Decades of reports from the Government Accountability Office, the National Infrastructure Advisory Council, and a succession of post-disaster reviews have documented the coordination deficits that haunt American infrastructure governance. What remains stubbornly persistent, however, is the structural reality that created those deficits in the first place: a system built on jurisdictional silos, legacy communication protocols, and political incentives that consistently reward local control over collective resilience.
When the Left Hand Does Not Know What the Right Hand Is Managing
Consider the anatomy of a typical infrastructure corridor. A single interstate highway may cross the jurisdictions of a state DOT, a metropolitan planning organization, a county public works department, and — where federal lands are involved — one or more Interior or Defense Department entities. Each of these bodies maintains its own asset databases, operates on its own inspection schedules, and reports upward through entirely separate chains of authority. In routine circumstances, this fragmentation is merely inefficient. During an emergency, it can be lethal.
The aftermath of Hurricane Katrina in 2005 remains perhaps the most exhaustively studied case of interagency coordination failure in American history. What the after-action reviews consistently revealed was not simply a failure of resources, but a failure of information flow. Local emergency managers lacked real-time situational awareness from state transportation agencies. State officials could not access federal asset inventories. FEMA's communication systems were incompatible with those of the Army Corps of Engineers. The physical infrastructure of the Gulf Coast was damaged by the storm; the institutional infrastructure that should have coordinated the response was, in many ways, broken before the first hurricane made landfall.
More recently, the 2021 Texas winter storm exposed similar fractures. The Electric Reliability Council of Texas, which operates the state's largely isolated grid, had limited formal coordination mechanisms with neighboring regional transmission organizations. Natural gas pipeline operators — regulated under a separate federal framework — had not systematically shared infrastructure vulnerability data with grid operators. When the cold snap arrived, agencies that needed to act in concert had, in practice, never built the relationships or protocols required to do so.
Jurisdictional Mandates That Were Never Designed to Overlap
Understanding why these coordination failures persist requires grappling with the foundational logic of American federalism as it applies to infrastructure. Most of the statutory frameworks governing critical infrastructure were designed at different historical moments, in response to different perceived threats, and with different assumptions about who bore primary responsibility for system integrity.
The Federal Energy Regulatory Commission, the Environmental Protection Agency, the Department of Transportation, the Department of Homeland Security, and dozens of state-level counterparts each operate under distinct legislative mandates. Those mandates were not written to be complementary. In many cases, they actively create friction. A project that requires environmental permitting from one agency, right-of-way approval from another, and safety certification from a third can spend years navigating processes that were never designed to interface with one another — let alone share data in real time.
The information technology dimension of this problem compounds the institutional one. Many state and local infrastructure agencies still rely on asset management systems built in the 1990s or earlier, systems that were never designed to interoperate with federal platforms. When the Department of Homeland Security's Cybersecurity and Infrastructure Security Agency attempts to push threat intelligence to a municipal water utility, it is often doing so across a technological gap that no amount of goodwill can fully bridge.
Emerging Frameworks Trying to Build Bridges
There are, to be clear, genuine efforts underway to address this fragmentation. The Infrastructure Investment and Jobs Act of 2021 included provisions aimed at improving data sharing between transportation agencies and created new incentive structures for states that adopt interoperable asset management platforms. CISA has expanded its sector-specific agency coordination model, working to establish clearer lines of communication between federal oversight bodies and the private operators who own much of the nation's critical infrastructure.
Several states have begun experimenting with unified infrastructure coordination offices — single points of contact designed to cut across the traditional departmental boundaries that slow information exchange during emergencies. Virginia's Commonwealth Preparedness Working Group and California's Office of Emergency Services have both moved toward more integrated situational awareness platforms that draw data from transportation, energy, and water systems simultaneously.
At the federal level, the National Infrastructure Simulation and Analysis Center has worked to develop modeling tools that allow agencies to visualize cross-sector interdependencies — understanding, for instance, how a disruption to a regional fuel supply network will cascade into transportation and emergency services. These tools represent a meaningful conceptual advance. The challenge is ensuring that the agencies who most need them have both the technical capacity and the institutional authorization to use them.
The Political Economy of Coordination
Perhaps the most underappreciated obstacle to genuine interagency coordination is not technical but political. Local officials who cede data access or operational authority to state or federal partners are, in a very real sense, giving up leverage. Infrastructure control is political capital. The official who controls access to a water system or a transit network controls something of profound community value, and the incentive to maintain that control — even at the cost of system-wide resilience — is often stronger than the abstract case for coordination.
This dynamic does not make coordination impossible, but it does mean that purely technical solutions will always fall short. Sustainable interagency frameworks require political architecture as much as they require software architecture. They require agreements on data governance, liability, and decision authority that must be negotiated and renegotiated across election cycles and administrative transitions.
The federal government can offer financial incentives, as it has begun to do. It can establish standards and reporting requirements. What it cannot easily do is change the underlying political incentives that make local officials reluctant to share operational control — or the institutional cultures that have grown up around decades of siloed governance.
Building the Connective Tissue
The path forward is neither simple nor cheap. It requires sustained investment in interoperable technology platforms, the development of shared data standards that agencies at every level can practically adopt, and the creation of coordination mechanisms that have genuine authority rather than merely advisory status. It requires training programs that give infrastructure professionals the skills to operate across institutional boundaries, and leadership at the federal level willing to make interagency coordination a condition of infrastructure funding rather than an afterthought.
Most fundamentally, it requires a shift in how America conceptualizes infrastructure governance — away from a model built on jurisdictional ownership and toward one built on system-wide accountability. The physical systems that keep this country running do not respect agency boundaries. The institutions charged with protecting them can no longer afford to either.