Your team has discussed the various options and it appears there is a general agreement in the room. The team leader suggests that if no one objects, the team agrees and you have consensus. Or do you?
Consensus means that everyone lives with the decision AND supports it upon implementation. By using the “silence implies agreement” rule, you might have consensus, but then again, you might not. Some common pitfalls:
Guessed Incorrectly. By listening to the discussion, reading the body language and making some inferences, the team leader is making a decision for all to abide by. Unfortunately, the team leader might be wrong and is asking people to have the courage and visibly object to the decision.
Power Play. Sometimes the team leader is intentionally pushing the decision through and doesn’t want to hear any objections. In reality, the team leader may achieve “pseudo-consensus” in the meeting, but will face resistance or sabotage during implementation.
Too Rushed. In the interest of time, the team pushes on without checking for agreement. Although, there will always be time to reemphasize and rework the issue when it becomes apparent the team is not committed to the decision.
No Voice. Quieter members certainly aren’t going to voice their opinions and extraverted members may venture a comment or two without trying to rock the boat. Unless the team leader is attuned to these subtle nuances, these unvocalized objections indicate a lack of consensus.
Ask Me Later. When the “silence implies agreement” rule is invoked, people simply reserve the right to object later. They don’t commit to the decision right then and there. Instead, they agree that they don’t object RIGHT NOW.
If your team is a victim of “pseudo-consensus,” take a moment to go around the room and ask each team member’s opinion.
Sarah Sheard, a systems engineering expert, found two things happen when you poll your team members:
- Build a Better Solution. Those who have reservations state the reservations, which they might not do if silence were an option. Often, their reservations change the whole direction of the group. Either they think of something no one else has, and thereby add to the quality of the product, or they have a real problem with it which the group has to address to ensure buy-in.
- Internal Buy-in. If a team member is required to respond to a request for buy-in, they have to make a commitment to the decision internally. If you have to say publicly “yes”, “no” or “I can live with it” (note, you can use a quick thumbs up, thumbs down or thumbs sideways for quick polling), then you actually decide at that point that your decision is what you say it is. Otherwise, you might reserve judgment.
A quick poll of the participants can improve the quality of the decision, ensure all team members are heard and help them make an internal commitment to the decision.
Question: Are you getting real consensus from your team members?
To book Kristin to speak or view her products go to www.ExtraordinaryTeam.com


Remember, whatever issue you are working on, the boss doesn’t have all the answers. The boss can (and often does) identify the issues, assign priorities, direct tasks, measure progress, etc. But the boss doesn’t do the work. You do. And who knows best how the work should be done? You do. So why not get your input in the process? Working as a team, you will have higher quality and a greater stake in successfully carrying out the decision.
So you have decided to have a staff meeting involving all your CSRs. Rather than corralling them into a room and talking at them, spend a few moments planning a team-based staff meeting:
You have piles of papers on your desk that report all kinds of operational data: time to answer, duration of call, cost per customer, abandonment rate, IVR first response, etc. With call center technology counting each click, we generate more data than we need or could ever use. However, each piece of information is part of the bigger puzzle created to help manage your CSR team better. Right?
Do you believe there is strength in numbers? Teams are based on the notion that two heads are better than one.
oach, he suggests the following techniques to make sure your team uses one voice:
Have you ever had one of your teammates complain about the same thing over and over again to the point that you could predict what they were going to say? It may even seem as though they just want to complain and are not interested in the solution.