If you want your team to be effective, you need meeting ground rules — and you need agreement about how to use them. Many teams that have ground rules don’t regularly use them. But having rules in place that you consistently enforce can significantly improve how your team solves problems and makes decisions. There are different types of ground rules. Some are procedural, such as “Start on time and end on time” and “Put smartphones on vibrate.” Procedural ground rules are useful but don’t help your team create productive behavior beyond, say, everyone being on time and having their smartphones on vibrate. Other ground rules are abstract, such as “Treat everyone with respect” and “Be constructive.” These rules focus on a desirable outcome but don’t identify the specific behaviors that are respectful or constructive. As a result, abstract rules create problems if group members have different ideas about how to act respectfully. For some group members, acting respectfully means not raising any concerns about individual members in the group; for other members it may mean the opposite. Behavioral ground rules are more useful. They describe specific actions that team members should take to act effectively. Examples of behavioral ground rules include “make statements and ask genuine questions” and “explain your reasoning and intent.” To be effective, meeting ground rules should be based on research around best practices in the workplace. For example, research has identified three results that all leadership teams need to achieve: strong performance, positive working relationships, and individual well-being. But many ground rules undermine one or more of these results. For example, some teams point out when a team member is off topic by directly saying “That’s off topic” or by using an agreed-upon word, such as “jellyfish.” But all these variations of the ground rules are based on the assumption that the person calling jellyfish is correctly stating that the other person is off topic. Research shows that calling out a team member can create unintended consequences if the person calling them out is wrong: The other person will keep raising the issue or will shut down for the rest of the meeting. Your team may make a lower-quality decision because that person’s contributions were not heard or because the person is not committed to implementing the decision. A more productive way to deal with this situation is to have a ground rule about testing assumptions and inferences. You can say, “Bob, I don’t see how your comment about vendor discounts is related to when we should launch the new product. Can you help me understand the connection, or, if it’s not related, can we figure out if and when we should address your topic?” Saying this enables you to quickly test your inference that Bob’s comment isn’t related. You may learn that Bob is thinking more systemically than the rest of the team and has identified an important issue that no one else thought of. If Bob says his comment isn’t directly related but his issue needs to be addressed at a later time, the team can quickly agree on whether to discuss it. Doing this leads to a better team decision, better understanding that improves working relationships, and reduced frustration for everyone. Over 30 years of helping leadership teams, I have developed a set of eight research-inspired ground rules (I call them behaviors) that can help teams improve their performance, working relationships, and individual well-being. (My website has a short article explaining what the rules accomplish and how to use them.) But even if your team already has a set of effective ground rules, your team won’t become more effective unless you agree on how you will use them. Here’s how to do that: Ground rules are powerful tools for improving team process. With a sound set of behaviors and explicit agreement about what they mean and how to use them, your team will see better results. This blog first appeared on Harvard Business Review on 06/15/2016. View our complete listing of Leadership Development blogs.
Agile processes for stable teams
March 08, 2021
Three Ways to Navigate Political Divides at Work
October 07, 2020