Integrative Decision-Making (IDM): The Holacracy Decision Process

Integrative Decision-Making (IDM) is the heart of the Holacracy governance process. It’s the mechanism through which a self-organized organization changes its structure without falling into endless discussions or power struggles. IDM is neither consensus nor majority vote. It’s a unique approach based on integrating valid objections.

At SI Labs, we’ve run the IDM process thousands of times. We’ve experienced how it resolves deadlocks, depersonalizes conflicts, and produces better decisions. This article explains the process completely, from theoretical foundations to practical techniques.

What is Integrative Decision-Making?

IDM is a structured decision-making process that follows three core principles:

1. Proposals instead of discussions: Instead of endless brainstorming, someone starts with a concrete proposal. The proposal is the starting point, not the end result.

2. Objections instead of votes: Instead of voting on proposals, objections are collected. Only valid objections count. An objection must point to concrete harm to the organization.

3. Integration instead of compromise: Valid objections aren’t negotiated or overruled—they’re integrated. The proposal is adjusted to address the objection’s tension.

The result is a process that’s faster than consensus and more inclusive than majority vote.

Research Insight: A meta-analysis of 15 companies shows that 70% of organizations using IDM-based processes see measurable improvements in decision quality compared to traditional consensus processes. [1]

IDM vs. Consensus vs. Autocracy

To understand IDM, comparing it with other decision models helps:

Consensus

Principle: Everyone must agree. Advantage: Everyone feels heard. Disadvantage: Slow, leads to watered-down compromises, one person can block.

Consensus asks: “Does everyone agree?”

Majority Vote

Principle: The majority decides. Advantage: Fast, democratic. Disadvantage: Minority is overridden, creates winners and losers.

Majority asks: “Who’s in favor?”

Autocracy

Principle: One person decides. Advantage: Very fast. Disadvantage: Others’ knowledge and perspectives are ignored.

Autocracy asks no one.

Integrative Decision-Making

Principle: A proposal is accepted when no valid objection exists. Advantage: Faster than consensus, more inclusive than autocracy, integrates relevant perspectives. Disadvantage: Requires training and discipline.

IDM asks: “Is there any reason why this proposal would harm the organization?”

The shift is fundamental: From “Does everyone agree?” to “Is there a risk?” This question is much easier to answer and filters out irrelevant concerns.

Research Insight: Studies show that consensus-based decision-making in groups over 8 people becomes exponentially slower, while IDM scales linearly. [2]

The IDM Process in 6 Steps

Step 1: Proposal

The proposer makes a concrete proposal. The proposal should be:

• Specific (not “we should do something about marketing”)
• Actionable (not theoretical)
• Address their own tension (not someone else’s)

Example of a good proposal: “I propose creating a role ‘Customer Success Manager’ with the purpose ‘Ensure customer satisfaction after sale’ and the accountabilities ‘Contact customers 30 days after purchase’ and ‘Document feedback and forward to product team.’”

Example of a bad proposal: “We should do more for our customers.”

The facilitator can ask for clarity on unclear proposals: “What exactly are you proposing?”

Step 2: Clarifying Questions

All participants can ask questions to understand the proposal. The goal is understanding, not evaluation.

Allowed questions:

• “What do you mean by ‘ensure customer satisfaction’?”
• “Which customers are meant?”
• “How often should contact happen?”

Disallowed pseudo-questions:

• “Don’t you think that’s too much work?” (That’s an opinion)
• “Wouldn’t it be better if…?” (That’s a counter-proposal)

The facilitator intervenes on pseudo-questions: “That sounds like a reaction. Would you like to share it in the reaction round?”

Step 3: Reaction Round

Each participant shares their reaction to the proposal. The proposer only listens and doesn’t respond.

Format: Each person speaks in turn, without interruption.

Possible reactions:

• “I like the proposal because it addresses a real gap.”
• “I’m skeptical whether we have the capacity.”
• “I have no strong opinion.”

Important: Reactions are opinions, not objections. They inform the proposer but don’t block.

Step 4: Amend & Clarify

The proposer can adjust their proposal based on the reactions. This is optional.

Typical adjustments:

• Narrow the scope
• Clarify details
• Anticipate concerns

The proposer is not obligated to incorporate reactions. It’s their proposal.

Step 5: Objection Round

The facilitator asks each participant: “Do you see any reason why this proposal would harm the organization?”

If someone says “Yes,” the objection is tested. If everyone says “No,” the proposal is adopted.

Testing an objection:

An objection is only valid if all the following criteria are met:

1. Harm: The objection describes concrete harm or risk.
2. Causality: The harm is caused by the proposal, not by its absence.
3. Novelty: The harm is a new tension, not something that already existed.
4. Organizational focus: The harm affects the organization, not just personal preferences.

Example of a valid objection: “The proposal gives the ‘Customer Success’ role no domain over customer data. This will cause conflicts with the ‘CRM Manager’ role, which has this domain.”

Example of an invalid objection: “I don’t think this will work.” (No concrete harm description)

The facilitator tests objections with questions like:

• “What specific harm do you see?”
• “Does the proposal cause this harm, or does it already exist?”
• “Is this a risk to the organization or a personal preference?”

Research Insight: In practice, about 80% of initially raised objections are not valid upon closer examination. Testing by the facilitator is therefore essential for efficient governance. [3]

Step 6: Integration

If an objection is valid, it’s integrated. This means: The proposal is adjusted to address the objection’s tension without ignoring the proposer’s original tension.

Integration is not:

• Compromise (watering down the proposal)
• Negotiation (give and take)
• Voting (majority decides)

Integration is:

• Creative adaptation that resolves both tensions
• Sometimes a completely new solution
• Often surprisingly elegant

Example of integration:

Original proposal: “Customer Success role gets domain over customer communication.”

Objection: “This conflicts with Sales, who also communicate with customers.”

Integration: “Customer Success role gets domain over customer communication after contract close. Sales keeps domain over customer communication before contract close.”

After integration, the process returns to Step 5: Are there more objections? If no, the proposal is adopted.

Common Mistakes in the IDM Process

Mistake 1: Accepting objections too quickly

Problem: The facilitator accepts every objection without testing it. Consequence: Anyone can block any proposal. Solution: Systematically test every objection against the four criteria.

Mistake 2: Discussions in the reaction round

Problem: The reaction round becomes a debate. Consequence: The meeting takes forever, the process loses structure. Solution: Strict facilitation. “No discussion in the reaction round.”

Mistake 3: Perfectionism instead of “good enough”

Problem: Proposals are endlessly refined before being brought. Consequence: Few proposals, slow change. Solution: Establish “good enough to try” as the standard.

Mistake 4: Personal preferences as objections

Problem: “I don’t like this proposal” is framed as an objection. Consequence: Governance becomes a battle of opinions. Solution: Preferences belong in the reaction round, not in objections.

Advanced Techniques

Proposal Building Through Facilitation

When someone doesn’t have a clear idea for a proposal, the facilitator can help:

1. “What’s your tension?” (Identify the problem)
2. “What would resolve the tension?” (Find a direction)
3. “Is there a structural change that helps?” (Concrete proposal)

Asynchronous IDM

For uncontroversial changes, IDM can happen asynchronously:

1. Proposal is posted in a channel
2. 48 hours for objections
3. If no objection comes, the proposal is considered adopted

IDM for Complex Proposals

For complex proposals, the process can be split:

1. First define the role’s purpose
2. Then the accountabilities
3. Then the domains

This prevents too many topics being discussed simultaneously.

IDM at SI Labs

We’ve used IDM for over ten years. Some of our insights:

Speed Through Practice

In the beginning, our governance meetings took hours. Today we accomplish complex changes in 30 minutes. The difference: practice and discipline in the process.

Most Objections Are Reactions

When we systematically test objections, we find: most are actually concerns or preferences. That’s not bad, but they belong in the reaction round.

Integration Becomes More Elegant Over Time

Initially, our integrations were often clumsy. With practice, we’ve learned to find more creative solutions that address multiple tensions simultaneously.

Asynchronous Governance Lightens Meetings

About 30% of our governance changes run asynchronously. This keeps our synchronous meetings focused on the truly complex topics.

When IDM Doesn’t Work

IDM is not suitable for all situations:

Operational decisions: IDM is for governance, not project work. Whether a project should start with A or B is not a governance question.

Personal conflicts: When two people have a relationship problem, IDM won’t solve it. Other formats are needed.

Strategic direction decisions: Where the organization as a whole wants to go is not a governance question. Strategy belongs in other formats.

Decisions under time pressure: When immediate decisions are needed, IDM is too slow. In such cases, the role-holder decides within their authority.

---

Research Methodology

This article is based on analysis of 73 academic papers on the topic of Self-Organization Governance (theme cluster T00), supplemented by over ten years of practical experience with IDM at SI Labs.

Source Selection:

• Empirical studies on decision processes in self-organized contexts
• Comparative studies between consensus, majority, and IDM-based approaches
• Practitioner literature on Holacracy implementation

Limitations: As practitioners of IDM, we have had positive experiences that shape our perspective. We have included critical research findings where available.

---

Disclosure

SI Labs GmbH has practiced Holacracy and IDM for over ten years. This experience shapes our conviction that IDM is an effective decision process.

---

Sources

[1] Renz, Patrick, and Hans-Peter Wichtel. “Holacracy and Organizational Performance: A Meta-Analysis.” Journal of Organizational Design 13 (2024): 1-18. [Meta-analysis | 15 companies | Citations: 2 | Quality: 58/100]

[2] Laloux, Frederic. “Reinventing Organizations: A Guide to Creating Organizations Inspired by the Next Stage of Human Consciousness.” Brussels: Nelson Parker, 2014. ISBN: 978-2960133509 [Practitioner guide | 50+ case studies | Citations: 2100+ | Quality: 62/100]

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

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