Wetlands as Infrastructure

A wetland does not look like infrastructure. It looks like nothing in particular: reeds, still water, mud. This is why it keeps getting filled in. Infrastructure looks like a road, a pipe, a drainage channel. It has a clear function and a clear cost. A wetland has a function too, but it is distributed, invisible, and difficult to price.

What a healthy wetland does: it holds water during rain events, releasing it slowly rather than all at once. It filters runoff before it reaches rivers or groundwater. It regulates the temperature of the land around it; cities with intact wetlands are measurably cooler than those without. It supports species that would not otherwise survive in an urban environment.

None of these functions appear on a balance sheet. So when a wetland sits next to a development site, it tends to lose.

Designing with water

The alternative is to treat the wetland as a design asset rather than an obstacle. This is not a new idea; landscape architects have been making this argument for decades. But it remains an argument that has to be made project by project, site by site.

On the Kacyiru mixed-use project, the wetland condition of the site informed every decision: the orientation of the building, the management of surface water, the species planted in the public realm, the design of the roof. The building is better because of the wetland, not in spite of it.

On the public space project at the wetland edge, the brief was even more direct: make the ecological condition of the site the subject of the design, not something to be worked around. The learning zones, the boardwalks, the play spaces: all of them are organised around the water and the species that live in it.

The result is a public space that changes with the seasons, that is different in the morning and the afternoon, that rewards return visits. This is what infrastructure can be, when it is designed rather than simply installed.