Building Where Institutions Won't

When formal institutions will not serve a need, the skilled operator builds the informal infrastructure that does.

The Gap Between Need and Provision

Formal institutions are designed to serve the needs they were built to address at the time they were built. They are not designed to serve the needs that emerge after their design was fixed, or the needs of populations that were not central to their design, or the needs that fall in the gaps between institutional mandates. These gaps are structural features of institutional systems, not temporary failures awaiting correction. They persist because no actor with the authority to close them has a sufficient interest in doing so, or because closing them would threaten other interests that the institutional system is organized to protect.

The skilled operator who faces a genuine need that formal institutions will not serve has two options: wait for the institution to change, or build the informal infrastructure that serves the need without the institution. The first option is rational when the expected cost of waiting is lower than the expected cost of building. The second option is rational when the gap is large, the wait is indefinite, and the cost of the unmet need is concrete and accumulating.

What Informal Infrastructure Looks Like

Informal infrastructure is the network of relationships, practices, resources, and shared understandings that allows a community to accomplish what formal institutions will not enable. It is less visible than formal infrastructure because it lacks the documentation, the official mandate, and the physical presence that mark formal institutions. But it is no less functional — and in domains where formal institutions are systematically absent or hostile, it is often more functional, because it was built by and for the people it serves rather than designed by actors with different interests and imposed from above.

Informal infrastructure builds through a consistent sequence: need becomes visible, one or a few actors begin improvising solutions, the improvised solutions work well enough to attract others, the practices become regularized through repeated use, the relationships supporting the practices strengthen, and eventually the informal network is sufficiently dense and reliable that it functions as infrastructure — as the background system that others take for granted when they operate in the domain.

The Formalization Question

Successful informal infrastructure eventually faces the formalization question: should what has been built be institutionalized, acquiring the protections and resources that formal status provides, at the cost of the flexibility and community ownership that informal status allows? This is not a question with a universal answer. Formalization protects what has been built against the loss of the individuals who built it. It also tends to shift control toward actors with institutional authority and away from the community the infrastructure was built to serve. The decision requires assessing whether the protection benefit outweighs the control cost in the specific context.

Building where institutions won't is not defiance of institutional order — it is the demonstration that the need exists, that the provision is possible, and that the institution's failure to provide is a choice rather than an impossibility.