When we hear the word infrastructure, we imagine concrete. Roads, drainage, power lines, hospitals and cooling systems all fit comfortably inside the category. Physical systems matter because they determine whether societies continue functioning during shocks.
But they are not the only infrastructure doing the work.
A flood-warning system depends on sensors, telecommunications and sirens. It also depends on thresholds that institutions agree to use, protocols determining who acts, budget authority, relationships with communities and a mechanism for learning after each event. Remove the physical infrastructure and the system fails. Remove the institutional infrastructure and it may fail just as completely.
The second kind is harder to see, and what is hard to see is often harder to fund. A donor can finance a data platform. A government can procure equipment. A development bank can finance a physical asset. It is harder to put a capital value on trust between departments, a shared measurement system, a technical standard or a standing mechanism that resolves conflicts before they become crises.
Yet collective-action research repeatedly points toward these connective systems. Collective Impact treats shared measurement, continuous communication and backbone support as integral to the work rather than as optional administration. Systems-orchestration practice likewise treats shared knowledge systems, standards and financing pathways as infrastructure for collective action.
Perhaps we have made infrastructure too synonymous with objects.
Consider project preparation. A city may have a strong climate plan and a development bank may have money, yet nothing happens because there is no permanent capability for converting the plan into costed, governed and appraisable projects. What is missing is not necessarily capital or policy. It is an institutional bridge.
Or consider heat. A cooling centre can be built quickly, but protecting workers may require heat thresholds, employer protocols, public-health surveillance, electricity planning, labour rules and local communication. Those are not supporting activities around the real intervention. They are part of the intervention.
There is an obvious danger in this argument. If everything becomes infrastructure, the word stops meaning anything. We should not call every network, meeting or training programme infrastructure simply because it sounds important.
A harder definition helps. Infrastructure should enable repeated activity by many actors, survive beyond a single project, and lower the cost of acting the next time. A road does this physically. A shared data standard can do it institutionally. A project-preparation facility can do it financially. A trusted protocol between a meteorological agency and a social-protection programme can do it operationally.
The key word is repeated. The best infrastructure makes difficult action ordinary.
That gives philanthropy and public finance a better question. Instead of asking only, “What asset should we fund?”, we should sometimes ask, “What capability has to exist so that many actors can use many assets better?”
This may be especially important in adaptation, where benefits are distributed and responsibility is fragmented. The most important missing investment may not be another visible project. It may be the invisible substrate that allows hundreds of future projects to work.
Sources
FSG, Collective Impact.
FSG, Understanding the Value of Backbone Organizations.
Systems Orchestration, Coordinating Complex Change.
Arunabha Bhattacharya 
Leave a comment