# Study Notes: Holacracy Constitution V5.0 ## Article 1: Organizational Structure ### 1.1 Role Definition A **Role** is a fundamental building block in Holacracy, representing a specific function or responsibility within the organization. A person filling a Role is called a **Role Lead**. A Role consists of: - **Purpose**: The capacity, potential, or goal the Role aims to achieve. - **Domains**: Assets, processes, or other resources the Role exclusively controls. - **Accountabilities**: Ongoing activities the Role manages to support its Purpose or other Roles. - **Policies**: Rules or constraints that govern the Role's authority. **Example**: A "Marketing Manager" Role might have: - **Purpose**: Increase brand awareness. - **Domains**: Control over the organization's social media accounts. - **Accountabilities**: Creating and executing marketing campaigns. --- ### 1.2 Responsibilities of Role Leads Role Leads are responsible for ensuring their Role's Purpose and Accountabilities are fulfilled. Key responsibilities include: #### 1.2.1 Processing Tensions - **Tensions**: Gaps between the current state and the ideal state of the Role's Purpose or Accountabilities. - Role Leads must identify and resolve these Tensions. Think of Tensions as opportunities for improvement rather than problems. #### 1.2.2 Processing Purpose & Accountabilities - Define **Next-Actions**: Immediate, actionable steps to move the Role forward. - Define **Projects**: Specific outcomes to work toward. #### 1.2.3 Breaking Down Projects - Regularly identify Next-Actions for each active Project. #### 1.2.4 Tracking Work - Maintain written lists of: - Projects - Next-Actions - Tensions to resolve - Regularly review and update these lists. #### 1.2.5 Executing Next-Actions - Prioritize and execute Next-Actions that add the most value to the organization. --- ### 1.3 Circles A **Circle** is a group of Roles and Policies organized around a common Purpose. Circles have their own **Governance** (Roles and Policies). #### 1.3.1 Breaking Down Roles - Every Role is a Circle internally, called a **Sub-Circle**. - The broader Circle containing it is the **Super-Circle**. Roles defined in the Constitution cannot be further broken down. #### 1.3.2 Delegating Domains - Circles can delegate Domains to their Roles. - The Circle retains the right to override Policies governing these Domains. Granting a Domain does not automatically include control over financial assets unless explicitly stated. #### 1.3.3 Anchor Circle - The **Anchor Circle** represents the entire organization. - It holds all authority and Domains of the organization and has no Super-Circle. #### 1.3.4 Linking Into Circles - Roles can link into other Circles if invited by a Policy. - Linked Roles become part of the Governance of the inviting Circle. #### 1.3.5 Facilitator & Secretary Roles - **Facilitator**: Ensures Circle governance aligns with the Constitution. - **Secretary**: Maintains Circle records and meeting outputs. Circles can add Accountabilities or Domains to these Roles but cannot change their Purpose. --- ### 1.4 Circle Leads A **Circle Lead** is the Role Lead of a Circle's internal Circle. They hold the overall Purpose and unassigned Accountabilities of the broader Role. #### 1.4.1 Assigning Roles - Circle Leads assign Roles within the Circle. - Assignments can be revoked or focused on specific contexts. #### 1.4.2 Covering Unfilled Roles - Circle Leads automatically act as Role Leads for unfilled Roles or Roles filled by non-Partners. #### 1.4.3 Defining Priorities & Strategies - Circle Leads resolve priority conflicts and define **Strategies** to guide prioritization. #### 1.4.4 Routing External References - Circle Leads can redirect external references to appropriate Roles within the Circle. #### 1.4.5 Amending the Circle Lead Role - Circles can add or remove Accountabilities and Domains from the Circle Lead Role. - Changes apply recursively to all Sub-Circles. --- ## Article 2: Rules of Cooperation ### 2.1 Duty of Transparency Partners must provide transparency to Role Leads upon request. This includes: - **Projects & Next-Actions**: Share what you're working on. - **Relative Priority**: Explain how tasks are prioritized. - **Projections**: Provide rough estimates for task completion. - **Checklist Items**: Verify recurring actions. - **Metrics**: Share relevant data collected. - **Progress Updates**: Summarize recent progress. - **Other Information**: Share readily available, non-harmful information. Transparency builds trust and ensures alignment across the organization. --- ### 2.2 Duty of Processing Partners must promptly process requests from Role Leads: - **Clarify Next Steps**: Define and communicate Next-Actions or explain delays. - **Accept or Decline Requests**: Evaluate and respond to requests for new Projects or Next-Actions. - **Impact Domains**: Allow or explain objections to requests impacting a Domain controlled by your Role. Ignoring requests or failing to communicate reasoning can disrupt organizational flow. --- ### 2.3 Duty of Prioritization Partners must prioritize their attention as follows: 1. **Processing**: Handle inbound messages before executing Next-Actions. 2. **Meetings**: Attend constitutionally-required meetings when requested. 3. **Circle Priorities**: Align work with official Circle Strategies and priorities. 4. **Deadlines**: Treat deadlines as prioritization guides, not mandates. Circle Leads or other authorized Roles can override prioritization rules. --- ### 2.4 Relational Agreements Partners may create **Relational Agreements** to define how they work together. These agreements: - Must focus on behaviors, not outcomes. - Cannot conflict with the Constitution. - Can be terminated by either party. **Example**: Two Partners agree to provide weekly feedback on each other's work. --- ## Article 3: Tactical Meetings ### 3.1 Attendance - Regular Tactical Meetings are scheduled by the Circle's Secretary. - Invitations are extended to all relevant Roles unless specified otherwise. --- ### 3.2 Meeting Process The default Tactical Meeting process includes: 1. **Check-in Round**: Participants share their current state. 2. **Checklist Review**: Verify completion of recurring actions. 3. **Metrics Review**: Share relevant metrics. 4. **Progress Updates**: Highlight recent progress. 5. **Build Agenda**: Participants add agenda items without discussion. 6. **Triage Items**: Process agenda items through requests and discussions. 7. **Closing Round**: Participants reflect on the meeting. Facilitators manage time to ensure all agenda items are addressed. Skipping steps in the process can lead to incomplete or unfocused meetings. **Example Agenda Item**: A Role Lead requests feedback on a draft marketing campaign during the Triage phase. --- ## Key Takeaways - **Roles** are the foundation of Holacracy, with clear Purposes, Domains, and Accountabilities. - **Circles** organize Roles and Policies around shared Purposes. - Partners have duties of **Transparency**, **Processing**, and **Prioritization** to ensure smooth collaboration. - **Tactical Meetings** provide a structured way to align and process work within Circles. Regularly review your Role's Purpose, Accountabilities, and Next-Actions to stay aligned with organizational goals.