Coordinating without a center

Decentralization is a choice many movements make instinctively — and for good reason. A movement with no single headquarters has no single throat to choke. You can't take down a network by arresting its leader or deplatforming its main account if the network doesn't have one. Under the conditions of active suppression that this series has been addressing, resilience through distribution isn't just a preference — it's a survival strategy.

But decentralization creates its own problem. A network that can't be taken down can also fail to move. Thousands of autonomous local groups, each doing their own thing, aren't a movement — they're a lot of people who agree with each other. The difference between a distributed network and a coordinated movement is the infrastructure that connects them: shared protocols, communication channels that cross organizational boundaries, and a common understanding of what "acting together" means even when no one is in charge.

This article examines what that infrastructure looks like in practice, through three cases that have worked it out in very different contexts: the No Kings coalition in the United States today, the Indivisible/50501/MaydayStrong coordination model, and the historical Solidarity movement in Poland. Each offers a different lesson about the relationship between decentralization and coordination — and all three point toward the same core principle: the goal isn't to eliminate the center, it's to make the center unnecessary.

The decentralization paradox

The tension is real and worth naming directly. A centralized organization is efficient — decisions get made, resources get deployed, everyone knows who to call. It's also fragile. A centralized organization can be decapitated, infiltrated, legally attacked, or simply exhausted. Movement history is full of organizations that fell apart when their leader was imprisoned, discredited, or burned out.

Decentralized networks distribute that vulnerability. No single point of failure means no single point of attack. But they're genuinely harder to coordinate. If every local group decides for itself when to act, what to demand, and how to communicate, the result is noise — or worse, internal conflict that consumes energy that should be going outward.

The way through this paradox isn't to pick one side or the other. It's to think carefully about what needs to be centralized and what doesn't. The answer, in every successful case: what needs to be shared is infrastructure and protocol, not control.

Case study: The No Kings coalition

The No Kings coalition didn't start as an organization. The 50501 Movement coined the "No Kings" brand and traces its origins to Reddit, where grassroots organizers began coordinating in late 2024. From that informal beginning, it grew into something that has no clear precedent in American political history: a sustained, escalating, geographically distributed mass movement that grew with each iteration, reaching an estimated eight to nine million participants on March 28, 2026.

What makes it instructive isn't the size — it's the structure. The movement's official pages and publicly distributed host toolkit frame No Kings as a people-powered, decentralized set of actions, providing guidance on safety, messaging, and event planning for local hosts rather than listing central leaders or a single organizing committee. That toolkit is the key artifact: a document that enables consistent action without requiring a chain of command.

Its decentralized model — national branding and coordination, local execution and permit-holding — has proven resilient and scalable across three protest cycles. The branding is shared. The toolkit is shared. The date is shared. Everything else is local.

The nokings.org platform functions as a national coordination tool for autonomous local chapters and activist groups to list events, share resources, and connect participants without requiring hierarchical organization. This is what digital infrastructure for a decentralized movement looks like in practice: a platform that makes it easy to join, easy to act, and easy to see that you're part of something larger — without routing everything through a bottleneck.

The No Kings model shows what "coordinating without a center" means at the action level. The shared elements — brand, toolkit, platform, date — create enough coherence that millions of people can act simultaneously without requiring a single decision-maker to authorize each event. The local groups retain autonomy over everything that matters locally: who speaks, what the specific demands are, how the event is run. What they give up is very little.

Case study: Indivisible, 50501, and MaydayStrong

The No Kings coalition isn't a single organization — it's a coalition of coalitions, and how those organizations coordinate with each other is its own lesson.

50501 was born from social media rather than established organizations, but it's not leaderless. By the April 5 "Hands Off" protests — which drew an estimated 5.2 million people at 1,200 locations — the coalition included MoveOn, Indivisible, Women's March, labor unions, and environmental groups. But this coalition operates differently than traditional organizing structures: there's less top-down control and more working side-by-side.

That distinction — side-by-side rather than top-down — is crucial. These organizations don't merge. They don't subordinate themselves to a central authority. They align on shared goals, coordinate on shared dates and messaging, and then each bring their own infrastructure, relationships, and capacity to bear. Different groups in different states emphasize distinct priorities, and 50501 commits to not telling "people what their demands should be."

MaydayStrong, which organized around May 1, 2026, demonstrates the same principle extended to the labor dimension: millions of workers, students, and families taking coordinated action across the country, demanding a nation that puts workers over billionaires, refusing business as usual through "No School. No Work. No Shopping." Multiple organizations, multiple constituent bases, one day, aligned messaging — achieved without a unified command structure.

What makes this coordination possible isn't a shared organizational chart. It's shared infrastructure: common platforms for listing and finding events, shared messaging frameworks that different organizations adapt to their audiences, and — crucially — relationships between organizers built up over time through repeated coordination. The infrastructure enables the relationships; the relationships make the coordination work.

The practical lesson here is about what organizers sometimes call "connective tissue" — the organizations and individuals whose primary function is to span boundaries. Every large coalition has people whose job is essentially to be on everyone else's calls, translate between different organizational cultures, and surface conflicts before they become crises. This role is rarely glamorous and often underfunded, but without it, coordination collapses into parallel tracks that never actually intersect.

Case study: Solidarity in Poland

The historical Solidarity movement in Poland offers a different kind of lesson — what decentralized coordination looks like under conditions of active state suppression, without the digital tools that today's organizers take for granted.

Solidarity was an extraordinary mobilization of citizens from all walks of life united in protest against living in a communist lie — a massive societal polity organized independently outside the realm of the state that encompassed a number of historical, cultural, philosophical and human experiences. At its peak it had ten million members. It survived martial law. It ultimately won.

What held it together under suppression was not a hierarchy that could be maintained when leaders were imprisoned — it was a culture of decentralized self-organization. When hundreds of Solidarity leaders were rounded up and detained, the opposition movement survived: arrested leaders found themselves replaced by other activists who avoided detention and by a number of female organizers who took leadership positions in the underground press and other Solidarity structures.

That resilience wasn't accidental. It was the product of a deliberate choice to build organizing capacity throughout the network rather than concentrate it at the top. It was the self-organizing experience gained during underground civil resistance, the well-developed underground press, and the extensive network of volunteers that gave Solidarity an important advantage over the communists.

The Solidarity case also illustrates a failure mode worth noting: coordination without a mechanism for resolving conflict. By 1981, as the movement grew and the economic situation deteriorated, isolated strikes broke out across the country — but the Solidarity leadership made no attempt to coordinate them or unify demands. A decentralized network that lacks conflict resolution infrastructure can find itself moving in multiple directions at once, dissipating energy that might otherwise have been focused. Decentralization is not a substitute for governance; it's a different form of it.

More recently, Poland has offered a contemporary lesson in digital coalition coordination. When half a million people converged on Warsaw in June 2023 to resist democratic backsliding, digital forms were used to survey participants on their motivations — women's health, education, immigrant rights, economic concerns — and that information was used to create campaign materials that reached different individuals while unifying them behind a shared opportunity. Digital platforms allowed participants to book seats on organized buses or carpool, while also preparing attendees for anticipated police action and helping them navigate quickly. Different organizations with different constituent bases, aligned on a shared moment, using digital infrastructure to coordinate logistics while preserving message diversity.

What these cases share

Three cases, three contexts, three different answers to the coordination problem — but the same underlying architecture. In each case, what enables coordination without a center is a combination of:

Shared infrastructure, not shared control. The toolkit, the platform, the date, the communications channel — these are things that organizations and individuals can use without giving up their autonomy. The No Kings host toolkit doesn't tell local organizers what to demand. It tells them how to run a safe, effective event. That's the right division of labor.

Protocols, not permission. In each of these cases, local groups don't ask for permission to act — they follow a protocol that tells them how to act in alignment with others. The difference is significant. Permission systems require a center; protocols distribute the decision-making.

Relationships as infrastructure. The connective tissue between organizations — the people whose job is to span boundaries, translate, and surface conflicts early — is infrastructure as much as any piece of software. It's slower to build and harder to maintain, but without it, the tools don't matter.

Redundancy at every layer. Solidarity survived martial law because organizing capacity was distributed throughout the network, not concentrated at the top. The No Kings coalition can lose its central platform and local chapters can still find each other. Redundancy isn't a backup plan — it's the design.

The tools that make this possible

The principles above require infrastructure to implement. A few categories of tools are doing most of the work in contemporary decentralized coordination:

Event aggregation platforms. The nokings.org model — a platform where autonomous local groups can register and list events, making the whole visible without centralizing the parts — is the most important category for mass mobilization. Action Network offers similar functionality for coalition organizing, allowing affiliated organizations to share lists and coordinate actions without fully merging their data.

Coalition communication channels. When organizations need to coordinate with each other rather than just run parallel actions, they need communication infrastructure that crosses organizational boundaries. Slack and Discord both work for this at the coalition level, though both carry the platform dependency risks covered in Article 1 of this series. For more sensitive coordination, Matrix/Element provides federated, self-hostable channels that don't route through a single corporate server.

Shared calendaring and action tracking. Knowing what other organizations are planning — and when — is prerequisite to genuine coordination. Google Calendar's shared calendar feature handles this for many coalitions; Movement Calendar (movementcalendar.com) was built specifically for this purpose in the progressive organizing ecosystem.

Shared data standards. The deeper form of interoperability — the ability for different organizations' systems to actually talk to each other — requires common data standards. In the progressive tech ecosystem, this is still underdeveloped. Action Network's open API allows some integration; the Movement Cooperative provides shared technical infrastructure for a consortium of organizations. But most coalitions still coordinate primarily through human relationships rather than system integration, which means the connective tissue problem never fully goes away.

Building for coordination before you need it

The hardest lesson from all three case studies is also the most actionable: coordination infrastructure has to be built during calm periods to function under pressure. The protocols have to be established, the relationships have to be formed, the platforms have to be tested, before the moment arrives when you need to move quickly.

For any coalition or local group, this means a few concrete things. Have a communication channel with peer organizations in your coalition that isn't dependent on any single platform — and that you use regularly enough that people actually check it. Have a shared understanding with your closest coalition partners about what "coordinating on a day of action" means operationally: who contacts whom, how quickly, with what information. Know which of your members and staff serve connective tissue roles — and make sure they're supported rather than quietly burning out on all that relationship maintenance.

And have a way to list your actions and find others' that doesn't require anyone's permission. The ability to say "here's what we're doing, here's when, here's how to join" — publicly, findably, in a way that aggregates with other groups' actions into something that looks like a movement — is one of the most basic functions of coordination infrastructure. It's also one of the easiest to build.

The goal isn't a movement that acts because someone told it to. It's a movement that acts because the infrastructure made it easy for autonomous groups to align — and because the people in those groups trusted each other enough to do it.