29-04-2025
Making decisions in agile teams - beyond the consensus principle
Modern, self-organized teams are supposed to make decisions independently. The idea: decisions are made decentrally. Closer to the market. Closer to the customer. But what does that mean concretely? Who decides what exactly? When and how? And who is ultimately responsible for the outcome?
The Consensus Reflex and Its Pitfalls
In many teams, I see a strong tendency toward consensus. Everyone should be included and on the same page. Sounds good, but often doesn't work, especially with tough topics.
The consequences:
- Paralysis. Difficult decisions get avoided because they're uncomfortable or consensus seems unrealistic.
- Compromises. Instead of good solutions, you often get the lowest common denominator. Nobody's truly satisfied.
- Roadblocks. Individuals can block decisions.
- Time sinks. Consensus takes time. Sometimes too much.
- Imbalance. Not everyone participates equally. Being loud doesn't automatically mean being competent.
Why Decisions Need Clarity, Not Just Participation
Having input is good. But participation alone isn't enough. What matters is that solid decisions actually get made. And at a pace that matches the situation.
This requires clarity. Who's accountable? How do we decide? And by when?
These four questions help structure team decisions clearly:
- What's it about? Is the topic clearly defined? Are goals and criteria spelled out?
- Who decides? Individual, circle, whole team, or leadership?
- How do we decide? Consensus, consent, majority vote, or individual call?
- How fast? Is there time pressure or can the topic marinate?
When questions like "Who decides?" and "How do we decide?" stay open, uncertainty creeps in. Some people then hold back. Not from lack of interest, but because consequences are unclear. And anyone who's seen a team decision get overturned later will be more cautious next time.
Often, unspoken dynamics play out in the background too. Whoever's louder tends to win. Whoever already has influence, obviously. This can damage trust and collaboration long-term.
Clarity doesn't mean micromanaging everything. It's about shared understanding. About roles, expectations, and decision logic.
Clear decision processes strengthen ownership in the team. They take pressure off leadership. And they make implementation faster. Because there's less uncertainty floating around.
Intentionally Designing Decision Processes
Not every decision needs the same approach. Depending on the topic, culture, team size, and urgency, different methods might work better.
What matters?
- Impact and significance of the decision: How far-reaching are the consequences?
- Available time: How urgent is the decision?
- Team size and structure: What method fits the number of people involved?
- Organizational culture: Should the method align with, or intentionally deviate from, the existing culture?
- Required buy-in for implementation: How much support from others is needed?
- Necessary expertise: Is it concentrated or distributed?
Mini Overview: Decision-Making Methods
- Consensus: Everyone agrees.
- Consent: No one has serious objections. (I illustrate how this works in practice in my case study on team reorganization at Pirate Ship.)
- Advice process: One person decides after consulting others.
- Majority vote: Democratic, but not always sustainable.
- Delegation: Responsibility gets clearly handed off
- Disagree & Commit: Despite different opinions, everyone commits to implementation
What Works When?
Two questions help:
- How decentralized should decisions be?How quickly do we need to decide?
The following diagram shows various decision-making processes along two dimensions:
How decentralized is the decision-making power? And: How quickly can decisions be made?
Depending on the situation, participation matters more. Or speed does. Consensus and individual decisions sit at opposite ends of the spectrum. Consent and majority votes offer good balance. Advice processes and delegation are often faster, but more centralized. The trick is choosing the right approach for each situation.
Reflection for You
How does your team make decisions? And does that fit where you are right now?
Bottom Line: Design Decisions Intentionally Instead of Leaving Them to Chance
Not every decision has to be consensus-driven. And not every decision should be made solo. The key question is: What fits this situation?
Anyone who wants to make effective decisions needs a clear decision framework. And the ability to choose situationally.
My advice: Make your decision processes visible. This clarity creates flow and strengthens ownership.
Want more clarity around decision-making in your team? I'd love to help. Through coaching sessions or workshops. Reach out for a no-strings-attached conversation.
Book a call