Coordination Is an Interface Problem

Many difficult problems have a strange emotional texture. People agree that the outcome is bad. They can describe a better one. They may understand the mechanism producing the damage. The pattern continues because no participant can safely move the whole system alone.

A company keeps optimizing a narrow metric because competitors do. A team protects its own roadmap because the organization rewards local performance. A maintainer keeps absorbing unpaid work because every user assumes somebody else will sustain the dependency. Each move can make sense from inside the participant's position. Together, the moves create an outcome few people would select directly.

This is a coordination failure. The failure sits between intention and action. People lack a sufficiently credible way to move together, divide risk, verify commitment, distribute responsibility, or preserve the result.

A better outcome is visible. Most participants can describe a result they would prefer: maintained infrastructure, fairer work, safer systems, cleaner environments, or a healthier community.

Acting first carries a cost. A participant who moves alone may pay more, move slower, reveal information, accept risk, or lose ground to someone who keeps optimizing for the existing rules.

Trust remains incomplete. People cannot verify whether others will contribute, follow the agreement, maintain the result, or withdraw once cooperation becomes inconvenient. Everyone therefore continues making locally defensible choices, allowing the harmful pattern to reproduce itself.

Collective-action problems were studied long before digital networks. Public-goods communities brought them into product conversations and treated governance, contribution, shared infrastructure, and ownership as things that could be designed and tested in the open.

This expanded the design space. It also exposed the distance between formal rules and healthy institutions. A visible vote can still be shaped by concentrated influence. A shared organization can still depend on an exhausted minority. Ownership does not automatically produce care.

The lasting contribution is the recognition that coordination deserves product design. Rules, identity, participation, governance, and exit all become surfaces people must understand and use.

Incentives matter because systems teach participants which behavior survives. They remain one layer among many. People also coordinate through reputation, identity, rules, ritual, friendship, professional norms, memory, shared language, physical place, and the expectation of meeting again.

Elinor Ostrom's work on communities governing shared resources challenged the assumption that commons inevitably collapse unless a market or central authority takes control. Durable arrangements can emerge when participants define boundaries, make rules suited to local conditions, monitor use, resolve conflict, apply proportionate consequences, and retain meaningful influence over governance.

This widens the role of design. The work includes onboarding, language, evidence, relationships, facilitation, moderation, documentation, conflict resolution, accessibility, maintenance, and the emotional cost of participation.

People need clear ways to find one another, understand the situation, contribute useful work, make decisions, record what happened, and keep the result alive over time.

Design can make dependencies visible, reduce uncertainty, clarify responsibility, support disagreement, and give maintenance the same dignity as launch.