Blue Cadence · Technical Support Technology

Professional Learning Groups

A working guide for members, facilitators, and practitioners — grounded in three decades of research on professional learning communities, critical friends, and team learning.

If you have just been invited into a Professional Learning Group, read this stage before your first meeting. It is short on purpose. The whole point of a PLG is that the work happens between people, not on a page; the page just gets you ready to walk into the room.

1. What a Professional Learning Group Is — and What It Is Not

A Professional Learning Group is a small, recurring meeting of practitioners — typically five to twelve people — who commit to improving their own work by presenting it to one another and asking for structured feedback. The group meets on a fixed cadence over a long enough period (usually at least one academic year, or six to twelve months in a workplace setting) that the members come to trust each other, recognize each other's recurring questions, and feel the cumulative effect of having their practice examined again and again by people who are not their boss.

A PLG is not a training course. Nobody in the room is positioned as the expert who delivers content. A PLG is not a status meeting. Nobody is reporting up. A PLG is not a venting circle. It does not exist to validate frustrations. And a PLG is not a brainstorming team. Its primary unit of work is not the group's collective idea but one member's actual artifact — a lesson, a design document, a proposal, a customer call, a piece of code, a manuscript, a difficult decision — looked at carefully by the others.

What the group does, week in and week out, is treat one another's real work as the most interesting thing in the room. The group's job is not to fix the work. The group's job is to help the person who brought the work see it more clearly than they could see it alone.

2. The Posture of a Member: Inquiry Over Advice

The hardest thing to learn as a new PLG member is that your most useful contribution is almost never your advice. It is your questions and your noticing. Members who arrive with strong opinions and a habit of dispensing them tend, in their early sessions, to feel slightly underused. That feeling is correct, and it is part of the design. You are being asked to do a different kind of work.

The posture the group asks of you has three parts. First, treat every artifact presented as the product of a thoughtful colleague who has already considered the obvious moves. If you find yourself thinking, "Have they tried X?" — assume they have. Ask what they tried and what happened. Second, separate your reaction to the work from your reaction to the person who brought it. The work is what is on the table; the person is your colleague. Third, recognize that the presenter, not you, is in the best position to decide what to do next. Your job is to help them think, not to tell them what to think.

This posture has a name in the literature: peer inquiry. It is not the posture of mentorship, and it is not the posture of management. It assumes the presenter is the protagonist of their own practice, and that the group exists to give that protagonist a higher-resolution view of the situation they are already inside.

3. Customs of Membership

Attendance

Attendance is the single most consequential commitment you make. Groups that meet monthly cannot tolerate frequent absence; if you miss two sessions in a row, the group's trust in your presence begins to thin, and so does your read on what is happening for the other members. If you cannot make a session, tell the facilitator in advance, and read whatever materials the next presenter circulates so you arrive at the following session current.

Preparation

Before each session, the presenter circulates a short document: the artifact itself (or a description of it) and a focusing question — the specific thing they want the group to help them see. Read it. Come with notes. Twenty minutes of pre-reading is the difference between a session that helps the presenter and a session that wastes their turn.

Presence

During the meeting, close your laptop unless you are taking notes. Put your phone face down. The protocols you will learn depend on people listening for extended uninterrupted stretches; a member who is half-attending makes the silent listening time noticeably more uncomfortable for the presenter, who is watching the room while their work is discussed.

Confidentiality

What is said in the group stays in the group. This is not a legal commitment; it is a working condition. Members will only present the work they are uncertain about — the half-finished, the awkward, the dilemma they have not yet resolved — if they trust that nothing they say will be repeated outside the room in a way that could embarrass them. If you are unclear whether something is shareable, ask the presenter.

Turn-taking

Every member presents. Over the course of the year, the rotation is roughly equal. Members who consistently consume the group's attention but never bring their own work, or who decline their turn when it comes, weaken the contract. If you are uncertain about what to bring, talk to the facilitator; almost any real piece of practice is a candidate.

4. Responsibilities of a Member

Three responsibilities follow from membership.

5. The Kinds of Feedback That Belong in the Room

PLGs run on three modes of feedback, which the literature on the Tuning Protocol calls warm feedback, cool feedback, and probing questions. Each does a different job. A good session uses all three; sessions that drift into only one usually misfire.

Warm Feedback

Warm feedback names what the work is doing well — specifically and concretely. Its purpose is not to make the presenter feel good. Its purpose is to help the presenter see strengths they may be too close to the work to notice, so they can build on them deliberately rather than accidentally.

A good warm comment is anchored in something specific in the artifact:

"The way you ended the customer call by repeating their problem back in their own words — that's why they agreed to the follow-up. The earlier paraphrasing in our own technical terms wasn't moving them."

That comment is warm because it identifies a strength, but it is useful because it points to the exact place in the artifact where the strength is operating. "Great call" is warm; it is not feedback.

Cool Feedback

Cool feedback names where the work is not yet in tune with its own stated goal. The word "cool" is deliberate: not cold, not harsh — just dispassionate. Cool feedback is at its strongest when it is offered as a question or as a noticing rather than a verdict.

"I noticed that the focusing question was about whether the technician would feel supported, but the script doesn't include any moment where the technician's existing knowledge is acknowledged. Is that intentional?"

That is cool feedback. It identifies a gap, it ties the gap to the presenter's own focusing question, and it leaves the presenter room to say, "Yes, here's why," or "No, that's the thing I missed." Cool feedback is the heart of the group's value; without it, the group is a support circle.

Probing Questions

Probing questions are open-ended, non-leading, and aimed at helping the presenter think more deeply about their own situation. They are not Socratic traps. A probing question does not have a right answer the asker is steering toward. It is a genuine inquiry into the presenter's reasoning, context, or assumptions.

"What would have to be true for this approach to fail?"
"What did you notice about your own reaction in that moment?"
"Whose voice is missing from the artifact?"

If you can already guess the answer the asker wants, it is not a probing question — it is advice in disguise. Try again.

6. The Kinds of Feedback That Do Not Belong

The following modes of contribution are prohibited in a PLG, not because they are necessarily bad in other contexts, but because they corrode the specific kind of work the group is trying to do. New members will catch themselves wanting to do all of these. That is normal. Catching yourself before you do them is the practice.

Unsolicited Advice and Fix-it Comments

"What you should do is —" is the most common form of contribution from new members, and it is the most damaging. It collapses the presenter's role as the protagonist of their own practice. The presenter knows their context better than you do; if they wanted your prescription, they would have asked for it. Convert your advice into a question: not "You should add a follow-up survey," but "Have you considered what a follow-up survey would tell you that you don't already have?"

Personal Critique

Comments about the presenter as a person rather than about the work are out of bounds. "You always do this" is personal critique. "This artifact does this" is feedback. The distinction matters because the work can be changed; the person, in the time the group has, cannot. The group's contract is with the work.

Comparison and Ranking

Comparing the presenter's work to someone else's work — favorably or unfavorably — is prohibited. "Last month's case was clearer than this one" puts members into competition. The group is not a tournament. Each presenter's work is examined on its own terms in service of that presenter's focusing question.

Hijacking

"When this happened to me…" is a hijack. Your similar experience may be relevant, but if it consumes the air, you have turned the presenter's session into your session. If you genuinely think your experience is useful, offer it as a question: "Would it be useful to hear what happened when I tried something like this?" — and accept the answer, including "not right now."

Rescue and Saviorism

A presenter who appears uncomfortable does not need to be rescued. Discomfort is sometimes the work. If you notice yourself wanting to soften every cool comment with a hasty warm one, or to step in and answer for the presenter, sit on your hands. The facilitator is watching the room; let them manage tone.

Vague Praise

"This is great" and "I love it" are not warm feedback. They are vague enough that the presenter cannot do anything with them. If you cannot say what specifically is working in the artifact, your warm comment is not yet ready. Sit with it; the specific version will come.

Speaking for the Presenter

"What I think they meant was —" is out of bounds when the presenter is in the room. In the protocols you will use, there are stretches when the presenter is intentionally silent. Those stretches are not an invitation to ventriloquize them. Speak only for yourself; let the presenter speak when their turn comes.

Comments About the Group Itself

Meta-commentary about the format ("We never get anywhere in these meetings") belongs in the debrief at the end of the session, not in the middle of someone's presentation. If you have a concern about the process, save it; the debrief is when the group revises its own customs.

7. The Presenter's Stance: How to Receive Feedback

When it is your turn to present, your job is to listen well, not to defend. The protocol will require you to be silent during the warm and cool feedback rounds. This silence is not a punishment; it is the design. It removes from you the burden of responding in real time and gives you space to hear comments you would otherwise argue with.

Three habits help.

Above all, bring something you are actually uncertain about. Members can tell when a presenter has brought a piece of finished work to be admired rather than examined; the session falls flat, and the presenter goes home with nothing they did not already have. Bring the half-built thing. The unfinished work is what the group can help with.

8. Confidentiality and Trust

The group's usefulness is bounded by how honest its members can afford to be. Members can only present the work they are uncertain about if they trust that what they say will stay in the room. This applies to the artifacts themselves, the focusing questions, the comments members make during the protocol, and — especially — the personal disclosures that sometimes accompany a piece of practice.

If you are asked to take notes or write a summary for your own learning, that is fine. Do not circulate it. If you find yourself wanting to mention something from the group in a conversation outside, ask yourself whether the person who brought it would be comfortable hearing you talk about it. If you are not sure, don't.

9. A Member's Promise

In one paragraph, this is the commitment a PLG member makes:

I will come on time and prepared. I will read what the presenter circulates. I will give the kind of feedback that helps the presenter see their own work more clearly — warm, cool, and inquiring — and I will not give advice unless asked, compare members to each other, or speak for the presenter when the protocol asks me to listen. I will take my turn to present, and when I do, I will bring real work that I am uncertain about. What is said in the room stays in the room.

This stage is written for the person who will convene and hold a Professional Learning Group. It assumes you have read Stage I; the customs there are what you are now responsible for teaching, protecting, and modeling. Stage II covers the practical mechanics — recruiting, scheduling, running the first sessions — and then turns to the harder craft: holding the room when it does not want to be held, sustaining momentum across a long cycle, and recognizing when to end.

1. The Facilitator's Role and Posture

A PLG facilitator is not a content expert, not a chair, and not a referee. The clearest analogue in the literature is the Critical Friends Group coach: someone trained to use a small set of structured conversations — protocols — to make peer learning possible. The facilitator's authority comes from holding the process, not from holding the answers.

In a well-functioning session, the facilitator says little. They open, they keep time, they remind the group of which stage of the protocol it is in, they intervene when a norm is breached, and they close with a short debrief. The temptation, especially for facilitators who come from training or coaching roles, is to over-talk — to add insight, summarize, smooth, encourage. Resist it. Every sentence the facilitator adds is a sentence a member did not have to find. The group's growth depends on the members finding their own sentences.

Two postural commitments are worth naming explicitly. The first is multipartiality: the facilitator is on every member's side at once, including the presenter's and including the members offering hard feedback. The facilitator is not the presenter's defender; nor is the facilitator the group's prosecutor on the presenter's behalf. The second is restraint: the facilitator's strongest move is usually to say less than they want to say.

2. Recruiting: Who Belongs in the Group

Size

Five to twelve members is the durable range. The Critical Friends Group tradition has converged on this range for good reason: fewer than five and a single absence destabilizes the room; more than twelve and members do not get to present often enough to feel the cumulative effect, while the protocols stretch past their useful length. For new facilitators, aim for seven to eight. That gives you a working group even when two members are out and keeps the protocols comfortably within a two-hour session.

Composition

PLGs work best when members share a domain of practice but bring different angles into it. A group of all senior practitioners can become an echo chamber of received wisdom; a group with too much status mixing — supervisors and direct reports in the same room — struggles with candor, because the cool feedback channel collapses against the reporting line. Some heterogeneity is good and some is structurally toxic. The screening question is: can each member afford to be uncertain in front of the others?

In workplace settings outside education, the most common configuration that works is a cross-functional group of peers — same band, different teams or different sites — convened around a shared kind of work (a customer-facing role, an engineering practice, a clinical specialty). The most common configuration that fails is a single intact team whose manager is also in the room. If you cannot avoid having the manager in the room, name the dynamic openly in the norms session and recognize that the group will need longer to reach honest cool feedback.

The Invitation

Recruit individually. A group announcement gets the wrong members — the eager joiners who like meetings — and misses the right ones, who are usually mid-career practitioners who are skeptical of one more program. A short individual conversation, in which you describe what a PLG actually is (a small group looking at each other's real work) and what it is not (training, a project team, a status meeting), tends to surface a self-selecting cohort that will take the work seriously.

Be explicit about the time commitment in the invitation. People who agree to a one-year commitment when they thought they were agreeing to a one-quarter commitment will resent the format, and their resentment will leak into the group.

3. Scheduling: Cadence, Duration, Number of Sessions

Frequency

Once a month is the standard cadence in the Critical Friends Group tradition, and it is the right default. Less often than that, the group loses continuity — members forget what was discussed last time, the presenter rotation drags out across calendar quarters, and the relationships do not deepen. More often than that, members cannot prepare adequately, and the group degrades into low-effort meetings that nobody respects.

Some groups, especially in workplaces where the work is fast-moving, find that every three weeks gives more momentum without overloading prep. Avoid weekly. Weekly cadence is rarely about the group's learning needs; it is usually about a sponsor's anxiety, and it converts the group into a status check.

Session Length

Two hours is the working length. Ninety minutes is the floor; below it, the protocols cannot run cleanly. Three hours is the ceiling; beyond it, fatigue degrades the quality of feedback noticeably, and members start looking for the exit during the final round. A two-hour session typically accommodates one full Tuning or Consultancy Protocol (about 65–75 minutes), one shorter activity or check-in, opening and closing, and a real debrief.

Number of Sessions in a Cycle

A full cycle should be long enough for every member to present at least once and for the group to feel the difference between an early session and a late one. In practice, that means a minimum of eight sessions and a comfortable working length of ten to twelve. In an academic-year cadence, that is monthly from September through May with a short break in December. In a workplace cadence, ten months of monthly meetings or eight months at a three-week cadence are common.

Avoid open-ended PLGs that drift forever. A defined cycle — with a known start, end, and renewal decision — generates better attention and better closure. Members can re-enlist at the end of the cycle, but they should have to re-enlist.

First and Last Sessions Are Different

The first session is dedicated to norms-setting, an experiential introduction to a protocol (usually a short one), and the presenter rotation. Do not let a member present substantive work in the first session; the group has not yet earned the trust to receive it well. The last session is dedicated to a closing protocol that names what each member is taking with them and what the group did well; the affective work of closing matters, especially if the cycle has been long.

4. Teaching the Process: The Opening Cycle

New PLG members do not arrive knowing how to be in a PLG. They arrive knowing how to be in meetings, which is a different and partially incompatible skill. The first two or three sessions are where the format is taught — not lectured, but practiced. Sequence matters.

Session 1: Norms and a Light Protocol

In the first session, do four things, in order. First, surface the group's hopes and concerns for the year — a short go-around in which each member says what they want from the group and what they are worried about. Second, co-construct norms; do not hand them down. The members' own words are more durable than yours, and the act of constructing them is what produces buy-in. Third, run a short, low-stakes protocol — the Compass Points or Connections protocol from the NSRF library are good choices — so the group experiences the rhythm of a structured conversation without anyone having to expose real work. Fourth, set the presenter rotation.

Session 2: First Real Presentation, with Scaffolding

In the second session, the first presenter brings real work. The facilitator's job is to over-scaffold: announce each stage of the protocol explicitly ("We are now in clarifying questions; clarifying questions are short and factual"), interrupt early drifts gently but visibly, and debrief at length at the end. The debrief is where members learn what just happened. Without a debrief, the experience is opaque.

Sessions 3–5: Establishing the Rhythm

By session three the group has run the protocol once. By session five, it has run it three times. The facilitator's interventions can shrink. Members start to police themselves — a member who starts giving advice will be caught by another member, not by the facilitator. This handoff of process-holding from the facilitator to the group is what makes the format sustainable; it is also one of the surer signs that the group is healthy.

5. Why the Format Works: The Theory of Action

It is worth being able to articulate to a skeptical member, or to a sponsor, why this format — which on the surface looks like a slow and ceremonial way to have a conversation — actually produces learning that ordinary collegial conversation does not. There are four mechanisms, all of them supported by the research summarized in Stage III.

Protocols Slow Down Reactivity

In ordinary professional talk, the first response to a colleague's problem is usually advice — fast, well-meant, and often misaligned with what the colleague actually needs. The Tuning Protocol's stipulated silences, ordered stages, and presenter-quiet rounds break this reflex. By the time a member is permitted to offer cool feedback, they have heard the focusing question, examined the artifact, asked clarifying questions, and listened to other members' warm comments. Their cool comment is, in consequence, better aimed.

De-privatization of Practice

Most professional work is done alone, presented only in finished form, and never seen at the messy middle stage by another practitioner. The literature on teacher communities calls the opposite condition de-privatization of practice (Little, 2003; Stoll et al., 2006). The PLG creates de-privatization in a controlled way: members present their work in a setting where exposure is reciprocal and predictable. Over a cycle, members come to treat their own work as legitimately public among this small group, and the quality of self-critique improves accordingly.

Reciprocity Produces Psychological Safety

Edmondson's research on team learning shows that the precondition for honest feedback is psychological safety — a shared belief that the team is safe for interpersonal risk-taking. Psychological safety is not produced by exhortation; it is produced by the experience of taking small risks and not being punished. The protocols engineer small risks (the presenter exposes a piece of work, the member offers a cool comment) and engineer them into a setting where they are reliably received well. Trust accumulates from session to session because the format makes it earn its accumulation.

The Group Develops Its Own Repertoire

Wenger's notion of a Community of Practice depends on a shared repertoire: the stories, tools, phrases, and tacit understandings that emerge from sustained joint work. A PLG running over a year develops a private vocabulary — references to past members' dilemmas, shared phrases for recurrent patterns, calibrated standards for what constitutes a good focusing question — and that vocabulary is one of the group's most valuable outputs. New members joining a second-year group will not have access to it for several sessions; this is expected.

6. Running the Tuning Protocol

The Tuning Protocol, developed by Joseph McDonald and David Allen at the Coalition of Essential Schools in 1992, is the workhorse format of the PLG world. A version of it is run in nearly every NSRF Critical Friends Group session and in most PLGs that have inherited the tradition. It exists in many minor variants; the version below is durable across settings.

Stage 0: Pre-Circulation (in the days before)

The presenter circulates the artifact and a one- or two-sentence focusing question. The focusing question is the lever; if it is vague, the session will be vague. Help the presenter sharpen it before the session begins.

Stage 1: Introduction (3 minutes)

The facilitator names the protocol, the stages, the total time, and the focusing question. The facilitator reminds the group of the warm/cool distinction. Brief; ceremonial; sets the tone.

Stage 2: Presenter Frames the Work (10–15 minutes)

The presenter describes the artifact, the context it sits inside, and the focusing question. The group listens silently. Members may take notes; they do not interrupt. The presenter's job in this stage is not to defend the work but to give the group what they need to engage it.

Stage 3: Clarifying Questions (5 minutes)

Members ask short, factual questions — "How long is the document?", "Who is the audience?", "When did this happen?" — that the presenter can answer briefly. Clarifying questions are not opinions in disguise. Facilitator: if a clarifying question begins with "Why didn't you —", redirect it. That is a probing question and belongs later.

Stage 4: Examination of the Artifact (5–10 minutes)

The group reads, watches, or examines the artifact silently with the focusing question in mind. Members take notes on what is in tune with the focusing question (warm material) and where it is not yet (cool material). Presenter is silent.

Stage 5: Warm and Cool Feedback (15–20 minutes)

This is the heart of the protocol. The group discusses the work; the presenter is silent and takes notes. Convention: the group speaks of the presenter in the third person, and the presenter physically turns slightly away from the group or otherwise breaks eye contact. This is not a stunt; it is a tested device that reduces the group's tendency to soften feedback to manage the presenter's face.

Begin with three to five minutes of warm feedback, then move to cool, then move flexibly between them. Probing questions are welcome in this stage and often produce the most useful feedback. The facilitator may need to balance the channels: if the group is all-warm, ask explicitly for cool comments; if all-cool, ask what is working.

Stage 6: Presenter Reflects (5–10 minutes)

The presenter speaks; the group is silent. The presenter is not required to respond to every comment. They are asked to share what they heard, what landed, what they want to think more about. The presenter does not have to defend or rebut. If the presenter starts arguing with the feedback, the facilitator may gently redirect: "Hold those for the debrief."

Stage 7: Debrief (5–10 minutes)

The group, including the presenter, debriefs the experience of the protocol itself. How did it feel? What was useful? What got in the way? The debrief is where the group revises its own customs and where the facilitator catches drifts before they harden. Never skip the debrief; the temptation to run over time and drop the debrief is the single most common facilitator mistake.

7. Variations: Other Useful Protocols

The Tuning Protocol is the default. The following variations cover most other situations a PLG will encounter.

The Consultancy Protocol

Best when the presenter brings a dilemma rather than an artifact — a stuck situation, a relational conflict, an open question. The structure is similar to the Tuning Protocol but oriented around a dilemma statement; the group's feedback is framed as ideas, options, or reframings rather than warm/cool comments on a piece of work. The Consultancy is the right choice when the presenter cannot describe what they would do with feedback on the artifact, because they do not yet know what the artifact should be.

The Charrette Protocol

Best when the presenter is genuinely stuck and wants the group's help generating options early in a project. The Charrette is more collaborative and less ceremonial than the Tuning; the presenter is permitted to remain in the conversation. Use it sparingly; it is easy to slip into ordinary brainstorming and lose the structure.

The Issaquah / Final Word Protocol

Best for processing a shared reading or piece of evidence rather than a member's artifact. Each member identifies a passage and reflects on it in turn while others listen silently; the originating member gets the final word. Good for keeping the group's intellectual diet varied.

The Compass Points / Connections

Light opening protocols that work well in the first session of a cycle or after a long break. They surface differences in working style and reset the group's attention without requiring anyone to expose work.

8. Norms-Setting and Trust-Building

Norms are not posters. They are the working agreements the group will fall back on under stress, and they need to be the group's own agreements, not imported from elsewhere. The first session's norm-setting should produce a short list — five to eight items — generated by the members, written down, and revisited at least twice during the cycle.

Useful norms tend to share two qualities: they are stated as commitments rather than rules, and they are specific enough to enforce. "Be respectful" is not a norm; it is a wish. "Speak from your own experience, not for others" is a norm. "Read the materials before the session" is a norm. "Hold the protocol stages" is a norm.

Revisit norms openly. Twice in a cycle, devote ten minutes at the start of a session to checking the norms against the group's recent behavior. If a norm is being routinely broken, name it; if a norm has fallen out of use because the group no longer needs it, retire it. Living norms outperform laminated ones.

9. Difficult Situations and How to Handle Them

Every PLG facilitator encounters the following situations. Naming them in advance, and having a planned response, is much of the craft.

The Advice-Giver / Fixer

One member keeps offering prescriptions. Public correction shames them; private silence allows it to continue. The middle path is the redirect-in-stage: "Hold that — let's frame it as a probing question. What are you wanting to learn from the presenter about that?" Said twice in a session, three times across two sessions, this teaches the member to convert prescriptions into inquiries without singling them out. If it continues past the third session, have a private conversation between sessions; the issue is rarely malicious and usually reflects a habit from another context.

The Hijacker

The hijacker turns every comment into a story about themselves. Mild cases respond to the same redirect-in-stage: "Let's hold that for now and stay with what's in front of us." Persistent cases need a private conversation, usually framed around what the hijacker is trying to contribute. Often they are trying to be helpful and do not realize what they are doing; sometimes they are managing their own anxiety about being on the receiving end when their turn comes.

The Silent Member

Some members listen more than they speak; this is fine. The problem is the member who is silent because they are disengaged, or silent because they feel they cannot afford to speak — a junior member in a group with senior members, for example. The diagnostic is to ask, between sessions, what would help them participate more. Sometimes the answer is structural (assign a role: notetaker, timekeeper, debrief opener), sometimes relational (acknowledge the status differential and rebalance the room's air), sometimes individual (they are introverted and prefer the silent rounds). Do not call on a silent member in the middle of a protocol; it is the worst place to expose them.

The Defensive Presenter

The presenter argues with cool feedback in real time, or pre-rebuts comments before they are offered. This usually signals one of three things: the presenter brought work they were not actually uncertain about (the protocol becomes a performance); the cool feedback is hitting a place the presenter is not ready to expose; or the group's trust has not yet built up to the level the protocol assumes. The intervention depends on which. If the work was a performance, debrief openly: "What would have to be different for you to bring a piece you're actually unsure about?" If the trust is the issue, slow the next session down; do not press forward.

The Under-Prepared Presenter

A presenter shows up without an artifact or without a focusing question. The temptation is to absorb the loss and run a half-strength session. Resist it. The under-prepared presenter signals to the group that the contract is optional; honoring it teaches the opposite. Move the presenter slot, run a shorter activity, and have a private conversation about what blocked the preparation. Usually the answer is more about workload than indifference; the response is to scale the artifact, not the standard.

Status Differentials in the Room

When senior and junior members are in the same group, junior members are systematically under-heard, and their cool feedback to senior members is systematically softened. The most direct intervention is to name this dynamic openly in the norms session and to design small structural counterweights: junior members open the warm-feedback round, senior members offer the first cool comment about their own work in the debrief. Over a cycle, the dynamic eases; in a first cycle, it never fully disappears.

Conflict Between Members

Two members start needling each other in feedback, the comments are stretched past what the work warrants, and the room gets quieter. Pause the protocol and name what you are seeing: "I want to slow down for a moment. The last few comments have started to feel like they're about something other than the work in front of us. Can we check in?" This is uncomfortable to do and almost always the right move. If the conflict has roots outside the group, the group is not the place to resolve them; suggest an offline conversation, and reset the protocol.

When the Group Turns on the Facilitator

Occasionally — usually around session four or five — a group will critique the facilitator: too rigid with the protocol, too soft with a difficult member, too slow with the debrief. Receive it the way the protocols ask the presenter to receive feedback. Listen. Do not defend. Take notes. Pick one or two threads. The fact that the group is willing to do this is a strong sign of the group's health, not its decay.

10. The Philosophy That Sustains the Group

Hard situations do not get easier because the facilitator has more tactics. They get easier because the facilitator has a stable philosophy of what the group is for. Three commitments make the philosophy practicable.

First, the presenter is the protagonist of their own practice. The group exists to help them see more clearly, not to take their decisions from them. Even when the group is offering its sharpest cool feedback, it is offering it in service of the presenter's own work, on the presenter's own terms. This commitment, which runs through the Critical Friends Group tradition and which is congruent with both Narrative Therapy and Motivational Interviewing, is what keeps the room from becoming a tribunal.

Second, the work is separable from the worker. A piece of practice can be examined critically while the person who produced it is treated as a respected colleague. This separation is harder than it sounds, and it is the discipline the group most often fails. The facilitator's job is to keep restoring the separation, sometimes by language ("the artifact does X" rather than "you did X"), sometimes by procedure (the presenter-silent rounds), sometimes by direct intervention.

Third, the format is for the work, not the work for the format. If a protocol is not serving a presenter on a given day — the artifact is the wrong size, the focusing question is wrong, the group is tired — adapt. The Tuning Protocol is a default, not a sacrament. The discipline is to know why you are breaking it when you break it, so that the break is intentional rather than slippage.

These three commitments are what the facilitator returns to when a session goes badly, when a member walks out, when a sponsor asks why the format takes so long. They are not slogans. They are operating principles, and they are what the group will feel when it does not consciously feel anything at all.

11. When Momentum Wanes

Every PLG hits a stretch where attendance softens, presentations feel routine, and the group's energy thins. This usually happens between sessions five and seven — past the novelty of the first cycle, before the consolidation of the final stretch. It is normal and does not mean the group is failing. It does mean the facilitator has to intervene.

Several moves work. They are listed in order of how disruptive they are; try lighter ones first.

Do not respond to the dip by tightening the protocol or by adding rules. The dip is rarely a discipline problem; it is a stimulation problem. Adding rules makes it worse. Refreshing the material makes it better.

12. Closing the Cycle and Deciding What's Next

A cycle should end deliberately. In the last session, run a closing protocol — the "What I Take With Me" protocol or a structured go-around in which each member names one thing the group helped them see — and use the debrief to discuss what should change in the next cycle if there is one.

Then ask the renewal question explicitly: who is in for another cycle, who is out, and what would the new cycle look like? Some members will leave. Some will return with different intentions. New members may join. Do not roll the group forward by default; the act of recommitting is what the next cycle needs in order to start with the right intensity.

If the group does not renew, that is also a successful outcome. A PLG that ran for one cycle, gave its members what they came for, and ended cleanly is a more durable contribution than a PLG that limped on for three years past its useful life.

This stage documents the research base behind the customs, protocols, and facilitation choices recommended in the Member and Facilitator stages. It is intended for readers who need to defend the design to a budget owner, a sponsor, an academic committee, or a skeptical colleague.

1. The Conceptual Lineages of Professional Learning Groups

The phrase "Professional Learning Group" sits at the convergence of three distinct but compatible research traditions, each of which contributes part of the design and none of which is sufficient alone.

The first is the Professional Learning Community (PLC) tradition rooted in U.S. educational reform. The seminal articulation is Hord (1997), whose synthesis of the literature identified five dimensions of an effective professional learning community: supportive and shared leadership, shared values and vision, collective learning and its application, supportive conditions (both structural and relational), and shared personal practice. DuFour (2004) sharpened the framework into three "big ideas" — a focus on learning rather than teaching, a collaborative culture and collective responsibility, and a results orientation — and warned that the term was already at risk of dilution from overuse. The DuFour and Eaker (1998) book Professional Learning Communities at Work moved the concept from research literature into widespread practice in U.S. schools.

The second is the Critical Friends Group (CFG) tradition originated in 1994 by the National School Reform Faculty at the Annenberg Institute for School Reform, later housed at the Harmony Education Center in Bloomington, Indiana. Critical Friends Groups are themselves a particular variety of professional learning community, distinguished by two features: an intentional cultivation of safety and trust among members, and the use of structured conversations — protocols — to accomplish specific learning goals. The NSRF and its successor organizations have developed and refined more than 200 protocols since 1994, of which the Tuning Protocol (Allen and McDonald, 1992; McDonald, Mohr, Dichter, and McDonald, 2013) is the most widely used. Curry (2008), in a Teachers College Record study, examined four design features of CFGs — diverse menu of activities, decentralized structure, interdisciplinary membership, and reliance on protocols — and found that CFGs enhanced teachers' collegial relationships, awareness of research-based practices, schoolwide knowledge, and capacity to undertake instructional improvement, while also showing the tensions inherent in the format.

The third is the Community of Practice (CoP) tradition developed by Lave and Wenger (1991) in Situated Learning and elaborated by Wenger (1998) in Communities of Practice: Learning, Meaning, and Identity. The CoP framework defines three constitutive elements: a domain (a shared area of interest that gives the community identity and to which members are committed), a community (the people who care about the domain and engage with one another), and a practice (the shared repertoire of experiences, stories, tools, and ways of addressing recurring problems that members develop over time). Wenger, McDermott, and Snyder (2002), in Cultivating Communities of Practice, extended the framework explicitly to workplace and organizational settings.

These three lineages overlap substantially. Stoll, Bolam, McMahon, Wallace, and Thomas (2006), in their authoritative literature review for the Journal of Educational Change, treated them as variations on a common phenomenon — the professional community — while noting the differences in emphasis. The PLC tradition emphasizes shared goals and collective inquiry oriented toward measurable outcomes; the CFG tradition emphasizes structured conversation and individual practitioner reflection; the CoP tradition emphasizes identity, social learning, and the slow accretion of shared repertoire. A well-designed PLG draws on all three.

2. Hord's Five Dimensions and DuFour's Big Ideas

Hord's (1997) five dimensions — supportive and shared leadership; shared values and vision; collective learning and its application; supportive conditions; and shared personal practice — provided the first empirically grounded operational definition of a PLC. The dimensions were developed through a synthesis of an extensive literature review conducted at the Southwest Educational Development Laboratory (SEDL), and they remain the basis of the most widely used PLC self-assessment instrument, the Professional Learning Community Assessment-Revised (PLCA-R).

DuFour's (2004) three big ideas — focus on learning, collaborative culture, results orientation — are best read as a more action-oriented restatement of Hord, designed for school leaders implementing the concept rather than researchers studying it. DuFour's later work with Reeves (2016) emphasized that PLCs are not events or programs but ongoing processes characterized by recurring cycles of collective inquiry and action research.

For workplace PLG design, the most consequential element of Hord's framework is the explicit pairing of structural conditions (time, space, scheduling, proximity) with relational conditions (trust, openness, respectful relationships). PLGs fail more often from neglected structural conditions — meetings squeezed into thirty minutes between other obligations, members joining by phone from cars — than from any failure of intention.

3. Critical Friends Groups and the Protocol Tradition

The Critical Friends Group concept was developed in 1994 by the National School Reform Faculty as a way to ground professional collaboration in safe, focused, protocol-mediated conversations among small groups of educators. The defining features, articulated in the NSRF's own materials and confirmed in Curry's (2008) empirical study, are: groups of five to twelve members; monthly meetings of approximately two hours; a certified coach trained to facilitate; a focus on solving problems and accomplishing goals brought by the participants themselves; and reliance on protocols — structured conversations that allocate turns, time, and roles in deliberately atypical ways.

The Tuning Protocol, the original protocol of the tradition, was developed in 1992 by Joseph McDonald and David Allen at the Coalition of Essential Schools, initially as a means for five high schools in the Coalition's Exhibitions Project to receive feedback on their developing student assessment systems (Allen and McDonald, 1993). It has since been documented, refined, and extended in McDonald, Mohr, Dichter, and McDonald's The Power of Protocols (2013, revised 2015), which remains the canonical reference for protocol-based facilitation.

The distinctive contribution of the protocol tradition is the recognition that ordinary collegial conversation is structurally biased against deep examination of practice. The first reflex in unstructured conversation is advice; the second is reassurance; the third is comparison to one's own experience. None of these produce the slow, focused, presenter-centered attention that the work requires. Protocols intervene in the conversational structure itself — allocating presenter-silent rounds, formalizing the warm/cool distinction, separating clarifying from probing questions — and in doing so, they create the conditions for a kind of professional talk that would not arise spontaneously. The recommendations in the Member stage about prohibited modes of feedback (unsolicited advice, hijacking, vague praise, speaking for the presenter) derive directly from this analysis.

Breidenstein, Fahey, Glickman, and Hensley (2012) studied the use of the Tuning Protocol with preservice teachers and found that participants reported four consistent themes: substantive benefits, structural drawbacks, attention to the protocol's structure as itself a learning object, and recommendations for adapted use. Their findings supported the use of the protocol throughout teacher preparation programs and underscored the centrality of the focusing question — the lever the recommendations in the Facilitator stage repeatedly return to.

4. The Empirical Evidence on Impact

The question whether PLCs and analogous structures actually improve practice and outcomes has been examined in several empirical reviews, the most cited of which is Vescio, Ross, and Adams (2008), published in Teaching and Teacher Education. Vescio and colleagues reviewed eleven empirical studies — ten U.S. studies and one large multisite English study (Bolam et al., 2005) — and asked two questions: did participation in PLCs change teaching practice, and was there evidence that student learning increased as a result. They reported that all eleven studies produced empirical data suggesting that the establishment of a PLC had shifted the professional culture of the school in ways linked to greater collaboration, deprivatization of practice, and more student-centered instruction. On student outcomes, they reported what they characterized as "a resounding and encouraging yes" — that the studies, while limited in number, consistently showed positive impact on student learning, with the strongest effects in settings where PLCs were both highly engaged and persistently focused on student data.

Bolam, McMahon, Stoll, Thomas, and Wallace (2005), in a Department for Education and Skills research report drawing on data from 393 schools in England, found that schools rated as effective professional learning communities by their staff also showed better student outcomes, controlling for prior attainment and school context. The effect was substantial and consistent across the sample.

Timperley, Wilson, Barrar, and Fung (2007), in the New Zealand Ministry of Education's Best Evidence Synthesis on Teacher Professional Learning and Development, conducted what remains the most rigorous synthesis of the conditions under which professional learning translates into improved teaching practice and improved student outcomes. The BES identified ten principles for effective professional learning, of which several map directly onto PLG design choices: extended timeframes (typically a year or more); engagement of external expertise; teachers as active participants rather than passive recipients; opportunities to question and challenge prevailing discourses; consistency with prevailing professional knowledge; and explicit engagement with what students need to learn. The synthesis explicitly cautioned against short, decontextualized training interventions, which dominate the professional development literature but show weak effects.

Vangrieken, Meredith, Packer, and Kyndt (2017), in a systematic review published in Teaching and Teacher Education, examined forty empirical studies of teacher communities and identified three types — formal, member-oriented with pre-set agenda, and formative — and four conditions for success: leadership support, group dynamics, trust, and respect. Their earlier review (Vangrieken, Dochy, Raes, and Kyndt, 2015) in Educational Research Review analyzed teacher collaboration more broadly and identified six factor categories influencing collaboration: process, guidance, personal, organizational, group, and structural. The structural factors — time, space, scheduling — emerged as necessary conditions; relational factors as sufficient conditions only when structural conditions were met.

It is important to register two caveats from this literature. First, the evidence base is dominated by educator settings; transfer to other professional contexts is plausible but less directly evidenced. Second, even in educator settings, Vescio and colleagues noted that most studies relied on self-report and that the field still needs more studies that connect PLC participation to outcome measures via observable changes in practice. The Facilitator stage's recommendation that PLGs run on defined cycles with explicit renewal decisions follows partly from this; the discipline of articulating what changed protects against the failure mode the literature documents.

5. Conditions That Predict Success

Stoll et al. (2006), in their review of the international PLC literature, identified eight characteristics that consistently distinguished effective from ineffective professional learning communities: shared values and vision; collective responsibility for student learning; reflective professional inquiry; collaboration; group as well as individual learning is promoted; mutual trust, respect, and support among members; inclusive membership; and networks and partnerships beyond the immediate group. The first five had appeared in earlier reviews; the last three were the distinctive contribution of Stoll and colleagues.

The condition of mutual trust deserves particular attention. Bryk and Schneider (2002), in Trust in Schools (Russell Sage Foundation), demonstrated through large-scale longitudinal research in Chicago elementary schools that what they called "relational trust" — the mutual obligations and expectations among teachers, principals, parents, and students — was a strong predictor of school improvement, mediated by its effect on the willingness of teachers to engage in the kinds of practice exposure that PLCs require. PLGs that try to skip trust-building, or that assume trust will arise from a shared cause, consistently underperform groups that invest in the relational scaffolding deliberately.

Vangrieken et al. (2017) noted that the presence of different stakeholders — and particularly the presence of supervisors in the same community as their direct reports — significantly altered the dynamics, generally degrading the candor that the format requires. This empirical finding underwrites the Facilitator stage's recommendation against mixing supervisors and reports in the same group when avoidable, and against assuming the issue can be talked away when it is unavoidable.

6. Psychological Safety as the Mediating Mechanism

Edmondson's (1999) study of fifty-one work teams in a manufacturing company, published in Administrative Science Quarterly, introduced the construct of team psychological safety: a shared belief among members of a team that the team is safe for interpersonal risk-taking. The study demonstrated that team psychological safety was associated with team learning behavior — asking questions, seeking feedback, discussing errors, experimenting with new approaches — and that learning behavior in turn mediated the relationship between psychological safety and team performance. Crucially, team efficacy (a confidence in the team's ability to succeed) did not predict learning behavior once psychological safety was controlled. It is the safety to take interpersonal risks, not the confidence in collective ability, that predicts whether a team learns from its experience.

Edmondson's later work (Edmondson, 2018, The Fearless Organization; Edmondson and Harvey, 2018, on team learning in the field) extended the framework to a wide range of organizational settings, including healthcare teams, executive teams, and innovation teams. Frazier, Fainshmidt, Klinger, Pezeshkan, and Vracheva (2017), in a Personnel Psychology meta-analytic review covering 136 studies, confirmed the robustness of the construct's relationships to learning behavior, information sharing, creativity, and task performance, across industries and team types.

The relevance to PLG design is direct. The protocols and customs described in the Member and Facilitator stages — the presenter-silent rounds, the warm-before-cool sequencing, the prohibition on hijacking and unsolicited advice, the gradual ramp-up from norm-setting to substantive presentation — are interpretable as a designed environment for the production of psychological safety through the repeated experience of taking small interpersonal risks and not being punished. Trust accumulates from session to session because the format makes it earn its accumulation. This is the underlying mechanism that explains why the format takes the time it takes, and why short-circuiting the format — "let's skip the warm round and get to the real feedback" — reliably undermines the work.

7. Why Protocols Work: Speech Norms and the Conversational Field

Several research traditions converge on a similar account of why structured conversations outperform unstructured ones for the specific purpose of examining practice. Little (2003), in a Teachers College Record analysis of teacher community in practice, documented how the de-privatization of practice — the willingness to expose one's own work to colleagues' examination — depends on conversational structures that distribute speaking turns predictably and that protect speakers from premature evaluation. Without those structures, the conversational field defaults to the patterns of ordinary professional talk, in which advice-giving, status-marking, and self-presentation crowd out the slower work of joint examination.

McDonald, Mohr, Dichter, and McDonald (2013), in The Power of Protocols, argued that protocols function as cognitive prosthetics: they offload the management of turn-taking, time, and conversational norms from the participants' working memory to the protocol itself, freeing attention for the substance of the work. The presenter who knows they will not be interrupted can concentrate on framing their work clearly; the listener who knows their turn to speak is reserved can concentrate on listening. The orchestration that protocols impose is what permits a quality of attention that unstructured conversation cannot reliably produce.

Curry (2008) noted that this orchestration is not free of costs. The decentralized structure of CFGs — and, by extension, of PLGs — means that the group's learning is shaped by the particular dilemmas members happen to bring, which may be narrower or wider than the practitioners would benefit from. The reliance on protocols can become ritualistic if the facilitator is unskilled. The diverse menu of activities can fragment attention if there is no through-line. None of these tensions invalidates the format; they are the inherent trade-offs of a structure that prioritizes member agency over curricular coherence.

8. Tensions, Limitations, and Failure Modes

The research literature is clear that PLCs and PLGs are not panaceas. Vangrieken et al. (2017) documented frequent failure modes: groups that drifted into superficial agreement without the cool-feedback edge, groups where the work of one or two presenters dominated, groups whose process was nominally collaborative but whose substance was directed by an administrative agenda. Curry (2008) reported similar tensions in CFGs. DuFour and Eaker themselves warned that the term "PLC" had been so widely adopted that it was at risk of meaning anything anyone wanted it to mean — and therefore, in practice, nothing.

Two limitations of the educator-centric literature are worth registering for workplace adaptation. First, most of the studies were conducted in settings where the group's purpose was understood as professional improvement rather than business outcomes; transferring the format to a setting where members are accountable to performance metrics changes the contract in ways the literature does not fully address. Second, the research has paid relatively little attention to settings with significant status mixing or cross-cultural dynamics; what works in a relatively homogeneous teacher group may need substantial adaptation in a multinational engineering team or a cross-functional healthcare unit.

Despite these limitations, the convergence of evidence across the PLC, CFG, CoP, and team-learning traditions is substantial enough that the basic design elements — small size, sustained cadence, protocol-mediated conversation, reciprocal presentation, attention to psychological safety, debriefing as a discipline — can be recommended with confidence. The recommendations in the Member and Facilitator stages are conservative readings of what the evidence supports.

9. From Education to Industry: Translation Considerations

The original Community of Practice literature (Wenger, 1998; Wenger, McDermott, and Snyder, 2002) was developed with explicit attention to workplace settings, and a substantial body of CoP research now exists in healthcare, software development, manufacturing, and professional services. Wenger and Snyder's (2000) Harvard Business Review article was an early and influential argument for the value of communities of practice as a knowledge-management strategy in commercial organizations.

The translation from education to industry preserves the central insight — that durable professional learning happens in small, sustained, peer-led groups examining real practice — while requiring three adaptations.

With those adaptations, the format transfers well. The team-learning research (Edmondson, 1999; subsequent meta-analytic work) was conducted largely in industrial and healthcare settings to begin with, and its conclusions are entirely consistent with the educator PLC literature. The convergence is itself evidence that the underlying mechanisms — protected attention, structured conversation, psychological safety, reciprocal exposure of practice — are not specific to schools.

10. References

APA 7th edition format. Arranged alphabetically by first author.