Role-Based Authority in Holacracy: A Fundamental Paradigm Shift

Role-based authority is the foundation of Holacracy and marks the most radical break from traditional organizational forms. Instead of power emanating from people, titles, or positions, authority emerges from clearly defined roles. This sounds like a small difference – in reality, it changes everything.

At SI Labs, we have practiced role-based authority for over ten years. We have experienced how people who previously had to wait for approvals suddenly act independently. We have seen how conflicts that used to escalate to supervisors dissolve when it’s clear who has which authority. And we have learned that the transition from person-based to role-based authority is one of the most challenging steps in Holacracy implementation.

What Is Role-Based Authority?

In traditional organizations, we ask: “Who is the boss here?” The answer determines who may decide. Authority is tied to people, to their position in the hierarchy, to their relationship with other power holders.

In Holacracy, we ask: “Which role has the authority for this decision?” The answer determines who may act – regardless of who the person is that currently fills that role. This system is organized in circles and coordinated through the Lead Link.

The core difference:

Traditional	Role-Based
Authority belongs to the person	Authority belongs to the role
”Maria may decide this"	"The Marketing role may decide this”
Power through position	Power through function
Hierarchy of people	Holarchy of roles

Research Insight: A study of 81 start-ups shows that unclear authority distribution is one of the most common reasons for organizational dysfunction. Flat hierarchies without clear authority assignment paradoxically often lead to more power concentration with informal leaders. [1]

From Job Titles to Roles: The Fundamental Difference

A job title describes a person: “Maria is the Marketing Manager.” The title implies a range of responsibilities that are rarely explicitly defined. What exactly may Maria decide? Where are her limits? This often remains unclear.

A role describes a function: “The Marketing role has the accountability to develop brand presence in social media, and the domain over marketing budget up to 5,000 EUR.” The definition is explicit, regardless of who fills this role.

Job Title Problems

1. Implicit Expectations

“Marketing Manager” means something different to everyone. The CEO expects strategic planning, the Sales Lead expects lead generation, the Product team expects product communication. Maria cannot meet all expectations because they were never explicitly defined.

2. Person-Bound Knowledge

When Maria leaves the company, the knowledge of what she actually did leaves with her. The successor must reinvent the role.

3. Status-Based Conflicts

Two managers with similar titles argue about who is responsible. The solution requires escalation to a shared supervisor.

Role Advantages

1. Explicit Definition

The Marketing role has documented accountabilities. Everyone knows what is expected.

2. Transferable Knowledge

When Maria hands off the role, the accountabilities remain. The next person continues where Maria left off.

3. Authority-Based Clarity

Two roles don’t argue – they have different domains. If overlap exists, it’s clarified in governance.

The Three Elements: Purpose, Domain, Accountability

Every role in Holacracy consists of three elements that together define its authority. For a detailed guide on defining these elements, see our article Defining Roles in Holacracy.

Purpose

The purpose describes WHY the role exists. It provides orientation for decisions when accountabilities aren’t sufficient.

Example: “Strengthen brand presence and build trust with potential customers”

Domain

Domains describe WHAT the role exclusively controls. Others may not intervene in this area without permission.

Example: “Marketing budget up to 5,000 EUR” – no one else may spend this budget.

Accountabilities

Accountabilities describe WHAT the role does. They are ongoing activities that the role responsibly performs.

Example: “Publishing posts on LinkedIn” or “Creating quarterly marketing analysis”

Research Insight: Research on self-organized teams shows that explicit role definitions with clear accountabilities significantly contribute to team effectiveness. Teams with clearly defined roles report less role ambiguity and higher satisfaction. [2]

Authority Comes from the Role, Not the Person

This is the paradigm shift that is hardest to internalize: Authority is not tied to the person.

What This Means Practically

Scenario 1: The New Employee

Thomas has been with the company for two weeks. He takes on the “Event Coordination” role with the domain “External events up to 10,000 EUR budget.” Thomas may book events, sign contracts, and spend budget from day one – not because he has experience, but because the role has this authority.

In a traditional organization, Thomas would first “learn,” then act “with consultation,” then eventually “independently.” This implicit development would take years and never be clearly defined.

Scenario 2: The Experienced Executive

Sabine was CEO for 15 years. She moves into a role in the Marketing circle. Her authority in marketing matters: exactly that of her role. Her CEO experience gives her no special rights in the Marketing circle.

This can be hard for people with long leadership experience. But it’s also liberating: Sabine no longer has to carry all decisions.

The Separation of Person and Role

In meetings, we consciously distinguish:

• “Speaking as the Marketing role…” vs. “Personally, I think…”
• “The role has the authority…” vs. “I would wish…”

This separation reduces personal conflicts. When I say “The Marketing role has no accountability for events,” I’m not criticizing the person but stating an organizational reality.

Multi-Role Reality: One Person, Many Roles

In traditional organizations, one person has one job. In Holacracy, one person typically fills multiple roles.

Why Multi-Roles?

1. Resource Efficiency

Small and medium organizations don’t have a full-time person for every function. Multi-roles enable the same people to fulfill various functions.

2. Expertise Utilization

One person can have expertise in various areas. Multi-roles enable using this diversity.

3. Flexibility

Roles can easily be transferred when workload changes.

Practical Implications

Switching Role Hats

Maria has three roles: Marketing, Recruiting, Event Planning. In a tactical meeting, she might be addressed in all three roles. She then consciously switches “hats”:

• “As the Marketing role, I need the briefing by Friday.”
• “As the Recruiting role, I have a tension: The job posting hasn’t been approved yet.”

Prioritizing Between Roles

When Maria has more work in her three roles than time, she must prioritize. This isn’t a personal decision – the Lead Link of her circle can set priorities between roles. More on this under Multi-Roles in Holacracy.

Research Insight: Harvard Business Review reports that self-organized teams often tend toward multi-role structures, increasing both flexibility and complexity. Successful implementations are characterized by clear mechanisms for prioritizing between roles. [3]

Multi-Role Limits

How many roles are realistic?

• 1-3 roles: Easily manageable
• 4-6 roles: Works, requires good organization
• 7+ roles: Warning sign – possibly too fragmented

When someone has very many roles, it’s often a sign that roles should be consolidated or transferred to others.

Authority Without Hierarchy: How It Works

“But who decides then?” – we hear this question often. The answer: The roles decide, in their domains.

The Authority Principle

In Holacracy: Every role has full authority to act in its area. No other role – not even the Lead Link – can overrule a role in matters of its domain.

Example:

The “Website” role has the domain “Website content.” The CEO personally cannot instruct to publish a specific text. They can communicate a wish to the role, but the final decision lies with the role.

But Isn’t This Anarchy?

No. The authority boundaries are clearly defined:

1. Within the domain: Full authority
2. Outside the domain: No authority without permission
3. With overlap: Governance clarifies the boundaries
4. With tensions: IDM process resolves the problem

The Holacracy Constitution creates a clear framework that regulates how authority is defined, changed, and handled in conflicts. More on this in The Holacracy Constitution Explained.

Authority Flow in the Holarchy

Holacracy isn’t flat – it’s holarchic. Circles contain sub-circles, which contain sub-circles. Authority flows:

From outside in: The super-circle defines the purpose and accountabilities of a sub-circle. Within these boundaries, the sub-circle is autonomous.

From inside out: Via Rep Links, sub-circles carry tensions outward that they cannot resolve internally.

Horizontally: Cross Links connect circles that need to coordinate.

This structure enables both autonomy (within defined boundaries) and coherence (through the overarching purpose).

The Limits of Role-Based Authority

Role-based authority doesn’t solve all problems. Knowing its limits is important.

Where Role-Based Authority Fails

1. Insufficient Role Definition

When roles are vaguely defined, confusion arises. “The Marketing role is responsible for marketing” helps no one.

Solution: Define precise accountabilities and domains. This is hard work, but necessary.

2. Role Gaps

Sometimes work falls into no role. No one feels responsible.

Solution: Process tensions. When someone notices “No one’s doing this,” they bring a governance tension and develop a proposal for the next governance meeting.

3. Personal Competence

Role-based authority says nothing about competence. A person can have a role and still not know how to fill it.

Solution: Lead Links assign roles thoughtfully. Training and mentoring support role holders.

4. Cultural Inertia

People who worked in hierarchies for years fall into old patterns. They ask the boss instead of deciding themselves.

Solution: Continuous coaching. Patience. Cultural change takes time.

Research Insight: Studies show that the transition to self-organized structures typically takes 2-4 years until new behavior patterns become the norm. Cultural transformation is more demanding than structural change. [4]

What Role-Based Authority Doesn’t Replace

1. Professional Expertise

The role gives authority, not knowledge. A new employee in a technical role still needs onboarding.

2. Personal Relationships

Holacracy structures work, not relationships. Collegiality, trust, and appreciation still arise between people, not between roles.

3. Strategic Leadership

Even with distributed authority, an organization needs vision and direction. The Lead Link of the Anchor Circle often carries this responsibility.

The Transition: From Person-Based to Role-Based Authority

The switch to role-based authority isn’t a project but a transformation.

Phase 1: Awareness (Weeks 1-4)

People understand intellectually what role-based authority means. Training and workshops create this understanding.

Typical challenge: “This sounds good in theory, but will it work for us?”

Answer: Practical exercises, simulations, examples from other organizations.

Phase 2: First Application (Months 1-3)

Roles are defined. First governance meetings take place. People begin speaking “as a role.”

Typical challenge: Old habits. People continue asking the boss.

Answer: Consistent redirecting. “What does your role say about this?” “Do you have the authority for that?”

Phase 3: Integration (Months 3-12)

Role-based thinking becomes habit. Governance becomes routine. Tensions are naturally processed.

Typical challenge: Relapses under stress. Under time pressure, hierarchy returns.

Answer: Persist. After the stress, reflect: “Why did we fall into old patterns?”

Phase 4: Mastery (Year 1+)

The organization thinks in roles. New employees are socialized into this thinking. Role-based authority is the norm.

Role-Based Authority at SI Labs

Our experiences over ten years:

What Works

Clarity creates speed. When everyone knows who has authority, decisions are made faster. No waiting for approvals, no checking upward.

Multi-roles enable flexibility. During project peaks, roles can be temporarily transferred. With personnel changes, roles remain stable, only the assignment changes.

Conflicts are resolved structurally. Instead of personal power struggles, we have governance processes. “Your role has this domain, mine has that one” – this can be clarified.

What Remains Difficult

The cultural shift takes time. Even after ten years, there are moments when someone forgets that authority lies with the role, not the person.

New employees need time. Those coming from traditional structures must unlearn. The first six months are often disorienting.

Role maintenance requires discipline. Roles must be kept current. Outdated role definitions create exactly the confusion we want to avoid.

Our Recommendation

Start with clear roles for the most important functions. Don’t perfect – iterate. Governance is a continuous process, not a one-time definition.

---

Research Methodology

This article is based on analysis of 43 academic papers on Organizational Design (theme cluster T04) and 33 papers on Agility & Hierarchy (T05), supplemented by over ten years of practical experience with role-based authority at SI Labs.

Source selection:

• Empirical studies on start-up structures and flat hierarchies
• Case studies on Holacracy implementations
• Theoretical work on distributed authority and self-organization

Limitations: As a practicing Holacracy organization, we have an insider perspective that shapes our analysis. We have tried to balance this with external research findings.

---

Disclosure

SI Labs GmbH has practiced Holacracy for over ten years. We have a business interest in Holacracy being perceived as a viable alternative to traditional structures. This perspective shapes our presentation.

---

Sources

[1] Kirtley, Jacqueline, and Siobhan O’Mahony. “The myth of the flat start‐up: Reconsidering the organizational structure of start‐ups.” Strategic Management Journal 44, no. 7 (2023): 1669-1702. DOI: 10.1002/smj.3333 [Empirical Study | 81 Start-ups | Citations: 81 | Quality: 78/100]

[2] Romme, A. Georges L., and Jan Stoker. “How to get better at flatter designs.” Journal of Organization Design 11 (2022): 5-14. DOI: 10.1007/s41469-022-00109-7 [Conceptual Analysis | N/A | Citations: 24 | Quality: 68/100]

[3] Bernstein, Ethan, et al. “Beyond the Holacracy Hype: The Overwrought Claims and Actual Promise of the Next Generation of Self-Managed Teams.” Harvard Business Review 94, no. 7/8 (2016): 38-49. [HBR Practice Article | Multiple Case Studies | Citations: 312 | Quality: 72/100]

[4] Hashim, Amal, et al. “Holacracy and Hierarchy Concepts: Which One is More Effective in an Organizational Leadership and Management System?” Malaysian Journal of Social Sciences and Humanities 5, no. 12 (2020): 117-130. DOI: 10.47405/mjssh.v5i12.600 [Literature Review | N/A | Citations: 8 | Quality: 52/100]

[5] Robertson, Brian J. “Holacracy.” In The Management Shift, edited by Vlatka Hlupic, 145-168. Chichester: Wiley, 2012. DOI: 10.1002/9781119197683.ch9 [Book Chapter | N/A | Citations: N/A | Quality: 60/100]