Decentralized governance needs accountability

Decentralization describes a distribution, not a virtue

A network may have many nodes while a few people control the money, software, or agenda. An organization may remove job titles while leaving informal influence untouched. Decentralization is useful only when we specify what is distributed: information, infrastructure, ownership, decisions, or the power to change the rules.

For a community, the aim might be to let local teams choose activities while preserving shared standards for access and spending. For a knowledge project, it might be to let contributors improve a resource while keeping an accountable editorial process. Neither aim is achieved merely by calling the project decentralized.

The polycentric idea

The Ostrom Workshop’s account of polycentric governance distinguishes the process of governance from government as an organization and emphasizes the many tasks and actors involved. That offers a useful lens for designing several decision centers that interact, rather than assuming one center must manage everything. Ostrom Workshop · What Is Polycentric Governance?

Our application is to ask which scale fits each problem. A neighborhood may understand a local maintenance need. Several neighborhoods may need a common service. A wider institution may be needed to protect rights or resolve conflicts between them. Moving every decision to the smallest unit can be as misguided as moving every decision to the largest.

Make the structure readable

A participant should be able to answer five questions without being an insider: who can propose a change, who decides, where the reasoning is recorded, how to challenge the outcome, and how a decision-maker can be replaced.

Write those answers in ordinary language. Keep them close to the work. A beautiful governance document is of little use if actual decisions happen in an inaccessible chat. Compare the formal process with the real one, especially when a founder, funder, or technically skilled member has unusual influence.

For each role, define a domain, a budget or resource boundary, and a review date. Distribute knowledge about how the role works so another person can take it over.

Plan for disagreement before it arrives

Suppose a local team wants to spend shared funds on a project that another team believes is unfair. The system needs more than a declaration of trust. It needs an agreed method for reviewing the claim, a way to protect people who raise concerns, and a person or body responsible for reaching a decision.

A small association might use an independent rotating review group for ordinary disputes, with clearly described escalation for matters outside its competence. The exact arrangement depends on context. The principle is that people should not have to appeal directly to the person whose conduct they are challenging.

Keep the response proportional. A missing receipt and a serious abuse allegation are different matters. Informal governance should not pretend to replace legal duties or appropriate professional processes.

Test whether power really moved

Look at a recent consequential decision. Who framed the options? Who controlled the evidence? Who could say no? Who carried the risk? Who could exit without losing access to something essential? These questions reveal more than the number of working groups on a diagram.

Then examine maintenance. Can members recover records, rotate responsibilities, and keep essential work running when a key person leaves? If one volunteer holds the only knowledge of a critical system, the organization has a hidden point of dependency.

A well-designed decentralized system makes local judgment possible and shared obligations enforceable. Its strength is not the absence of responsibility. It is the ability to locate responsibility, question it, and improve it.