Adaptive governance
~5 min read
Core Primitive
Governance structures that can evolve as the organization grows and changes.
Most organizational governance is static — designed once and changed only through major reorganization efforts. Adaptive governance is governance that includes its own mechanisms for evolution: regular review, experimentation with governance alternatives, and the ability to modify governance structures without requiring a governance crisis. The organization that can change how it governs itself has the meta-capability required for genuine sovereignty — it is not bound by inherited structures but can consciously design and redesign the structures through which it operates.
The governance paradox
Governance exists to provide structure — to define how decisions are made, who has authority, how resources are allocated, and how conflicts are resolved. Good governance enables the organization to function reliably and predictably. But reliability and predictability, taken to their extreme, become rigidity — and rigidity prevents the organization from adapting to changing circumstances.
This is the governance paradox: the structures that enable organizational functioning also constrain organizational evolution. An approval process that prevents reckless spending also prevents rapid response to opportunities. A reporting structure that ensures accountability also creates communication bottlenecks. A meeting cadence that ensures coordination also consumes the time needed for focused work.
Brian Robertson, the creator of Holacracy, identified this paradox as the central problem of organizational design. Traditional organizations resolve the paradox periodically — through reorganizations that disrupt existing structures and replace them with new ones. Adaptive organizations resolve the paradox continuously — through governance processes that evolve incrementally in response to organizational learning (Robertson, 2015).
What makes governance adaptive
Adaptive governance has four properties that distinguish it from static governance.
Built-in review mechanisms
Static governance is reviewed only when it breaks. Adaptive governance includes regular, scheduled reviews of governance effectiveness — not waiting for failure but proactively examining whether each governance mechanism is still serving its purpose. The review cadence should be proportional to the rate of organizational change: faster-changing organizations need more frequent governance review.
Experimental capacity
Adaptive governance can be tested before it is committed. Rather than redesigning governance structures through deliberation and then implementing the redesign permanently, adaptive governance uses the pilot methodology (Pilot programs as system experiments): test the governance change in a bounded context, measure its effects, and decide whether to expand, modify, or revert.
Incremental evolution
Adaptive governance changes incrementally — modifying one mechanism at a time rather than redesigning the entire governance structure simultaneously. Incremental change is less disruptive, easier to evaluate, and lower risk than comprehensive redesign. If an incremental change fails, its effects are contained; if a comprehensive redesign fails, its effects are organizational.
Constitutional authority
The organization must have the explicit authority to modify its own governance. This seems obvious but is often absent: many governance structures are treated as untouchable — established by founders, inherited from previous leadership, or mandated by external authorities. Adaptive governance requires that the organization explicitly claims the authority to modify its own structures — subject to legal and regulatory constraints but not constrained by tradition or inertia.
The governance review protocol
A practical protocol for adaptive governance review follows six steps.
Step 1: Inventory. List the governance mechanisms currently in operation — approval processes, meeting cadences, reporting structures, decision rights, resource allocation methods, escalation protocols. Most organizations have more governance mechanisms than they realize, accumulated over years of adding without removing.
Step 2: Purpose identification. For each mechanism, identify the organizational purpose it serves. What problem does this meeting solve? What risk does this approval process mitigate? What coordination need does this reporting structure address? If no one can articulate the purpose, the mechanism is a candidate for elimination.
Step 3: Effectiveness assessment. For each mechanism, assess whether it is still serving its purpose effectively. Has the organizational context changed? Has the problem the mechanism was designed to solve been resolved by other means? Is the mechanism producing the coordination, accountability, or risk mitigation it was designed to produce?
Step 4: Cost assessment. For each mechanism, estimate the costs: time consumed, decisions delayed, flexibility reduced, people frustrated, attention diverted. Governance mechanisms that serve a genuine purpose but at excessive cost are candidates for redesign. Mechanisms whose costs exceed their benefits are candidates for elimination.
Step 5: Alternative design. For mechanisms that are ineffective or excessively costly, design alternatives. Draw on the sovereignty mechanisms described in this phase: can the approval process be replaced with consent-based decision-making? Can the reporting structure be replaced with transparent dashboards (Transparency as organizational infrastructure)? Can the meeting cadence be replaced with asynchronous coordination?
Step 6: Pilot and evaluate. Implement the alternative as a time-bounded pilot. Define the metrics that will determine whether the alternative is better than the current mechanism. Run the pilot for a defined duration. Evaluate the results. Decide: retain, modify, or revert.
Governance at different scales
Adaptive governance operates differently at different organizational scales.
Team governance (5-15 people) is the most fluid — teams can modify their internal governance quickly, with immediate feedback on the effects. Team-level governance includes standup formats, code review processes, task allocation methods, and communication norms. These should evolve weekly or bi-weekly based on the team's retrospectives (Organizational retrospectives).
Department governance (50-200 people) requires more coordination — changes to departmental governance affect multiple teams and require broader consultation. Department-level governance includes resource allocation, priority-setting, hiring processes, and cross-team coordination mechanisms. These should evolve monthly or quarterly based on departmental retrospectives and performance data.
Organizational governance (200+ people) requires the most deliberation — changes to organizational governance affect everyone and must be carefully tested. Organizational-level governance includes strategic planning processes, executive decision-making, performance management, and cultural practices. These should evolve semi-annually or annually based on organizational retrospectives and strategic assessment.
The principle across all scales is the same: governance is a tool, not a monument. Tools are maintained, sharpened, and sometimes replaced when they no longer serve their purpose.
The Third Brain
Your AI system can serve as a governance analysis tool. Describe a governance mechanism (a meeting, a process, an approval chain) and ask: "Analyze this governance mechanism: (1) What organizational purpose does it serve? (2) What evidence suggests it is or is not serving that purpose effectively? (3) What are its costs (time, delay, flexibility, frustration)? (4) What three alternative mechanisms could serve the same purpose? For each alternative, what are its advantages, risks, and implementation requirements?" This analysis provides the structured assessment that governance reviews require but rarely receive.
From adaptive governance to consent-based decisions
Adaptive governance provides the framework for evolving organizational structures. One of the most powerful governance innovations is consent-based decision-making — a process that enables faster, more adaptable decisions than traditional consensus while maintaining broader participation than top-down authority. The next lesson, Consent-based decision-making, examines this approach.
Sources:
- Robertson, B. J. (2015). Holacracy: The New Management System for a Rapidly Changing World. Henry Holt and Company.
Put it into practice
Exercise
Select one governance mechanism in your organization — an approval process, a meeting cadence, a reporting structure, a resource allocation method — and evaluate it using four questions: (1) What purpose does this mechanism serve? What organizational need does it address? (2) Is it still serving that purpose effectively? Has the organizational context changed since this mechanism was designed? (3) What are the costs of this mechanism — time consumed, decisions delayed, flexibility reduced, people frustrated? (4) What alternative mechanism could serve the same purpose with lower cost? Design the alternative as a time-bounded pilot: implement it for one month, measure the difference, and decide whether to retain, modify, or revert. This is adaptive governance in practice — conscious, evidence-based evolution of organizational structure.
More on putting it into practice
See it in action
A mid-size technology company, Helix, found that its governance structure — traditional executive committee, functional department heads, project-level managers — was becoming a bottleneck as the company scaled from 200 to 600 people. Rather than redesigning the entire governance structure at once (the typical reorganization approach), they adopted an adaptive governance practice. Every six months, they reviewed one aspect of their governance structure using three questions: Is this governance mechanism still serving its original purpose? Has the organizational context changed in ways that make this mechanism less effective? What alternative governance approach would better serve the current context? In the first review, they examined their project approval process — a three-level approval chain that added an average of two weeks to project initiation. They replaced it with a consent-based process (Consent-based decision-making) where projects within defined parameters could proceed unless someone raised a substantiated objection. In the second review, they examined their resource allocation process — quarterly executive committee allocation that could not adapt to mid-quarter opportunities. They replaced it with a distributed allocation model where teams had discretionary budgets for small investments and only large commitments required executive review. Each governance evolution was treated as a pilot — tested for two cycles, measured against defined criteria, and either retained, modified, or reverted. Over three years, the company's governance structure evolved continuously — becoming more distributed, more responsive, and more aligned with the organization's needs — without ever experiencing the disruption of a major reorganization.
Watch for the failure mode
Governance rigidity — treating governance structures as permanent fixtures rather than evolving tools. Organizations often treat their governance structures — meeting cadences, approval processes, reporting lines, decision rights — as immutable features of the organizational landscape. The meeting exists because the meeting has always existed. The approval process persists because the approval process has always persisted. This rigidity becomes increasingly costly as the organization changes: governance structures designed for a 50-person startup constrain a 500-person growth company, and governance structures designed for stable markets paralyze organizations in volatile ones. The antidote is treating every governance mechanism as provisional — subject to regular review and deliberate evolution.
Make it stick
This lesson applies the systemic change framework from Systemic Change to the organization's own governance structures. The insight from systemic change is how organizations evolve applies recursively: the governance system itself must be subject to systemic change. The connection to organizational retrospectives is procedural: retrospectives identify governance dysfunctions, and adaptive governance provides the mechanism for addressing them. The connection to Organizations can become self-directing (self-directing organizations) is foundational: an organization that cannot modify its own governance structures is not truly self-directing — it is bound by inherited structures. Look forward to Consent-based decision-making, which examines consent-based decision-making — a specific governance innovation that replaces consensus with a faster, more adaptable decision-making process.
Practice
Design and Pilot a Governance Alternative in Notion
Map an existing governance mechanism, evaluate its effectiveness, and design a time-bounded pilot alternative. You'll document the four-question evaluation framework and create a pilot implementation plan with measurable outcomes.
- 1Open Notion and create a new page titled 'Governance Pilot: [Mechanism Name]'. Select one governance mechanism (approval process, meeting cadence, reporting structure, or resource allocation method) and document its current state by creating a process map using Notion's toggle lists or columns to show each step, decision point, and stakeholder involved.
- 2Add a database or table in Notion with four sections for the evaluation questions. In the first section, define the mechanism's original purpose and organizational need; in the second, assess whether context has changed since design; in the third, quantify costs (time, delays, frustration); in the fourth, describe an alternative mechanism that could serve the same purpose with lower cost.
- 3Create a 'Pilot Design' section in your Notion page using a template with fields for: pilot duration (one month), success metrics (3-5 specific measurements), implementation steps, and rollback criteria. Define exactly what data you'll collect during the pilot to compare against the current mechanism's performance.
- 4Build a linked Notion database for 'Daily Pilot Observations' where team members can log experiences, friction points, and outcomes during the month. Set up properties for date, observer name, incident type (positive/negative/neutral), and impact level to enable structured analysis at pilot conclusion.
- 5Schedule a pilot review meeting in your Notion page by creating a 'Decision Framework' section with three options (retain new mechanism, modify and extend pilot, or revert to original). Include specific thresholds for each decision based on your success metrics, ensuring the governance evolution itself follows an evidence-based process.