📖 Source→⚡ Observation·Where the pattern works/Where the pattern breaks·Interpretation ≠ Conclusion

Cooperation

Cofacilitation

⏱ 4 min

Facilitation is a process of helping groups work cooperatively and effectively. Facilitation can be particularly helpful for individuals who, based on a certain level of insecurity or inexperience, tend to lurk rather than participate. At the same time, in peeragogy, a facilitator isn’t necessarily an “authority.” Rather, facilitation work is done in service to the group and the group dialogue and process. For example, a facilitator may simply “hold space” for the group by setting up a meeting or a regular series of discussions.

Co-facilitating in peer-to-peer learning

Co-facilitation can be found in collaborations between two or more people who need each other to complete a task, for example, learn about a given subject, author a technical report, solve a problem, or conduct research. Dee Fink writes that “in this process, there has to be some kind of change in the learner. No change, no learning” [1]. Significant learning requires that there be some kind of lasting change that is important in terms of the learner’s life; in peeragogy, one way to measure the effectiveness of co-facilitation is to look for a change in the peer group.

Co-facilitation roles can be found in groups/teams like basketball, health, Alcoholics Anonymous, spiritual groups, etc. For example, self-help groups are composed of people who gather to share common problems and experiences associated with a particular problem, condition, illness, or personal circumstance. There are some further commonalities across different settings. Commenting on the work of Carl Rogers:

Godfrey Barrett-Lennard: The educational situation which most effectively promotes significant learning is one in which (1) threat to the self of the learner is reduced a minimum, and (2) differentiated perception of the field of experience is facilitated. [2]

Part of the facilitator’s role is to create a safe place for learning to take place; but they should also challenge the participants.

John Heron: Too much hierarchical control, and participants become passive and dependent or hostile and resistant. They wane in self-direction, which is the core of all learning. Too much cooperative guidance may degenerate into a subtle kind of nurturing oppression, and may deny the group the benefits of totally autonomous learning. Too much autonomy for participants and laissez-faire on your part, and they may wallow in ignorance, misconception, and chaos. [3]

Co-facilitating discussion forums

If peers are preparing a forum discussion, here are some ideas from “The Community Tool Box”, that can be helpful as guidelines:

  • Explain the importance of collaborative group work and make it a requirement.
  • Establish how you will communicate in the forum.
  • Be aware of mutual blind spots in facilitating and observing others.
  • Watch out for different rhythms of intervention.

Co-facilitating wiki workflows

A good place to begin for any group of co-facilitators working with a wiki are Wikipedia’s famous “5 Pillars.”

  • Wikipedia is an encyclopedia.
  • Wikipedia writes articles from a neutral point-of-view.
  • Wikipedia is free content that anyone can edit, use, modify, and distribute.
  • Editors should interact with each other in a respectful and civil manner.
  • Wikipedia does not have firm rules.

Co-facilitating live sessions

Learning experiences in live sessions are described in the article Learning Re-imagined: Participatory, Peer, Global, Online by Howard Rheingold, and many of these points are revisited in the handbook section on real-time tools. But we want to emphasize one point here:

Howard Rheingold: Remember you came together with your peers to accomplish something, not to discuss an agenda or play with online tools; keep everything as easily accessible as possible to ensure you realize your goals.

References

  1. Fink, L. D (2003). /Creating significant learning experiences: An integrated approach to designing college courses/. John Wiley & Sons.

  2. Barrett-Lennard, G. T. (1998). /Carl Rogers’ Helping System: Journey & Substance/. Sage.

  3. Heron, J. (1999). The complete facilitator’s handbook. London: Kogan Page.

⚡ Unpeeragogy · Friction · Observation

Co-facilitation Is a Burden

⏱ 4 minaudit-v2cofacfacilitationgroup

The Assumption

Co-facilitation distributes authority and prevents single points of failure in peer learning groups. When multiple people share facilitation duties, the group becomes more resilient and democratic. Shared facilitation naturally produces better outcomes through distributed responsibility.

Operational Reality

Two facilitators sit across from each other in a meeting that started late. The group they are supposed to guide dissolved weeks ago — half the members stopped showing up, the other half argue in private channels about who is actually in charge. This is not peer learning failing. This is co-facilitation eating itself.

Not shared leadership. Not distributed authority. Not collective wisdom. Co-facilitation becomes a performance of equality that nobody can afford to maintain. The work doubles while the clarity halves — two people checking with each other before every decision, two people responsible when things fall apart, two people who cannot move fast enough to catch problems before they metastasize.

Perturbatore: “What if the burden of co-facilitation is not the extra coordination, but pretending authority does not exist when someone always ends up holding it anyway?”

Two chairs. One decision. No one sits.

The peer learning experiments that lasted more than six months did not distribute facilitation — they concentrated it, then built systems around that concentration that looked like distribution.

P2PU shows that role clarity — not distributed ambiguity — enables resilience. OpenStreetMap shows that some conflicts require singular authority, not shared facilitation. Drupal shows that distributing authority is a multi-year structural project, not a facilitation choice. The IETF shows that even the most peer-driven bodies need singular appeals paths — co-facilitation without backup is organized procrastination with extra meetings.

Empirical Evidence

Resilience Cases (Confirming):

  • P2PU Learning Circles — Peer learning models with defined facilitator roles and institutional partnerships are more sustainable than purely peer-driven learning. Role clarity — not distributed ambiguity — enables resilience.
  • OpenStreetMap Data Working Group — Formal dispute resolution bodies with binding authority resolve conflicts that informal consensus cannot. Some conflicts require singular authority, not shared facilitation.

Fracture Cases (Complicating):

  • Drupal Governance — Governance transition from BDFL to community model required years of structural work. Distributing authority is a multi-year structural project, not a facilitation choice.
  • IETF About — Rough consensus governance only works when backed by hierarchical escalation paths. Even the most peer-driven bodies need singular appeals paths — co-facilitation without backup is organized procrastination with extra meetings.

Operational Heuristics

Positive Boundary: Apply co-facilitation only when supported by formal dispute resolution mechanisms and institutional continuity — institutional partnerships and hierarchical escalation paths make shared facilitation sustainable.

Negative Boundary: Do not apply co-facilitation when the group lacks formal escalation paths or institutional support — consensus without appeals creates irresolvable conflicts, and two facilitators without authority are worse than one with authority.

Epistemic Synthesis

The theoretical assumption — that distributing facilitation increases resilience and democracy — is systematically contradicted. Every successful case in the archive concentrated authority, then built systems around that concentration that resembled distribution. Co-facilitation without backup is organized procrastination with extra meetings.

Evidence Status

Status Count
Confirmed cases 2
Cases under study 2
Unverified cases 0
Ambiguous cases 0

Traceability

Run: audit-v2 · Delta: 1.3 → 1.3319 · Diversity D: 2

References

💬 Field Report: Co-facilitation Is a Burden

Every pattern in the Handbook has been tested in the real world — and the real world usually has something to say about it. If you tried something similar, or saw it fail differently, share the story here.

Write in your native language — the browser will translate. Lowering the entry barrier is more important than choosing the "right" language. GitHub translates threads automatically so everyone can follow along.
Read how evidence is collected →

✏️ Share your story🔍 Structural analysis📋 Browse field reports
What happens after I share my story?

1. Your post appears in GitHub Discussions in the Field reports category.

2. Once a week, the project reads new threads and checks for patterns worth integrating.

3. If your story reveals a new Failure Vector, a revision to tension_index, or a sharper edge for the Perturbator — the entry gets updated.

4. The change is logged at /log and goes live on the next deploy.

Don't have a GitHub account? Here's how it works

GitHub Discussions is free. You need a GitHub account (30 seconds to create one).

Once you're signed in, click "Share your story" above. Write in your own language — the thread will be translated for everyone else automatically.

You don't need to know how to code. You don't need to know what "git" is. You just need an observation that the theory didn't match reality.

What are GitHub Discussions? →

Every pattern raises more questions than it answers.
Read the theory. Then look at what happened.

🗂️ Browse all patternsWhy this project? →← Back home