Executive Structures

Part of Institutional Design

Practical designs for the bodies that carry out community governance decisions day to day.

Why This Matters

Governance decisions must be implemented to mean anything. The council decides to build a granary; someone must actually coordinate the labor, source the materials, and get it built. The assembly agrees on a new water allocation policy; someone must track allocations, resolve conflicts at the source, and adjust when the situation changes. This implementation function — translating governance decisions into action — is the executive structure.

How the executive structure is designed determines whether governance translates into action efficiently or gets stuck in coordination failures, whether accountability is possible or diffuse, and whether the people doing the day-to-day work of implementation are empowered or frustrated.

Unlike legislative and judicial functions, which are primarily deliberative, executive function is primarily operational. The design challenges are different: how to get things done reliably, how to maintain accountability for ongoing operations rather than discrete decisions, and how to balance the need for coordination with the need for expertise in specific domains.

Basic Executive Organization

The coordinator-staff model: A single executive coordinator (by whatever title) oversees a set of domain staff responsible for specific functional areas. The coordinator integrates across domains, manages priorities, and is accountable for overall community operations. Domain staff are responsible for their specific areas and report to the coordinator.

This model works well for communities of 50-500 people. It provides clear accountability and integration while allowing domain expertise. It fails if the coordinator is a bottleneck for domain decisions that should be made at the domain level, or if domains become siloed and fail to coordinate.

The council-as-executive model: The governing council is itself the executive body — council members collectively direct implementation rather than delegating to separate executives. All governance and executive authority is concentrated in the same body.

This model is appropriate for very small communities (under 50) where the same people must do everything. It becomes dysfunctional as the community grows because the council cannot govern and manage simultaneously; governance deliberations crowd out operational attention and vice versa.

The separated executive model: The executive branch is entirely separate from the legislative branch — different people, different selection processes, different authorities. The council makes decisions; the executive implements them. This separation creates clearer accountability and prevents confusion between governance and management.

This is appropriate for medium to large communities with enough people to staff both functions without the same individuals doing both. The challenge is ensuring adequate coordination between the two branches.

Functional Divisions

Regardless of the overall structure, some functional divisions are almost universal:

Food and resource management: Tracking food reserves, managing community stores, coordinating agricultural labor, administering trade. The most materially critical executive function; staffed by someone with genuine expertise in inventory and agricultural management.

Infrastructure and construction: Planning and executing construction and maintenance. Managing tools and equipment. Coordinating skilled labor for infrastructure work. Requires technical competence in the specific types of construction the community does.

Health administration: Coordinating medical services, managing medical supplies, administering sanitation and public health standards. Must be closely connected to the actual medical practitioners.

External relations: Managing relationships with other communities, trading relationships, external communications. Requires good judgment about community interests and communication skills.

Record-keeping and administration: Maintaining the community’s records, managing information flow, supporting governance processes. The administrative backbone that everything else depends on.

Staffing Executive Roles

Selection criteria: Executive staff need different skills than council members. Prioritize proven operational competence — people who have actually managed complex tasks successfully — over political skills or community popularity. The granary manager must be able to manage a granary; their popularity is secondary.

Clear scope of authority: Each executive role must have a written description of what it includes and what it does not. “Manages food reserves” is incomplete — does this include making trade decisions? Allocating food to households? Adjusting planting plans? Ambiguity about authority leads to either paralysis (no one acts without consensus) or conflict (multiple people claim authority over the same decision).

Explicit decision limits: Define the threshold at which an executive staff member must escalate a decision to the coordinator or the council rather than deciding alone. Below-threshold decisions should be within their authority; above-threshold decisions require authorization.

Performance accountability: Define specific outcomes each executive role is responsible for. The food manager is accountable for caloric reserve levels, waste rates, and equitable distribution — not just for showing up and doing tasks. Performance is evaluated against these outcomes at regular intervals.

Coordination Mechanisms

Multiple executive functions must coordinate or they work at cross-purposes. Standard coordination mechanisms:

Regular executive meetings: The full executive team meets regularly — weekly for most operational contexts — to share information, surface coordination problems, and make joint decisions on cross-functional matters.

Information sharing requirements: Each domain must make relevant information available to other domains. The food manager’s inventory data informs the trade decisions of the external relations role; the health administrator’s demand projections inform food reserve calculations. Information sharing should be a specified requirement, not a voluntary practice.

Escalation procedures: When a cross-functional issue cannot be resolved at the executive level, define how it escalates. Who decides if there is a conflict between the infrastructure executive’s construction timeline and the agricultural executive’s labor requirements during harvest? Clear escalation paths prevent gridlock.