First of all, as it says on the Home page, in order to understand where we're coming from please read the following pages before writing or editing patterns:
Reminder: What we mean by "pattern"
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. The Change Handbook);
- catalogues of tools and techniques.
Of course within our brainstorm list of potential patterns, some of them are more general and some are more specific, just as 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 (aka "The Pruning Tool")
The following list of questions are here to help guide the pattern writing and editing process. While it’s not required that every pattern necessarily be able to answer yes to every question on this list, these are hallmarks that have been noted across many of the patterns.
Does it further the goals of the project?
- Support purpose-driven design
- Deepen the skills of those who serve as group process guides
- Serve as a resource for those who are teaching others
- Increase process literacy among people who are users of process(es)
Does it point us toward “the quality that has no name”? Does it describe a feature that shows up repeatedly in group processes that result in “deepening, connection, and a fulfillment of purpose”?
Does it feel resonant? Is it evocative? Does my gut respond to this with a sense of recognition?
Do it happen across methods/approaches? Is it a common piece underlying multiple methodologies? This is like stacking functions in permaculture, where one element contributes to many yields.
Is it unifying? Can it take a large variety of forms? It may bring together what previously seemed like separate aspects of group process.
Is it fractal? That is, does it show up at more than one scale (such as within one item of a meeting and again within the meeting as a whole)?
Is it a distinct creature? That is, once grasped, it stands out as its own thing, coherent, and not merely a result of other aspects of process. While it may take a while to first “see” a pattern, its essential “shape” should be easy to recall once understood.
Does it describe an action that can be consciously undertaken by convenors and/or participants? Rather than, for instance, a dynamic to be passively observed. Does knowledge of this pattern increase the skill of practitioners?
See also What is a Pattern Language
Steps to compose and enter patterns into the pattern language site
- Review the existing brainstorm list of potential patterns to get some sense of possibilities.
- Take a look at some of the Patterns that have already been written.
- Choose an area of group process in which you have experienced a sense of something really working, and where you have some ideas or inspiration about how and why this has occurred.
- Click Add a pattern to go to a blank pattern template. (This link also available in sidebar.)
- Enter a name for your pattern. This could be a name from the existing list or something new.
- Read the explanation by each section to see what's wanted for it. For your convenience, that template text is also available here, below. At a minimum, write up a draft-quality Heart section and enough of a Description that would allow others to get a sense of where you are going. (If you’re more comfortable working offline or in your own personal word processor, you can copy the section headings: Heart, Description, etc.) If you refer to another pattern, then put that pattern name in double brackets [[like this]] to create a link.
- When you're done filling out the form, scroll all the way to the bottom and click on the "Save" button.
Template for pattern writing
NAME
A pattern name should be a short, evocative word or phrase. Usually 1-3 words, occasionally longer. Succinctly titles the pattern for common reference and at the same time conveys (or at least hints at) the heart of the design instruction.
VISUAL
An evocative visual, either symbolic or representational. There are good places for finding images.
HEART
What is the essential core of this pattern? Why is it important: what calling, purpose, or higher values are expressed through it? What possibilities does it open up? What needs does it satisfy? Two to four sentences in length; an abstract.
DESCRIPTION
Context: What is outside of this pattern that is relevant to it? Under what recurring circumstances might we apply it — the “if” for which this pattern is the “then.” What forces and constraints are worked in this pattern to produce the desired outcome?
Instructions: How does one use this pattern? Guidance designing or practicing this element in a group conversation. What users should know about it.
Variations (optional): Different ways the pattern might be implemented. May include specific, named techniques or formats that embody or apply this pattern.
Cautions & Caveats (optional): Potential misinterpretations, misuses, exceptions, over-applications and/or limitations of the pattern.
RELATED PATTERNS
Patterns that are closely linked to this one, for example because they mutually support each other, or because one of them depends on the other or is a subset of it.
EXAMPLES
What best illustrates this pattern at work in group process? Offer one to three examples that bring the pattern to life, providing a sense of the range of possible solutions using the pattern. Could include songs, poems, videos, and other forms as well as written stories.
RESOURCES
How to learn more about this pattern, including: people who have experienced it in use and can say what it is like; organizations, networks or individuals who can provide information or expertise about this pattern; other references – books, websites, articles, videos, bibliographies.
OTHER
Anything else you want to say about the pattern. Could include:
Levels/Fractal: How does this pattern play out at various individual and collective/holonic levels (micro and macro)? In the hierarchy of patterns (from general to specific), what level is this pattern at? What category does it occupy with other patterns at its level?
Learning Edges: Reflective commentary at the borders of what is known about a pattern, its application, and its relationship to other patterns. May include instances where the pattern appears to break down, pose questions that arise in application, offer insight into unusual applications, etc.
Quote: Short, expressive statement that embodies or articulates this pattern (explicitly or implicitly), from a recognized authority, or an especially astute observer or advocate of the pattern.
STAGES
See more about stages.
We've held a few events now where we've done pattern-writing in groups. While some people feel fine writing patterns solo from home, given that we are writing a pattern language of group process it's not surprising that many of our collaborators find it more fun or effective to do the pattern writing live in groups. Here is some of what we've learned so far about doing that. We've found there tend to be several steps in the development process for each pattern. Here is the sequence we naturally fell into during the April 2010 session at Bowen Island: A. Initial brainstorming: An open-ended conversation of 2-4 people surfacing ideas and possibilities for this pattern (3 people seemed to be a particularly popular number). Patterns selected based on who was excited to work on what.
-
One person would volunteer to be notetaker. Many of our notetakers used a starting document within a word-processing program listing the main categories of our template so that as people spoke their statements could be directly entered into the categories of:
- Image Ideas
- Heart & Description
- Cautions & Caveats
- Related Patterns
- Resources
- Other
We tended to group Heart & Description together and then later pull out the most essential or resonant statement as the Heart. While Cautions & Caveats is only an optional part of the description, we found ourselves listing it separately.
-
In order to deal with the problem of losing content input from the notetaker, some of us started by having a few minutes during which the notetaker would think and write their own initial thoughts, and then we'd start the out-loud conversation by having them tell the others their input.
- Sharing personal stories and experiences (some of which were outside the realm of group dynamics but could then be mined afterward for what would also apply in a group setting) was an important part of this.
- Other patterns this one might relate to would be mentioned in the course of the conversation, often accompanied by an immediate sorting as to whether the relationship was strong and consistent enough to justify inclusion in the Related Patterns category of the template or whether it was a more occasional relationship that might come up in the Description or as an Example. Sometimes new Potential Patterns were noted to be added to the brainstorm list. Familiarity with the existing lists of Patterns and Potential Patterns obviously helps enormously in this, and we found that newcomers gained enough currency to do this after one full day of choosing patterns from the list and discussing them.
- After a while of open conversation, the notetaker or someone else would ask for the categories of that pattern that had not yet been filled in, and we'd then target the conversation specifically to fill those fields.
- This step took about 30-60 minutes per pattern.
B. Writing up the rough notes, if it wasn't done simultaneously with the initial conversation. The notes need to be arranged into the proper categories of the template, and entered into the wiki. It's also good to select the Heart at this point while the conversation is still fresh. This is pretty much a one-person operation.
C. Polishing the notes: Taking the draft text that was often in the form of incomplete sentences or bullet points and drafting it into complete sentences and paragraphs to express that pattern. This also often includes tracking down correct links and references, or finding an actual visual to upload instead of just an idea for one. Completing this step usually moves the pattern from Sprout to Bloom stage. Probably best done by 1-2 people.
D. Editing the pattern: Normally includes one or more newcomers to working on that pattern. Looking the pattern over for language, clarity of expression, substitution of everyday words for process-geek jargon, seeing if the Name and Heart "sing," adding things that were missed, listing additional resources, and so on. If you are doing group reviews of entered patterns live in-person, it helps to have a projector on hand that can hook up to someone's computer.
.