CIRAL Pattern Language
This list contains patterns in various stages of completion -- all the way from just a title to a pattern in the Liberating Voices book. The idea is to use these patterns as an organizing strategy. The patterns, essentially, would form a “master plan” similar to that used by the University of Oregon. One of the most important aspects of the patterns, required by the project (we hypothesize) is the use of various facets. A preliminary list of these facets includes: Status (basically whether it’s adopted, preliminarily adopted, etc.), phase of life-cycle, category (perhaps), and other contextual information (e.g. used for home office).
Philosophy and Perspective
Design Stance (44)
Ecosystem of Efforts (proposed)
Evergreen (and the community “outside” of Evergreen) engage in many activities that demonstrate and promote civic intelligence: we must think of CIRAL as a symbiotic entity that strives to support other groups with similar objectives by encouraging the use of their facilities and services while developing facilities and services that others can use.
Experimental School (89)
Opportunity Spaces (33)
Community (CIRAL / internal)
We are consciously opening up participation for Evergreen students, Evergreen faculty and staff, as well as community members and students around the world.
Thinking Communities (118)
Education and Values (17)
Sustainable Design (22)
Participatory Design (36)
Capacity (CIRAL and beyond)
Capacity Bootstrapping (proposed)
Our capacity will always (of course) be finite. But we can build on what we have and increase it gradually over time through reflection, experiment, experience, dedication and creativity.
Strategic Capacity (34)
Leadership Development (proposed)
Leadership, much as the ability to support or follow, is of value and has rights and responsibilities. While we believe that everyone can -- and should -- lead, we believe that leadership skills can be improved through practice and reflection.
We improve our thinking by thinking about it and by changing it as necessary.
Asset Mapping (proposed)
How can we work together if don’t know what we have to work with? This applies to our work within CIRAL and to our collaborations with the community.
Research and Reflection (proposed)
In-House Projects (proposed)
Our in-house projects can increase our ability to work on collaborative ones with the community.
While we refuse to engage in the less savory aspects of marketing, we fail if we don’t do our marketing properly.
Institutional Memory (proposed)
Done thoughtfully today, CIRAL participants in the future can easily obtain the information they’ll need tomorrow. “Smart memory” development promotes “smart information retrieval”
http://www.publicsphereproject.org/content/document-centered-discussion Document Centered Discussion] (92)
Online Deliberation (52)
Removing Barriers to Participation (proposed)
Structure, Policy, and Procedures
Pattern Language Master Plan (proposed)
A pattern language has the potential to represent our shared vision from launching the CIRAL project to its development and maintenance and beyond.
Focus and Activity Clusters (proposed)
The simplest way to bring people together is around common interest and projects. We’re calling them clusters and how they form, act, and are evaluated may change over time.
Ground Rules (proposed)
These include the guidelines we’ll use for the Lab and the ones that we’ll use when working with the community. It also must include the ones that Evergreen introduces, such as those about “human subjects”, privacy, research, and intellectual property – among others.
Collaborative Scheduling / Default Meetings (proposed)
Our meetings don’t have to be the same every time but they don’t have to be different either: 30 minutes for faculty time then 60 for student time -- unless we decide differently.
Dynamic Leadership (proposed)
Dynamic Leadership We recognize the roles of leadership while acknowledging that leadership must not be absolute or persistent: thus dynamic leadership is needed in which leadership changes and evolves.
Document Template (proposed)
If we think through what types of information we’ll need, we can design templates that provide a similar look and feel for the lab. It will also make our retrieval job easier.
Service Learning (90)
Citizenship Schools (96)
Project Life Cycle (proposed)
As with other things that are created or that otherwise live, projects have life cycles. The fact that different things are done during different phases of life informs our project work. Research and Reflection Because this is a research – as well as action – project, the research (and reflection) aspect of it must always be present.
Generic Task List (proposed)
In addition to specific tasks we should always maintain a list of generic tasks so that people can feel secure that they’re contributing even when guidance is unclear or unavailable.
Future Design (88)
Diverse Portfolio (proposed)
A diverse portfolio helps provide evidence for comparative research. It also raises that chance that there is something for everybody. Diversity of size, approach, duration, focus, etc.
Relationships (CIRAL & others)
Partnership Life Cycle (proposed)
Like any relationship, from dating to scientific collaboration, there is a natural life cycle. To the extent that we acknowledge this, the higher the likelihood that we are successful.
Rather than have nobody or everybody talking to nobody or everybody, we appoint -- at least informally -- liaisons, who, as part of their job, carry information back and forth between groups.
Covenants help codify the relationships of the various participants including rights and obligations.