I’ve written before about how to improve your conference with explicit ground rules. Though it’s interesting and enlightening to compare the ground rules embedded in conference designs—for example, Open Space Technology has five ground rules, while Conferences That Work and World Café have six—I won’t do that today. Instead, I want to share two principles for designing conference ground rules.
Ground rules should increase participants’ freedom, not restrict it
- “Don’t speak unless the teacher asks you a question.”
- “Pay attention!”
- “Don’t chew gum in class.”
We’re used to rules like these that restrict our actions and reduce our freedom. But, surprisingly, it’s quite possible to create ground rules that increase our freedom at an event. Here are some examples:
- Whenever it starts is the right time.—Open Space Technology
- You have the freedom to ask about anything puzzling.—Conferences That Work
- Make collective knowledge visible.—World Café
Each of these is a rule that gives permission for participants to act in a way that does not generally occur at traditional meetings. By explicitly giving permission for activities that normally are not associated with Conference 1.0 events, we increase participants’ freedom.
Make ground rules measurable
- “Listen to others.”
- “Be respectful.”
- “Treat people politely.”
Rules like these are superficially appealing, but they aren’t effective because they rely on unmeasurable assumptions. How can we determine whether a participant is listening, respectful, or polite? We can’t, and this can lead to unproductive, time-consuming, and ultimately unresolvable disagreements during an event.
In contrast, here are examples of ground rules that are measurable and thus far less likely to lead to disagreement and subsequent conflict.
- “Don’t interrupt.”
- “Stay on time.”
- “Keep what happens in each session confidential, unless everyone agrees otherwise.”
How were these principles for designing conference ground rules derived?
It would be nice to be able to claim that I first conceived these meta-rules for ground rule design, and then used them to build my conference ground rules. No such luck! It took me ten years to realize that explicit ground rules for Conferences That Work would be useful, and another five to figure out the six I now use. Only recently did I notice that all six follow the two principles I’ve described above.
What ground rules do you use for your events? Can you share any other principles for designing conference ground rules?