Immunity to Change Peer Coaching Triads: A Practical Guide

Immunity to Change peer coaching triads are three-person learning arrangements. Participants rotate through presenter, questioner and process-observer roles to examine a wanted change, relevant behavior and possible assumptions. The presenter retains choice about the account, disclosure and next step.

Robert Kegan and Lisa Lahey developed the Immunity to Change framework. A peer triad is one way to support inquiry around it, not a guarantee of trust, developmental change or an explanation for every difficulty. This guide provides an original ninety-minute format and a complete case in which a peer corrects a real error without treating it as proof of someone's character.

Choose peer work deliberately

Neither arrangement removes the need to assess fit. A peer coach is a learning role, not a qualification. Do not diagnose anxiety, assign a developmental stage or claim to have uncovered a colleague's hidden truth. An ordinary knowledge or authority gap may need information rather than a psychological explanation.

The guide to exploring concerns in Immunity to Change considers the inquiry further. A participant can choose a less sensitive topic, another group, individual support or no participation.

Use the framework without treating the map as a verdict

Kegan and Lahey's Harvard interview describes protective commitments and an inquiring stance toward assumptions. The creators' Minds at Work account outlines four connected areas: a wanted improvement, contrary behavior, competing commitments and assumptions. These are model concepts, not a clinical diagnosis or evidence that every delay has a hidden cause.

Use brief wording the presenter accepts. A concern about quality can protect something legitimate. The question is whether a particular prediction needs examining, not whether the person must admit an irrational fear. A practical barrier can coexist with an assumption, and neither should be silently removed from the record.

The experiment stance in Kegan and Lahey's Immunity to Change supports modest inquiry. The schedule and practical prompts here are original suggestions, not their prescribed complete protocol, certification training or a reproduction of their worksheets.

Give each learning role a clear responsibility

• Presenter: choose the goal and relevant examples, correct the wording, decline a question or stop. Keep ownership of the map and conclusion.
• Peer questioner: ask one question at a time, check understanding and distinguish observations from predictions. Ask permission before changing to advice.
• Process observer: track time, notice leading questions or unsolicited solutions and give specific feedback about the exchange. Do not analyze personality.

An observer can say, “That sounded like a proposed solution; would the presenter like it now?” Their role is to support the agreement, not embarrass someone. If participants need basic practice, begin with a simpler exercise or appropriate facilitation rather than rush into sensitive material.

Prepare questions that leave room for disagreement

Start with a concrete occasion the presenter is willing to discuss. “What did you do at that point?” asks for an account; “Why did you sabotage it?” supplies a judgment. Let the presenter distinguish something they observed from what they expect might happen. Ask what would make the account more accurate before moving to an explanation.

Useful practice questions include: What change matters to you here? Which action seems to work against it? What does that action help you protect? What are you predicting would happen if you tried something different? What information would challenge or strengthen that prediction? These are original prompts for practice, not an assessment instrument or a requirement to complete every field.

One question can be enough. Leave space for an answer instead of delivering the list as an interview script. If the presenter says the question does not fit, ask what would help or return to the concrete event. A process observer can identify the wording that closed a choice and invite a repair without deciding what the presenter really means.

Launch a bounded voluntary pilot

1. Explain the purpose and limits. Separate learning from performance assessment and state what attendance or process information, if any, reaches a sponsor.
2. Check the group. Consider reporting lines, competition, conflict and genuine ability to decline without penalty. Being in different departments does not remove power.
3. Agree information handling. Decide what stays with the presenter, whether any notes are needed and how a concern reaches an appropriate support route.
4. Reserve usable time. Include preparation, each turn, process review and any accepted receiving work outside the meeting.
5. Review actual experience. Offer a private route as well as a group discussion. Keep, change or stop the arrangement according to what participants report.

A development invitation is not blanket permission to circulate disclosures. Explain how someone can pause, change partners or leave the learning format while preserving whatever ordinary support is already promised. Do not interpret declining as resistance to development.

A complete ninety-minute agenda

Three forty-five-minute rounds do not fit inside ninety minutes. This original agenda uses three twenty-four-minute rounds plus opening and closing time. It is a practical option, not a prescribed Kegan–Lahey protocol.

Nine plus three times twenty-four plus nine equals ninety. Every person reserves the whole meeting, not just their presenter turn. If someone needs longer, agree a different arrangement rather than consume the last presenter's time. A time notice before the experiment outline can make that choice visible.

Completing every map field is not required for the clock to end. A person can leave with a revised question, an identified practical gap or a decision not to test anything. Record that accurately rather than manufacture an experiment to make the meeting appear successful.

Discuss access and breaks before choosing this schedule. If someone needs a break or another communication format, agree a usable alternative and account for its time. Do not describe an extra break as included in ninety minutes while preserving every listed activity at its original length.

A triad with actual choices about participation

In this fictional case, Jules, Tova and Mei are colleagues without a direct evaluation relationship. Their bounded learning work runs from 1 to 9 June 2072. Existing professional work and prior learning sit outside the account without being assumed free. No one claims professional qualification from a rotating role.

Jules spends fifteen minutes on 1 June preparing and sending purpose, allocations, audience and return windows, reading both replies and sending confirmation. Tova spends ten minutes reading, declining an offered extra forty-five-minute live slot, accepting the ninety-minute triad and a bounded written alternative, then reading confirmation. Mei spends ten minutes reading, accepting her arrangement and reading the confirmation.

They reserve preparation and the later written work before starting. Tova accepts up to twenty active minutes for one nonpersonal logistics note and its correction and closing work. Jules accepts fifteen minutes for reading and observations, and Mei fifteen for reading and feedback. Personal maps remain with their owners; the shared note contains process logistics only.

Each spends fifteen minutes preparing a chosen topic on 2 June. On 3 June they use the complete ninety-minute agenda. Jules presents first, Tova questions and Mei observes. In the second round Tova presents, Mei questions and Jules observes. In the third Mei presents, Jules questions and Tova observes.

Repair a leading question within the first round

Jules: I want to let peers carry routine internal updates, but I rewrite every detail.

Tova: Are you afraid of looking careless?

Jules: That is not quite my wording. Quality matters, but I do not want a fear assigned to me.

Mei: Can we pause? We are suggesting the explanation. Could Jules describe what seems important?

Tova: What feels important about checking the update yourself?

Jules: Being seen as reliable about quality. I predict that if I do not check it before circulation, an error will make you think I am careless.

Tova: Would you like to examine that prediction with the small logistics note we discussed?

Jules: Yes, with no customer information or personal maps in it. A real error would still need correction.

The pause and repair occur within the first round's inquiry time. Jules retains this original four-area account:

This is Jules's accepted hypothesis for this situation. It is not a statement about every quality check. In Mei's later turn, her concern is an unclear policy; she chooses to seek the policy instead of supplying a hidden commitment. The group accepts that practical result. Tova also chooses what remains private in her turn.

Define the experiment and its receiving work

The experiment is not a challenge to be brave with high-risk material. Do not use confidential disclosures, safety-critical work, customer rights or an unauthorized decision to test a belief. Where the concern reflects a real risk, address that risk through its proper process.

Keep an actual error in the evidence

Tova spends ten minutes on 5 June preparing and sending a process note to Jules and Mei. It wrongly gives 10 June as the written close instead of the agreed 9 June. Jules spends ten minutes on 6 June reading it and privately recording the urge to rewrite the whole note. Jules does not rewrite or forward personal material.

Mei spends ten minutes that day reading and sending the date correction and her own observation to both. She says an error needs correction but does not equate it with Jules's overall care. That is feedback from one colleague about this event, not a measure of everyone else's judgment.

Tova spends five minutes on 7 June reading the correction, fixing the note and sending this complete replacement to both:

Our written learning close is 9 June, not 10 June as I first wrote. Please use the agreed reading slots to check this process account and return an accuracy reply. Personal maps and assumptions remain with their owners; this note does not summarize them. We are not booking another live triad or assigning a new experiment through this message.

Jules and Mei each spend five minutes on 8 June reading the corrected note and sending an accuracy reply. Jules also reads Mei’s 6 June observation within that five-minute block. Tova spends five minutes on 9 June reading both replies and recording closure. No additional acknowledgment is assumed.

Jules has evidence of a real error and a limited, workable correction. The observation complicates the absolute prediction, but cannot establish that checking is never useful or that trust has transformed. The group does not announce an overturned assumption, infer a developmental stage or begin another experiment.

Separate the observation from the conclusion

A useful review distinguishes four things: what was predicted, what happened, what someone actually reported and what remains unknown. Here the wrong date is observable. Mei's response is one person's reported judgment. Jules's private urge to intervene is a personal observation. None provides access to every colleague's thoughts or predicts the result of a higher-risk assignment.

The correction also matters. A test that contains an error is not automatically a failed learning exercise, but successful repair does not make the error disappear. Ask whether the original prediction was too broad, whether a narrower concern still fits and what practical control the work requires. A date check may remain useful even if checking every sentence is unnecessary.

Finish with wording the presenter accepts, including uncertainty. Keeping a concern, reducing the scope of a claim or declining a further test can be responsible conclusions. A later test would need a fresh purpose, suitable limits and agreement from anyone whose work it requires. It is not created by the triad's enthusiasm or by spare minutes in this account.

Count all three people's time

The bounded work totals 400 person-minutes against 460 allocated. Each person has a twenty-minute difference, totaling sixty. The meeting contributes 270 person-minutes already included; the other 130 cover preparation and written handling. Tova's twenty-minute written episode includes its final receiving and close, not just the original note.

Confidentiality needs a realistic arrangement

Agree what stays in the triad, which process issues can reach a facilitator and what relevant limits apply. Explain any attendance reporting before participation. A promise cannot guarantee every colleague's later conduct or erase organizational obligations.

Ask whether peers need notes at all. A presenter can retain their own map while others keep only an agreed support action. A group feed should not become the default repository for identifiable assumptions, personal histories or screenshots. Sharing a logistics note does not authorize sharing the map.

A plenary review can discuss process without exposing personal content: the timing was difficult, advice came too early or a written option was useful. Named assumptions or recognizable histories need separate consideration. Funding a development programme is not blanket permission for a sponsor to inspect them.

Work with power and support honestly

Colleagues may compete for promotion, budgets or influence even without a direct reporting relationship. For sensitive work, avoid presenting a manager–employee arrangement as equivalent to a separate confidential peer group. State the real authority and offer an appropriate alternative.

If conflict, coercion or a serious concern makes this format unsuitable, use an appropriate management, complaint or professional-support route. Acas guidance provides UK context for formal workplace concerns; a peer-learning agreement should not block legitimate advice or reporting.

A presenter can pass on a question, narrow the topic or stop. If the work becomes emotionally difficult beyond the group's competence, do not escalate the exercise to prove commitment. Choose appropriate support. The ICF Code of Ethics provides professional context for clear roles, agreements, information handling and competence.

Know when advice would help

During inquiry, a solution offered too early can close the presenter's examination. Ask whether information or a suggestion would help before changing roles. An observer can notice the change without making the questioner the problem.

A knowledge gap deserves an accurate information route. Someone who does not know the delegation policy may need that policy. Do not insist they must discover a competing commitment before being allowed to ask. An assumption and a practical gap can also exist together.

If advice is requested, name it as advice, explain its basis and leave the choice with the presenter. A suggestion that requires another person's work needs that person's agreement. Do not count an experiment as ready because someone in the triad has volunteered an absent colleague.

Review learning without requiring transformation

After a chosen period, ask whether each person had useful turns, an appropriate experiment and evidence worth examining. Include a private feedback route, with a real reader and agreed receiving time, because criticism may be difficult in front of the group.

Review when advice dominates, participation feels compulsory, confidentiality is uncertain or the format is no longer useful. Changing groups, simplifying the task or ending the pilot can be legitimate results. There is no universal programme duration that guarantees developmental change.

At any later meeting, start with what actually happened: the original prediction, action, conditions, evidence and unknowns. An error may identify a needed review process. Do not discard that information because it supports part of the concern. The presenter can revise the map, retain a narrower assumption or choose another goal.

Organize preparation and logistics in Coachful

Coachful is our #1 recommendation for organizing appropriate materials and agreed follow-through around this work. This is an editorial workflow judgment, not a measured market ranking, certification endorsement or guarantee of psychological safety. Review Coachful's features against the actual service.

Keep individual preparation in the appropriate location and verify actual audiences before assigning or sharing it. A shared program resource can explain logistics without collecting sensitive maps. Internal Coach review is not a delivered participant reply. Deliberately select which agreed actions should become tasks; a completed form does not authorize a sponsor report or another experiment.

The demonstration images show product organization, not the fictional triad's records or an author-performed trial. The collective team-map guide concerns a different arrangement from three individual maps rotating through peer roles.

Frequently asked questions

What is an ITC peer coaching triad?

Three people rotate through presenter, questioner and observer learning roles for inquiry and appropriately bounded experiments. Participation does not confer a coaching qualification.

Is advice always forbidden?

No. It may help with permission, especially for a practical knowledge gap. Distinguish it from inquiry rather than supplying the presenter's explanation.

Do triads create psychological safety automatically?

No. Participation choices, power, trust, information handling and process skill matter. Review actual experience.

Should managers and direct reports share a triad?

For sensitive work, a group without a direct evaluation relationship is a more appropriate starting point. Offer alternatives and acknowledge remaining power differences.

How long should a programme run?

Choose time for preparation, useful turns and review of accepted experiments. No fixed duration guarantees a particular change.