{{The_Intersection_of_Theory_and_Practice|float:right}}For the purposes of this project, a pattern is a feature we believe shows up repeatedly in [[http://processarts.wagn.org/wagn/processes|group processes]] that result in deepening, connection, and a fulfillment of purpose. 

Scope: Our scope is the realm of deliberative/dialogic group processes aimed at goals such as decision-making, input, feedback, visioning, and conflict resolution, that take place in the context of meetings, conferences, and other convenings that have these goals.  Thus there are many times when people gather together that are beyond our zone of exploration (weddings, soccer matches, choir practice, etc.), although some of the patterns we come up with might also occasionally apply beyond our chosen domain.

While we believe that many of these patterns show up cross-culturally, we do not make the claim that our pattern language is universal.  This language is being written by a cross-section of North Americans from a variety of group backgrounds (political activism, communal living, and other alternative cultures; higher education; corporate experience in finance, software, and other fields; religious organizations; nonprofit management; indigenous tribes; public agency work; etc.).  That diversity lends strength but falls far from addressing all places and groups.  Any session takes place within a specific cultural context, and our assumption is that users of this language will take what inspires them and adapt appropriately.

Range: If you think about everything that goes into making a group conversation fulfilling, there is a vast range of things to pay attention to, from the most general to the most specific. In crafting this language, we ask people to focus on a particular middle section within this range, and hold your thinking at that level. We want to avoid being too general: For example, values such as democracy and cooperation, or principles such as Schwarz’s “valid information” and “free and informed choice,” are assumed or embedded rather than explicitly considered in the body of this work. We also want to avoid being too specific: There is a level of detail that is already well-represented in the existing literature and that we do not seek to replicate, namely:

• listing and explanations of methods (e.g. [[http://thechangehandbook.com/content/category/6/16/38/|The Change Handbook]]);
• catalogues of tools and techniques.

Of course within our [potential[[potential patterns|list of potential patterns]], some of them are more general and some are more specific, just as [[http://www.patternlanguage.com/leveltwo/patternsframegreen.htm?/leveltwo/../apl/twopanelnlb.htm|Alexander's architectural pattern language]] includes patterns ranging from "Independent Regions" to "Different Chairs."

Rather than listing methods or techniques, we look for behaviors and qualities that repeat across methods and approaches. What is it that happens over and over again in group processes that work? And then we try to give some guidance for how to do that behavior or evoke that quality. Preferably in straightforward language, using as little jargon as possible. Essentially, we are aiming at the core wisdom of what makes group work successful. And we want it to sing.

{{Hallmarks List|open}}

See also [[What is a Pattern Language]]

{{+discussion|closed}}