USA: The California water model: Resilience through failure

Source(s): California WaterBlog

By Nicholas Pinter, Jay Lund, and Peter Moyle

[...]

California’s droughts and floods and tension between economic growth and environmental protection have pushed it to develop a diverse toolkit for managing water.

The toolkit consists of an integrated system of infrastructure, laws, institutions, and economic tools. This system, the ”California water model,” has evolved from the first Spanish settlement, through the gold mining era, the ascendancy of agriculture and major cities, to the recent broad mix of objectives that includes strong environmental protection. California has steadily adapted its water management by making mistakes and then learning from those mistakes.

[...]

We suggest that a prerequisite for providing and maintaining healthy aquatic ecosystems and adequate supplies of clean water is “far-sighted incrementalism” among water managers and political leaders.  Incrementalism involves addressing seemingly intractable problems by small forward-looking steps.  “Far-sighted,” at least in California, has involved forward-thinking planning among scientists, managers, and leaders during and after each water-related crisis.  The common response after a damaging flood is reactive – repair the levee breach and rebuild floodplain neighborhoods.  Far-sighted leaders see opportunities in such a crisis to move the system forward, usually incrementally, in a longer-term strategic direction (usually too controversial or difficult to achieve in one step).  California must continue to support organized and independent learning from and adapting to disasters and extremes.

[...]

Explore further

Hazards Drought Flood
Country and region United States of America
Share this

Please note: Content is displayed as last posted by a PreventionWeb community member or editor. The views expressed therein are not necessarily those of UNDRR, PreventionWeb, or its sponsors. See our terms of use

Is this page useful?

Yes No Report an issue on this page

Thank you. If you have 2 minutes, we would benefit from additional feedback (link opens in a new window).