Objection vs Concern: Understanding the Difference in Holacracy

The difference between objection and concern is one of the most misunderstood aspects of Holacracy. In traditional meetings, every opinion carries equal weight. In Holacracy, only what can prevent concrete harm to the organization counts. This distinction isn’t harsh—it’s liberating: it enables quick decisions without endless debates.

At SI Labs, we’ve heard thousands of objections over more than ten years of Holacracy practice. Most of them, upon closer examination, were concerns. That’s not a problem—it just requires clarity about what’s what.

What Is an Objection in Holacracy?

An objection is a pointer to concrete harm that a proposal would cause. The objection says: “If we do this, something bad will happen.” It’s not an opinion, not a preference, and not a suggestion for improvement.

An objection must be concrete. It describes a specific harm, not diffuse discomfort. “That won’t work” is not an objection. “That will cause customer inquiries to remain unanswered for 48 hours” is an objection.

An objection must be causal. The harm is caused by the proposal, not by its absence. If the harm existed before, it’s not an objection to the proposal but a separate tension.

An objection must be organization-focused. It affects the organization’s ability to fulfill its purpose. Personal preferences are not objections.

Research Insight: A study on self-organized teams shows that distinguishing between valid objections and mere concerns is a critical success factor for effective governance. Organizations that consistently apply this distinction achieve faster decision cycles. [1]

What Is a Concern?

A concern is a reaction that doesn’t describe concrete harm. It’s an opinion, a preference, discomfort, or a suggestion for improvement. Concerns aren’t unimportant—they just don’t belong in the objection round.

Typical concerns:

• “I’m not sure if that will work.”
• “I would have done it differently.”
• “That doesn’t feel right.”
• “Wouldn’t it be better if…?”

Concerns are valuable. They inform the proposer and can be shared in the reaction round. But they don’t block a proposal because they don’t point to concrete harm.

The Difference: Objection vs Concern

Dimension	Objection	Concern
Focus	Concrete harm	General discomfort
Phrasing	”This will cause X"	"I’m not convinced”
Effect	Blocks until integrated	Informs, doesn’t block
Place in process	Objection round (IDM Step 5)	Reaction round (Step 3)
Testing	Validated by facilitator	No validation needed
Consequence	Proposal is amended	Proposer can ignore

The core question: An objection answers: “Why will this proposal harm the organization?” A concern answers: “Why don’t you like this proposal?”

The 4 Validity Tests for Objections

The facilitator tests each objection against four criteria. All four must be met for the objection to be valid.

1. Harm Test: Does the objection describe concrete harm?

Question: “What concrete harm do you see?”

Valid: “This will cause two roles to have the same accountability and we’ll have conflicts.”

Invalid: “I don’t like it.” (No concrete harm described)

2. Causality Test: Is the harm caused by the proposal?

Question: “Does the proposal cause this harm, or does it already exist?”

Valid: “The proposal removes the accountability ‘contact customers’ from Sales, but no one else gets it. Customers won’t be contacted.”

Invalid: “We already have problems with customer communication.” (The harm already exists, independent of the proposal)

3. Novelty Test: Is the harm a new tension?

Question: “Does this proposal create a new problem, or does it not sufficiently address an existing one?”

A proposal doesn’t have to solve all problems. If the proposal doesn’t make things worse, it’s not a valid objection, even if the proposal isn’t perfect.

Valid: “The proposal creates a new domain overlap that didn’t exist before.”

Invalid: “The proposal doesn’t solve our fundamental team communication problem.” (That’s a separate tension)

4. Organization Test: Does the harm affect the organization?

Question: “Is this a risk for the organization or a personal preference?”

Valid: “This will extend our delivery times and lose customers.”

Invalid: “I personally find that confusing.” (Personal reaction, not organizational harm)

Research Insight: Research shows that about 80% of initially raised objections don’t meet all four criteria when systematically tested. Consistent application of validity testing significantly reduces meeting times. [2]

Examples: Valid Objections

Example 1: Domain Conflict

Proposal: “Marketing role gets the domain ‘website content.’”

Objection: “The Product role already has the domain ‘product descriptions on the website.’ This will lead to conflicts because both domains overlap.”

Testing:

• Harm: ✓ (domain conflict between two roles)
• Causality: ✓ (the proposal creates the overlap)
• Novelty: ✓ (the overlap didn’t exist before)
• Organization: ✓ (affects the role structure)

Result: Valid objection → Integration needed. For more on domain conflicts, see our guide on governance anti-patterns.

Example 2: Missing Capacity

Proposal: “Support role gets the accountability ‘respond to all tickets within 2 hours.’”

Objection: “We only have one person in Support. With our ticket volume, a 2-hour response time is physically impossible. This will cause Support to be permanently ‘failing.’”

Testing:

• Harm: ✓ (impossible expectation creates permanent failure)
• Causality: ✓ (the proposal defines the unrealistic expectation)
• Novelty: ✓ (the current accountability has no time requirement)
• Organization: ✓ (affects the role’s ability to function)

Result: Valid objection → Integration needed

Example 3: Authority Gap

Proposal: “Event Manager role gets the accountability ‘plan and execute events.’”

Objection: “The role has no domain over the event budget. Without budget authority, it can’t plan events. This creates a role that can’t fulfill its accountability.”

Testing:

• Harm: ✓ (role can’t fulfill accountability)
• Causality: ✓ (the proposal creates the incomplete role)
• Novelty: ✓ (the role doesn’t exist yet)
• Organization: ✓ (affects ability to work)

Result: Valid objection → Integration needed

Example 4: Process Disruption

Proposal: “Sales may change prices without consultation.”

Objection: “Finance creates invoices based on the price list. If Sales changes prices without informing Finance, invoices with wrong prices will be created. This damages our customer relationships and creates billing chaos.”

Testing:

• Harm: ✓ (wrong invoices, customer complaints)
• Causality: ✓ (the policy enables uncoordinated changes)
• Novelty: ✓ (currently price changes must be coordinated)
• Organization: ✓ (affects customer satisfaction and finances)

Result: Valid objection → Integration needed

Example 5: Responsibility Gap

Proposal: “Delete the ‘Office Manager’ role.”

Objection: “No one else has the accountability ‘order office supplies.’ If we delete the role, no one will order office supplies and we’ll run out of printer paper.”

Testing:

• Harm: ✓ (no responsibility for essential task)
• Causality: ✓ (the deletion creates the gap)
• Novelty: ✓ (currently the responsibility is clear)
• Organization: ✓ (affects office operations)

Result: Valid objection → Integration needed

Examples: Invalid Objections (Concerns)

Example 1: Opinion Without Harm

Proposal: “Marketing role gets the accountability ‘publish social media posts.’”

Pseudo-objection: “I think social media isn’t that important.”

Testing:

• Harm: ✗ (no harm description, just opinion)

Result: Not an objection, but a concern → belongs in reaction round

Example 2: Existing State

Proposal: “Customer Success role is created with the purpose ‘customer satisfaction after purchase.’”

Pseudo-objection: “We generally have problems with customer satisfaction.”

Testing:

• Harm: ✓ (customer satisfaction problems are real)
• Causality: ✗ (the problem exists independent of the proposal)

Result: Not an objection to this proposal → bring as separate tension

Example 3: Improvement Suggestion

Proposal: “Design role gets the domain ‘corporate design.’”

Pseudo-objection: “Wouldn’t it be better if Marketing had that?”

Testing:

• Harm: ✗ (no harm described, just alternative idea)

Result: Not an objection → bring own proposal in the next round

Example 4: Personal Preference

Proposal: “Meetings start at 9 AM.”

Pseudo-objection: “I’m not a morning person and prefer to work later.”

Testing:

• Harm: ✓ (person is less productive)
• Causality: ✓ (the proposal sets the time)
• Novelty: ✓ (new rule)
• Organization: ✗ (personal preference, not organizational harm)

Result: Not an objection → concern can be shared in reaction round

Example 5: Missing Prediction

Proposal: “We introduce weekly stand-ups.”

Pseudo-objection: “I’m not sure if that will work.”

Testing:

• Harm: ✗ (no harm description, just uncertainty)

Result: Not an objection → “Good enough to try”

Example 6: Ideal State

Proposal: “Product Owner role gets 3 accountabilities.”

Pseudo-objection: “That’s too many accountabilities. Roles should be focused.”

Testing:

• Harm: ✗ (abstract preference, no concrete harm)

Result: Not an objection → can be adjusted later if problems arise

Common Mistakes

Mistake 1: Accepting Objections Too Quickly

Problem: The facilitator accepts every stated objection without conducting validity testing.

Consequence: Any person can block any proposal. Governance becomes political.

Solution: Systematically run every objection through all four tests. Ask clearly: “What concrete harm do you see?”

Mistake 2: Rejecting Objections Too Quickly

Problem: The facilitator rejects objections without seriously testing them.

Consequence: Real risks are overlooked. Trust in the process erodes.

Solution: Take every objection seriously and test methodically. When in doubt, integrate.

Mistake 3: Suppressing Concerns

Problem: Concerns are treated as worthless.

Consequence: Important information is lost. Participants feel ignored.

Solution: Explicitly welcome concerns in the reaction round. “Your perspective is valuable and informs the proposer.”

Mistake 4: Conflating Objection and Person

Problem: A rejected objection is experienced as personal criticism.

Consequence: Participants raise fewer objections out of fear of rejection.

Solution: Communicate: “It’s not about whether your objection is ‘good,’ but whether it meets the technical criteria.”

Mistake 5: Objections as Negotiation Tactics

Problem: Participants use objections to push through their preferences.

Consequence: The process is manipulated. Trust erodes.

Solution: Consistent validity testing. Address patterns: “I notice your objection doesn’t describe harm to the organization.”

Research Insight: Research on Holacracy implementations shows that correct distinction between objections and concerns often only becomes consistent after 6-12 months. Training and regular reflection accelerate the learning process. [3]

Practical Exercises

Exercise 1: Objection Analysis

Analyze the following statements. Is it a valid objection or a concern?

1. “The proposal gives no one responsibility for data privacy. This will lead to compliance violations.”
2. “I don’t think that’s the best solution.”
3. “This contradicts our existing remote work policy.”
4. “This will work, but I would have done it differently.”
5. “If we delete the role, no one will have access to the CRM system.”

Solution:

1. Valid objection (concrete harm: compliance violations)
2. Concern (opinion, no harm)
3. Valid objection (contradiction to existing governance)
4. Concern (preference, no harm)
5. Valid objection (concrete harm: system access lost)

Exercise 2: Objection Formulation

Transform the following concerns into potential objections by identifying concrete harm.

1. Concern: “I’m not sure if we can do this.” → Objection: “With our current capacity, we won’t be able to deliver [X], which will cause [concrete harm].”

2. Concern: “That’s too complicated.” → Objection: “The complexity will cause [who] to not understand [what], which will cause [concrete harm].”

Exercise 3: Facilitator Training

Practice validity testing with a partner:

1. Partner A makes a proposal
2. Partner B raises an objection
3. Partner A tests the objection with the four questions
4. Reflect together: Was the objection valid?

Objections at SI Labs

Our experiences with the objection-concern distinction:

The 80/20 Rule

About 80% of initially raised objections are concerns when examined closely. That’s normal and not a problem, as long as the facilitator consistently makes the distinction.

The Learning Process

New team members need 3-6 months until they can intuitively distinguish between objections and concerns. Proper understanding comes through practice in governance meetings. We support this through:

• Explicit explanation during onboarding
• Debriefs after governance meetings
• Encouragement to raise too much rather than too little

Language Changes

Over time, team members change their phrasing. Instead of “I don’t like that,” they say “I see the following harm…” or “That’s a concern, I’ll share it in the reaction round.”

---

Research Methodology

This article is based on the analysis of 73 academic papers on the topic of Self-Organization Governance (thematic cluster T00) as well as over ten years of practical experience with the Holacracy decision process at SI Labs.

Source selection:

• Empirical studies on decision processes in self-organized contexts
• Holacracy implementation studies with focus on governance processes
• Practitioner literature on facilitation and objection testing

Limitations: As practicing facilitators, we have developed strong convictions about the importance of the objection-concern distinction. We have endeavored to support these through research findings.

---

Disclosure

SI Labs GmbH has practiced Holacracy for over ten years. Several team members are certified Holacracy facilitators. This experience shapes our perspective on the importance of clean governance processes.

---

Sources

[1] Velinov, Emil, et al. “Change the Way of Working: Ways into Self‐Organization with the Use of Holacracy.” Journal of Organizational Change Management 34, no. 5 (2021): 1063-1078. DOI: 10.1108/jocm-12-2020-0395 [Qualitative study | 43 interviews | Citations: 43 | Quality: 67/100]

[2] 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]

[3] Robertson, Brian J. Holacracy: The New Management System for a Rapidly Changing World. New York: Henry Holt and Company, 2015. ISBN: 978-1627794879 [Practitioner guide | N/A | Citations: 523 | Quality: 55/100]

[4] Romme, A. Georges L., and Gerardus A. Reymen. “The Building of Shared Purpose Without Managers: How Holacracy Works.” Academy of Management Proceedings 2020, no. 1 (2020): 20972. DOI: 10.5465/ambpp.2020.20972abstract [Empirical study | 2 organizations | Citations: 15 | Quality: 61/100]