How distributed solar eliminates the need for most power plants

1. The Architecture of Coordination

Coordination requires several elements: Shared direction: Not identical beliefs, but enough alignment on what matters and what the collective is trying to accomplish that people understand how their work contributes to the whole. Different people will have different beliefs about why the direction matters, but they align enough on what the direction is. Clarity about roles and authorities: Who does what? What decisions are distributed? What decisions are coordinated? Which people are responsible for which functions? Without this clarity, people either step on each other or leave gaps that no one fills. Communication about progress: Who is doing what? Are there obstacles? Are we moving toward our shared direction? This communication prevents people from working in isolation, disconnected from what others are doing. Feedback loops: Are we actually moving toward what matters? Do we need to adjust direction? Are there emerging problems? Feedback allows the collective to learn and adapt together rather than discovering months later that things have drifted in the wrong direction. Rhythm and synchronization: Even distributed work needs moments of synchronization where people align, check in, recalibrate. Collectives that have no rhythm of synchronization fragment because people diverge. Without these elements, you have people working in the same collective doing different things with no alignment. With them, you have coordination that allows people to maintain autonomy while multiplying collective power.

2. The Problem of Over-Coordination

Too much coordination is also a problem. When every decision requires full group alignment, when every person needs permission from the group to act, the collective becomes paralyzed. Over-coordination creates bottlenecks. Everything flows through the same approval process. The collective can only move as fast as the slowest decision-maker. Responsive action becomes impossible. Over-coordination also creates resentment. People feel controlled. They feel that their autonomy is not respected. Even if the coordination process is technically democratic, it feels oppressive because every action requires permission. The goal is not maximum coordination. It is optimal coordination. Some decisions should be made by individuals or small teams without collective approval. Some should be made by the collective. Some should be made by designated people with delegated authority. Getting this right is what allows the collective to both maintain coherence and move fast enough to accomplish things.

3. Shared Direction Without Enforced Belief

Shared direction is not the same as shared belief. It is not even the same as shared strategy. It is alignment on what matters enough that people want to move in that direction. A healthcare cooperative might be coordinated around "accessible healthcare for everyone." Some members believe this because they are socialists who want universal provision. Others believe it because they are pragmatists who see that prevention is cheaper than emergency care. Others believe it because they are spiritual practitioners who see healthcare as service. These are different beliefs motivating the same direction. This is different from false coordination where people agree on the goal but have fundamentally different visions of what it means. That kind of hidden misalignment surfaces later when resources have to be allocated or difficult choices need to be made. Creating shared direction without enforced belief means: Articulating what actually matters: Not vague values but concrete commitments. "Accessible healthcare for everyone" is more concrete than "serving humanity." The more concrete the direction, the less room for later misalignment. Checking whether the direction makes sense with diversity: Can socialists and pragmatists and spiritual practitioners genuinely move together on this direction? What would create tension? The tensions that surface now can be addressed. The tensions that surface later destroy the collective. Distinguishing between shared direction and shared belief: People don't have to believe the same things. They do need to be moving toward the same concrete direction. If someone's belief system actually prevents them from moving in that direction, that is a fundamental misalignment. If their belief system can coexist with the direction, the difference doesn't matter.

4. Role Clarity as Coordination

Most collectives are vague about who is responsible for what. They have task lists but not clear ownership. They have meetings but not clear decision authority. They have projects but not clear leadership. This vagueness produces several problems: Duplication: Multiple people doing the same work because they each thought it was their responsibility. Omission: Nobody doing necessary work because everyone thought someone else was doing it. Resentment: People feeling like they are carrying more than others because they don't know what others are doing. Lack of accountability: If nobody is clear about who is responsible, nobody can be held accountable when something doesn't happen. Clear role definition solves these problems. It means: Functional clarity: This role includes these responsibilities. These responsibilities do not include that. Authority clarity: This role has authority to make these decisions without approval from others. Delegation clarity: This role can delegate to others and retain responsibility, or must retain responsibility? Accountability clarity: Who is this role accountable to? What does accountability mean? What happens if this role is not fulfilled? Without role clarity, collectives become bogged down in repeated discussions of who is responsible for what. With it, people know where they fit, what is expected, and what authority they have.

5. Communication Loops as Coordination

Coordination breaks down when people are not communicating about what they are doing. The left hand does not know what the right hand is doing. People make conflicting decisions because they did not know others were working on related issues. Good coordination requires communication loops where information flows about: What each person/team is working on: Regular updates so people can understand how their work relates to others'. Obstacles and needs: When someone is stuck or needs something from another person/team, that is communicated clearly rather than bottlenecked internally. Progress toward shared direction: Are we moving toward what matters? What is actually happening? Emerging conflicts: When people's work is in tension or when someone is going in a different direction, that is surfaced so it can be addressed quickly rather than allowing misalignment to compound. These communication loops do not need to be constant. But they do need to be regular enough that serious misalignment does not accumulate. Weekly check-ins in a small team. Monthly in a larger collective. The frequency depends on the pace of change.

6. Decision Distribution as Coordination

Not all decisions should be made by the whole collective. Coordination requires clarity about what level of decisions require what level of input. Types of decisions: Autonomous decisions: Individual or small team decides without checking with others. These are typically decisions that do not affect others' work. Consulting decisions: The person decides but solicits input from relevant stakeholders first. Coordinated decisions: Multiple parties affected by the decision collaborate on it. Consensus decisions: The whole collective decides together. These should be rare because they are slow. Distributed decisions: Designated people with delegated authority decide on behalf of the collective. Most collectives perform poorly because they treat all decisions as consensus decisions or they treat all decisions as autonomous. The reality is that different decisions require different processes. Getting this right is critical. The collective should decide things that affect the whole (values, major direction, resource allocation). Small groups should decide things that affect them. Individuals should decide things that only affect their work. This clarity prevents both gridlock and rogue action.

7. Feedback as Coordination

Feedback loops are what allow the collective to learn and adapt. Without them, the collective cannot correct course when something is not working. Good feedback includes: Transparent metrics: What are we actually measuring? Are we moving toward our goals? What is the evidence? Regular review: Not constant review but regular moments where the collective steps back and asks: Is this working? Psychological safety: People need to be able to report problems and suggest changes without being blamed or dismissed. Responsiveness: When feedback indicates a problem, the collective actually does something about it rather than just noting it and moving on. Feedback systems are often missing in collectives, especially when there is ideological commitment to the work. People assume that if everyone is committed, things will work out. But commitment is not enough. You also need information about what is actually working and what is not.

8. The Problem of Hidden Disagreement

The worst coordination failures are not conflicts that are out in the open. They are disagreements that people hide because they assume everyone should be unified. Someone disagrees with the direction but does not say so because she thinks it would be disloyal. Someone believes the strategy is wrong but goes along because she doesn't want to rock the boat. Someone has crucial information that conflicts with the group narrative but doesn't share it because he is afraid of how it will be received. These hidden disagreements eventually surface, usually at the worst moment. Or they never surface and the collective slowly dies because it is not adaptive. Good coordination requires creating safety for disagreement. It means: Explicitly inviting dissent: "If you see problems with this direction, I want to hear them." Distinguishing between disagreement and disloyalty: You can disagree with a direction and still be committed to the collective. Creating decision points where disagreement can surface: "Before we commit to this, are there serious concerns?" Taking disagreement seriously: When someone disagrees, it is an opportunity to learn something, not an attack to defend against. The collective that can hear and integrate disagreement is more adaptive and more coherent than one that suppresses it. The unified front that is actually unified disagreement creates brittleness. The collective that can surface disagreement and work with it is more resilient.

9. Coordination Across Difference

One reason collectives fragment is that they cannot hold genuine difference. They either demand sameness or they fragment into separate camps that barely coordinate. Real coordination across difference means: Respecting different approaches: If someone has a different way of doing something that produces results, their approach is respected rather than suppressed. Creating space for different people: Some people work fast and loose. Others are detail-oriented. Some are big-picture thinkers. Others are implementers. Coordination does not require that everyone work the same way. Building on different strengths: The collective does not ask everyone to be good at everything. It asks people to develop their strengths and coordinate their complementary gifts. Addressing real incompatibilities: If someone's approach actually prevents coordination or contradicts shared values, that is addressed directly. But many differences that feel like incompatibilities are actually complementary. The collective that can coordinate across genuine difference is far more powerful than one that demands conformity. It attracts more people, it adapts better, it generates more creative solutions.

10. Rhythm and Synchronization

Even distributed work needs moments when everyone comes together. Without these moments, people diverge and coordination breaks down. Synchronization moments might include: Regular meetings: Where the collective checks in together. Joint projects: Where the whole collective works on something together. Celebrations or rituals: Where the collective gathers to mark progress or recommit to purpose. Decision points: Where the collective pauses and aligns before moving forward. The frequency and nature of synchronization depends on the scale of the collective and the pace of change. A small tight-knit collective might synchronize weekly. A large distributed network might synchronize quarterly. The point is that synchronization happens regularly enough that people do not diverge so far that coordination becomes difficult.

11. Coordination and Accountability

Coordination requires accountability. If people are working toward shared direction but nobody is accountable for results, the work drifts. Accountability means: Clear expectations: What is this role/team/person accountable for? Regular reporting: How often do we check on whether expectations are being met? Consequences for non-accountability: What happens if someone is not meeting expectations? Can they be supported to improve? Are they released from the role? Is the expectation changed? Support for success: Accountability is not punishment. It is providing what people need to succeed and then holding them to standards. Without accountability, coordination becomes fantasy. With it, coordination works.

12. The Integration of Coordination

The mature expression of coordination amplification is alignment that is neither rigid nor loose. It is tight enough that collective effort compounds rather than cancels. It is loose enough that people maintain autonomy and can adapt to changing circumstances. It is a dynamic balance that requires constant attention and adjustment. This kind of coordination allows collectives to function at scale. It allows groups to grow beyond informal consensus. It allows different people with different gifts to work together. It is the foundation of all movements that actually accomplish change.