Decision Making

Structuring how community decisions are made — who decides what, through which process, with what documentation — to ensure decisions are both good and legitimate.

Why This Matters

Every community makes decisions constantly. Some are made well: deliberate, informed, with input from relevant stakeholders, leading to clear outcomes that everyone understands and accepts. Others are made poorly: rushed, based on incomplete information, by whoever happened to be present, leaving half the community unaware that a decision was made and others disputing its legitimacy.

The difference between these outcomes is not luck or the wisdom of individual leaders. It is structure. Communities with clear decision-making structures — defined processes for different types of decisions, clear roles for who participates in what, documented outcomes that are communicated to all — consistently make better decisions than communities where decisions emerge from improvised discussion among whoever is present.

Structure does not mean bureaucracy or slowness. It means knowing in advance what process applies to which decisions, so that when a decision is needed, no time is wasted figuring out how to make it. A community that has defined its decision processes can make routine decisions in minutes and complex decisions in a structured way that produces durable outcomes.

Categorizing Decisions

Different decisions warrant different processes. Applying the full community consensus process to what color to paint the meeting room is wasteful. Applying a single leader’s unilateral judgment to a decision about rationing food reserves is dangerous.

Categorize decisions by stakes and reversibility:

Routine administrative decisions (low stakes, easily reversible): handled by designated role-holders without consultation. The resource manager decides how to organize the grain store. The labor coordinator assigns who covers a vacancy on the water crew. Fast, no deliberation required.

Significant operational decisions (moderate stakes, moderately reversible): handled by the council with consultation of affected parties. Adjusting rationing allocations for a season. Assigning a community member to a new role. Approving a construction plan. Council deliberation, community notification, documented outcome.

Major policy decisions (high stakes, difficult to reverse): require community assembly input before council vote or full assembly vote. Establishing a new community rule. Entering a significant trade agreement. Accepting or expelling members. Requiring broader participation ensures legitimacy.

Constitutional decisions (highest stakes, very difficult to reverse): changes to fundamental community rules, governance structure, or identity require supermajority approval. Changing from consensus-based to majority-vote governance. Merging with another community. Establishing a new territory or leaving current territory.

For each category, define: who makes the decision, what process is followed, who is consulted, how the decision is documented, and how it is communicated. Write these definitions into your community charter. Having the category definitions available means no time is wasted in the moment debating what process applies.

Information-Gathering Before Deciding

Good decisions require relevant information. Before any significant or major decision, assign someone responsible for gathering the necessary information and presenting it in the decision meeting.

Information to gather typically includes:

  • What is the current situation? (Facts, not interpretations)
  • What are the options being considered?
  • For each option: what are the resource requirements? What are the likely consequences? What has been tried before?
  • Who is affected by the decision and what are their interests and concerns?
  • Is there relevant expertise in the community that should be consulted?

A brief written summary of this information, presented at the start of the decision discussion, dramatically improves decision quality. Without it, discussions devolve into competing assertions of fact, speculation about consequences, and arguments about options that are not actually available.

Assign information gathering in advance of the meeting, not at the meeting. “We need to decide about the water cistern next week — please gather information on current water supply, options for cistern construction, and material requirements” allows someone to do the research and present findings, rather than having everyone guess together in the meeting room.

The Decision Meeting

A decision meeting has a structure. Deviating from it under time pressure is a common failure mode.

Open with the framing question: state precisely what decision is being made. “We are deciding whether to begin cistern construction this autumn or defer to next spring.”

Present information: the person who gathered information presents it. Questions for clarification only — not debate yet.

Discussion: explore options, raise concerns, identify constraints. The facilitator ensures all relevant voices are heard. Set a time limit for open discussion. When the time limit approaches, check whether new information is still emerging or whether the discussion is cycling — if cycling, move forward.

Identify convergence: the facilitator summarizes the apparent direction of the discussion. “I’m hearing that most people favor Option A, with some concern about the timing. Does that capture where we are?”

Address remaining objections: give objectors a last chance to state their specific concern. The group addresses the concern explicitly: change the proposal to address it, explain why it cannot be addressed, or acknowledge the risk as unavoidable.

Make the decision: through whichever process applies (consensus check, vote, leader decision). State the decision clearly.

Assign implementation: name who is responsible for acting on the decision and by when. A decision without an assigned owner and deadline is rarely implemented.

Document and communicate: record the decision immediately. Communicate it to those who were not present.

Documenting and Communicating Decisions

Every significant decision should be documented in a decisions register — a chronological log of community decisions. Each entry includes:

  • Date of decision
  • Summary of the decision (one sentence)
  • Process used to make it
  • Who participated
  • Any dissenting concerns that were overridden
  • Who is responsible for implementation
  • Implementation deadline

This record serves multiple purposes: new community members can understand why current rules exist; disputes about whether a decision was made can be resolved by checking the register; patterns in decision-making can be reviewed; and accountability for implementation can be tracked.

Communicate every significant decision to the full community, not just to those who attended the decision meeting. Post decisions on the notice board. Announce them at the next community gathering. Inform household heads who will relay information to their households. Decisions that are not communicated are not effective — people cannot comply with or act on decisions they do not know about.