Team Decision-Making with Consent: Why "Are there any objections?" is the better question

Do you recognize this in your team? An important decision is on the table, and you spend hours discussing, going in circles, only to postpone the decision—or hand it over to your team lead. How can decisions like this be made with less frustration and more flow?

One approach worth trying in such cases is the consent decision-making process. Unlike consensus, its goal is not to achieve full agreement, but to move forward as long as there are no objections.

Consent (not to be confused with consensus) is a decision-making process in which a proposal is accepted if no one has a valid objection. Put differently: a decision is made when no participant can give a reason why the proposal would cause harm to the organization or falls outside the group’s shared tolerance.

The difference from consensus is clear: while consensus requires everyone to actively agree, consent requires only that no one objects. This seemingly small distinction has a huge impact on decision-making dynamics—and can spare teams from paralyzing discussions.

The consent process originates in sociocracy, an organizational model developed in the 1970s by Dutch entrepreneur Gerard Endenburg. He was looking for a way to make decisions in his electrical engineering company that were both efficient and participatory.

Inspired by reform educator Kees Boeke and cybernetic principles, Endenburg created sociocracy as an organizational form built on the equivalence of all participants. The consent principle is one of its four pillars:

• Consent principle: Decisions are made if no one objects.
• Circle structure: The organization is divided into circles (teams) with their own decision-making authority.
• Double linking: Circles are connected to the next higher circle by at least two people.
• Sociocratic elections: Roles are filled through an open nomination and selection process.

Today, the consent principle is often used independently of sociocracy—especially in agile teams and self-managed organizations. I first encountered it in Sociocracy 3.0 (S3), a flexible, pattern-based approach to collaboration and decision-making.

The consent process follows a clear, structured flow. The version I use comes from Sociocracy 3.0, which offers a modular set of patterns to support more participatory and effective collaboration. S3 is not a rigid framework but a toolkit organizations can adapt to address tensions or development needs. What’s important: all steps belong to the process. They can be shortened or adjusted in intensity, but they should not be skipped.

First comes clarification of the underlying driver and requirement. A driver in Sociocracy 3.0 describes the situation that makes change necessary – it consists of a description of the current situation, the effects of this situation, and the requirement that must be fulfilled. Everyone should understand why this decision needs to be made at all and whether the group is the right one to decide on it.

The questions here are:

• Is the description of the driver clear enough?
• Is it relevant for the team or organization?
• Are we the right people to make this decision?

One person or a small group presents their proposal. Ideally, this was already shared in writing beforehand so everyone could familiarize themselves with it.

Before substantive discussion begins, all participants have the opportunity to ask questions for understanding. This is exclusively about fully understanding the proposal, not evaluating or discussing it.

Everyone briefly shares their thoughts and feelings about the proposal. This helps make different perspectives visible and gives a first impression of how the proposal is received.

The facilitator asks: "Are there any possible objections or concerns about this proposal?"

Important to understand: Concerns don't prevent a proposal from becoming an agreement – only qualified objections do that.

In this step, it's examined whether the arguments raised actually qualify as objections. The group checks together whether the argument shows that the unchanged proposal:

• leads to consequences that should be avoided
• could lead to risks that shouldn't be taken
• shows a better way to achieve the goal

Now the proposal is improved based on the information revealed by the objection. The attempt isn't to circumvent or outvote the objection, but to integrate the insight to arrive at a better proposal.

If no further objections exist, an agreement is reached! This is a moment to celebrate – the proposal now counts as "good enough for now and safe enough to try." It’s about moving forward, not finding the perfect solution.

Concerns (softer doubts or gut feelings) can still be noted for later evaluation, but they don’t block the decision.

A central aspect of the consent process is the clear distinction between serious objections and personal preferences or concerns.

An objection means: If we implement the proposal this way, serious risks or disadvantages arise for the team or organization, or there's a significantly better way.

A concern, on the other hand, is more of a gut feeling or uncertainty for which there aren't yet clear arguments or strong evidence.

Task management tool

• Qualified objection: "We'll lose the time tracking integration. This leads to double data entry."
• Personal concern: "I don't know this tool and would have to learn it first."

Team restructuring

• Qualified objection: "Two closely interlinked areas would be separated. This increases coordination effort."
• Personal concern: "I don't want to leave my current team."

1. Efficiency with simultaneous participation
The consent process is significantly faster than classic consensus but still includes all participants.
2. Focus on legitimate objections instead of personal preferences
Through clear distinction, only truly relevant concerns are addressed.
3. More robust decisions
The integration of objections leads to better, more thoughtful solutions that consider more perspectives.
4. Higher acceptance during implementation
Since everyone had the opportunity to raise objections, acceptance for implementation is higher than with top-down decisions.
5. Strengthening team culture
The respectful handling of objections and collaborative solution-finding strengthens trust in the team.
6. Learning effect through integration of perspectives
Teams continuously learn from each other and develop a deeper understanding of different perspectives on decisions.

Not every decision justifies the effort of a complete consent process. From my practice, I can offer the following guidance:

Well-suited for consent:

• Strategic decisions with long-term effects on team or organization
• Structural changes like team reorganizations or new workflows
• Decisions that fundamentally change collaboration
• Conflict-heavy topics where different perspectives are important

Less suited for consent:

• Day-to-day operational decisions
• Decisions that need to be made quickly
• Decisions requiring specific expertise that clearly fall into individual experts' responsibility

Of course, there are also challenges in applying consent decision-making:

Challenge 1: Distinguishing between objections and preferences
Solution: Practice regularly as a team to make this distinction. Question objections constructively: "Can you explain how this proposal would harm the team?"

Challenge 2: Dominant personalities can influence the process
Solution: A good facilitator ensures that everyone gets to speak and objections are discussed objectively. Rotating moderation can help here.

Challenge 3: Time pressure can lead to superficial application
Solution: Prioritize which decisions really need to be made through consent. Not every decision needs this process.

Challenge 4: Difficulties integrating complex objections
Solution: For very complex objections, it can make sense to form a small working group that develops a revised proposal. In the Sociocracy 3.0 toolkit, this is called Proposal Tuning.

Challenge 5: New team members aren't familiar with the process
Solution: Document your consent process, ensure onboarding, and encourage new team members to ask questions.

The consent process works well remotely. Some adaptions might be helpful:

• Use digital whiteboards (Miro, Mural) for collaboration.
• Apply clear facilitation in video calls
• Share proposals and materials asynchronously beforehand
• Keep groups smaller for easier moderation

The consent process is, in my view, a helpful approach for decision-making in teams. It combines the advantages of participatory processes with pragmatic efficiency. I find the perspective shift particularly important: Objections aren't disruptions, but valuable contributions to improvement.

A tip for everyday use: Don't ask "Do you agree?" but rather "Are there any objections?" Test what effect it has to not always ask for agreement, but to ask for objections instead.