A water management intervention is designed around a primary objective — flood control, agricultural productivity, drought resilience. The system being managed, however, serves multiple users with different and partially incompatible needs: farmers, fishers, urban residents, upstream and downstream communities, different economic classes. The intervention requires shared infrastructure — sluice gates, canals, embankments — whose operation directly affects the distribution of benefits and risks between these groups.

The forces in tension

The logic of project design pushes toward a single optimizing objective, because that is what makes a project legible, fundable, and evaluable. But water systems are inherently distributive — every management decision about timing, volume, and direction of water creates winners and losers. The more precisely the infrastructure controls water, the more consequential those decisions become, and the more intensely different user groups will compete to control them. Meanwhile, the project timeline creates pressure to complete construction and declare success before the slower-moving social conflicts fully materialize. Evaluations happen too early, when the infrastructure is new and the governance arrangements are still formally in place. The people who designed the intervention are rarely the people who have to live with the conflicts it generates.

The pattern

When an intervention concentrates control over a shared resource into a small number of decision points — sluice gates, allocation rules, governance bodies — while serving multiple groups with conflicting interests, conflict over those decision points is structurally inevitable. This conflict will be predicted in project documents, acknowledged in stakeholder consultations, and then not resolved, because the mechanisms proposed to manage it are procedural rather than relational. The written arrangement substitutes for the actual relationship. The conflict emerges anyway, and is then treated as a social failure rather than a design failure.

Consequences

When this pattern plays out, the most powerful user groups capture the critical control points — wealthier shrimp farmers control the sluice gates, politically connected officials manage the structures. More vulnerable groups lose access to the resource they depended on, often in ways that are diffuse and hard to document. The project is evaluated as a technical success while the social fabric around it deteriorates. The next project inherits the same multi-user situation, acknowledges the same conflicts in its documents, and proposes the same procedural solutions.

The pattern is not resolved by better conflict management procedures, but by changing the design logic. Interventions need to be evaluated not only on their primary objective but on the distribution of control they create and the conflicts that distribution predictably generates. Governance arrangements need to precede infrastructure, not follow it. The relationships between user groups need to be developed and tested before the infrastructure makes those relationships consequential. And evaluation needs to happen late enough, and independently enough, that it can honestly capture what the intervention actually produced.

Related patterns

— Infrastructure Without Culture (governance arrangements collapse when project budgets end) — The Boundary Creates the Outside (intervention benefits one group by disadvantaging another) — Governance Cannot Reflect on Itself (the institution that created the conflict evaluates whether the conflict occurred)