Immunity to Change: Explore Unspoken Social Expectations
Nour
Founder, Coachful

Immunity to Change can help a client explore unspoken social expectations that make a chosen change feel risky. Someone may want a more sustainable way of working while acting as though belonging depends on always being available. The useful inquiry connects that person's actual behaviour, what they are protecting and what they predict would happen if they acted differently.
“Social contract” is a metaphor here for a perceived bargain or expectation. It is not a legal contract, a separate standardized Immunity to Change diagnosis or proof of an unconscious agreement among colleagues. Actual duties, authority, workload and other people's expectations need to be examined in their own right.
Separate the perceived bargain from the actual agreement
An unspoken bargain often has a reciprocal shape: “If I never make anyone wait, I will remain a valued team member.” The first part describes what the person supplies; the second describes what they hope to receive or avoid losing. Neither part should be attributed to the group without evidence.
Ask what supports the account. A manager may have praised responsiveness, a colleague may have objected to a missed deadline, or the person may remember being left out of a meeting. Those are events to understand. They do not automatically establish a universal rule that any delayed reply causes exclusion.
Conversely, an expectation can be explicit and consequential. A designated duty role, an agreed customer deadline or a handover responsibility may require a response. The coaching task is not to relabel a genuine obligation as a limiting belief and encourage someone to ignore it.
A useful first distinction is among four things: what was actually agreed; what another person has said; what the client infers; and what remains unknown. If the first category is unclear, a role conversation may be needed before an assumption test. The hidden-loyalties guide considers a related question about belonging and chosen obligations.
Use the four-column model with a distinct worry
Robert Kegan and Lisa Laskow Lahey developed Immunity to Change to explore how a desired improvement can coexist with commitments that protect a person from an anticipated difficulty. Their four-column map connects an improvement goal, behaviour that works against it, competing commitments and big assumptions. Minds at Work's developer description presents that structure; it is a working model to examine, not an explanation the coach should impose on every client.
Keep the worry separate from the protective commitment. “I fear being excluded” describes an anticipated experience. “I am committed to never letting a colleague experience waiting for me” describes a possible protective strategy. Repeating the fear in every column makes the map less informative.
The big assumption states a predicted relationship that makes the strategy feel necessary. It might be accurate, partly accurate or inaccurate in the setting. The authors' authorized book excerpts explicitly leave that possibility open. The task is to develop a more examinable account, not force the client to announce that a belief is false.
This is not a clinical investigation of unconscious motives. The client can reject a proposed wording, choose another present concern or decide not to use the framework. The coach does not need a childhood explanation to make the exercise complete.
Agree the purpose and record before exploring
The following is an original fictional case. Lina manages internal projects and has agreed two coaching sessions with Mira, on 2 and 23 November 2026. She wants to handle routine requests without turning every evening into an extension of her working day. Her employer has a separate incident route and designated duty staff; she is not testing whether urgent incidents can wait.
Lina chooses to explore her expectation that immediate replies earn continued inclusion in planning. She does not want a family-history discussion or a psychological assessment. Mira accepts that focus. They agree that the detailed map stays within their coaching arrangement; any management discussion will concern work expectations and a separately chosen summary.
Before recording or producing a recap, Mira checks the actual settings and audience with Lina. Lina keeps her detailed personal wording in her own unshared notes. Her manager will not receive the map merely because he funds the two sessions.
For context, Lina reviews six routine requests from the previous working week. She answered all six during the evening. This is a small personal work log, not a measure of the whole team's expectations. She has not asked the six senders whether an evening reply was required.
Complete a client-owned map, then allow correction
| Part | Lina's tentative account |
|---|---|
| Chosen improvement | Agree realistic response times for routine requests and use them, while keeping the actual incident route intact. |
| Doing or not doing | I answer ordinary messages in the evening, avoid asking when the answer is needed, and quietly prepare replies even when I promise them for the next working day. |
| Worry | If colleagues wait, they may see me as unreliable and stop involving me in planning. |
| Possible competing commitment | I am committed to preventing colleagues from experiencing any wait for me. |
| Big assumption to investigate | If I leave a routine answer until the agreed next morning, that colleague will exclude me from the next planning discussion. |
Mira first suggests, “You believe people will reject you whenever you say no.” Lina corrects her: “That is broader than what I said. This is about waiting for a reply, and being left out of planning.” Mira withdraws the broader sentence and reads back the specific prediction. Lina confirms the revised wording.
The narrower statement matters. It identifies an action and an observable consequence without pretending to measure Lina's whole sense of worth. It also distinguishes inclusion in a particular work discussion from whether everybody likes her.
Lina supplies two pieces of relevant history. Her manager Owen once said quick replies were helpful. She was also omitted from one planning invitation, but she does not know why. Mira records those as separate facts and does not invent a causal connection between them.
Lina recognizes that her strategy can be understandable and costly at the same time. Protecting reliability matters to her. The question is whether preventing every wait is necessary to do that, and which real expectations need to be made explicit.

Check the work expectations before changing the behaviour
Lina asks Owen to clarify ordinary response expectations without disclosing her private map. He confirms that her agreed working day is 09:00–17:00, that routine requests can normally be answered the next working day and that the separate incident route remains authoritative for incidents. This describes the fictional arrangement, not a general rule about employment rights or working hours.
Owen also says that some planning requests have an earlier stated deadline. Lina must clarify those rather than assume every message can wait until the same time. He agrees to help resolve conflicting priorities when necessary; that is different from promising that every colleague will be satisfied.
The UK HSE's Role standard emphasizes clear, compatible requirements and routes for raising uncertainty or conflict. That supports examining the work system alongside the client's interpretation. A personal map cannot allocate staff time, remove a duty or decide an employment dispute.
Lina chooses one colleague, Paz, and an ordinary information request that does not concern safety, a customer emergency or restricted information. She explains the proposed response window and checks whether it suits the work. Paz can decline or name an earlier need. Lina does not ask Paz to confirm a theory about the team's unconscious loyalty.
Design a learning test with more than one possible result
Kegan and Lahey's book uses S-M-A-R-T differently from the familiar goal acronym: a test should be safe and modest, actionable soon, and conducted with a research stance toward the assumption. Completing an activity is not enough; the person needs relevant observations and an interpretation that may qualify the prediction.
Lina initially proposes ignoring an unspecified request overnight and seeing whether anyone complains. Mira asks how that would establish its deadline, importance or the other person's expectation. Lina discards the proposal. It would confound a possible unmet obligation with the particular belief she wants to examine.
The agreed design is more precise:
- Choose a routine request with Paz and confirm that a reply by 10:00 the next working day is acceptable.
- Acknowledge the request during Lina's working day, naming the agreed reply time, without supplying the substantive answer immediately.
- Do not complete the answer that evening. Use ordinary daytime work the next morning and send it by the agreed time.
- Record what Lina actually did, what Paz said about the response, and whether the next relevant planning invitation includes Lina.
- Keep alternative explanations visible: a changed deadline, an incomplete answer, an unrelated invitation decision or a return to evening work can limit the interpretation.
Paz agrees to the response arrangement for a suitable request. Lina's personal map is not shared. This is ordinary agreed work and a private coaching inquiry, not a clinical experiment conducted on an unsuspecting colleague or a research study claiming generalizable findings.
First attempt: the outward reply changes, the work does not
On 10 November Paz asks a routine question at 15:00. They agree a reply by 11 November 10:00. Lina acknowledges that window and sends the answer at 09:30 the following morning. Paz says the timing worked and includes Lina in the next planning invitation.
At first Lina calls this proof that she can stop working in the evening without losing inclusion. Looking at her own record, she notices that she actually wrote the complete answer at 21:00 and merely delayed sending it. The behaviour central to the test did not change.
Mira does not count an attractive outward result as a completed test. They retain two observations: Paz accepted the agreed response time, and Lina still protected against waiting by doing the work privately at night. The attempt provides limited information about communication timing, but not about what happens when she leaves the work until morning.
Lina chooses a second attempt rather than hiding the evening work or expanding the claim. Her own correction improves the learning record. It is not evidence of failure as a person or a reason to make the next test more risky.
Second attempt: a legitimate dependency changes
On 12 November Paz and Lina agree another routine answer for the next morning at 10:00. Lina acknowledges it during the afternoon and finishes her working day at 17:00 without preparing the answer. At 17:20, an unforeseen agenda change gives Paz a 09:00 meeting the next morning. Paz emails the new need, but no new response time is agreed with Lina.
Lina reads the message at the beginning of her next working day and sends the answer at 09:20 on 13 November. That meets their original 10:00 agreement but misses the newly arising 09:00 need. Paz says, “That timing does not work for the morning meeting.” The meeting has already proceeded without that input.
Lina acknowledges the operational impact and explains when she saw the changed requirement. She does not claim to have supplied the information before the meeting or apologize for breaking a replacement deadline she never accepted. She asks how they should handle that kind of changed dependency next time.
Paz still includes Lina in the following planning discussion. This challenges the prediction that any wait will cause that colleague to exclude her. It does not mean there was no cost to the response arrangement, that every colleague will react similarly or that a scheduled invitation proves permanent social acceptance.
| Review field | Completed second-attempt entry |
|---|---|
| Different behaviour | Lina did not prepare the answer during the evening. |
| Original agreement | Reply by 13 November 10:00; actual reply 09:20. |
| New event | Paz's 09:00 meeting need arrived at 17:20 after Lina's working day; no replacement deadline was accepted. |
| Actual colleague response | Paz criticized the timing for that meeting and continued to include Lina in planning. |
| Interpretation | Criticism and inclusion coexisted. The specific exclusion prediction was challenged, while the coordination problem remained real. |
| Unresolved work | An agreed route for changing deadlines and resolving competing needs. |
The outcome does not require a reassuring ending. Lina can learn something about the perceived bargain while also needing a better operational arrangement. Calling Paz's criticism a distortion would avoid the very information the test produced.
Negotiate the actual expectation without imposing a team motive
On 20 November Owen, Lina and Paz discuss the response process. They agree that routine requests should name the needed time; Lina will confirm a feasible response or raise a conflict. Where possible, requests needing an answer before 10:00 should be identified before the previous working day's 16:00 planning check.
A genuinely new requirement after that check does not create an automatic overnight promise. Owen accepts responsibility for helping the relevant people replan the work or identify available authorized cover. Nobody redirects ordinary planning questions to the incident route or assumes another colleague is always available after hours.
They record a limited trial of this arrangement from 24 November to 4 December, with an operational review on 7 December. All three acknowledge the text. Those dates are future work at Lina's final coaching session; the article does not claim the new process has already succeeded.
A colleague joining the discussion says that a broad team statement, “We are all afraid to disappoint each other,” does not describe their experience. Owen agrees to keep the record about deadlines and responsibility rather than assign everyone a shared competing commitment. The colleague does not have to complete a private map to help improve the workflow.
If a team chooses a collective Immunity to Change inquiry, begin with a genuinely shared goal and behaviour, invite different accounts and distinguish the group's tentative map from individual disclosures. A leader's preferred explanation is not a reason to require psychological agreement. The indispensability guide examines a different pattern involving dependency on a particular role-holder.
Close the coaching review with the remaining difficulty
On Saturday 21 November Lina answers another routine message during the evening. She says the old urge returned even after Owen's role clarification. She records the event rather than presenting the earlier two attempts as a permanent change. There is no claim that mapping has dissolved an unconscious contract.
In the 23 November coaching session, Lina revises her working account: “A routine wait does not necessarily remove me from planning. I may still receive criticism, especially when deadlines change. I need to clarify those requirements instead of trying to prevent every uncomfortable reaction.” She chooses that wording herself.
Mira initially drafts a summary saying the team now accepts next-day replies. Lina rejects it because only a limited arrangement with Owen and Paz has been agreed, and the future trial is not yet observed. Mira replaces it with the narrower account; Lina reads and confirms the correction.
Lina then approves a separate work-only summary naming the response arrangement, its owners, dates and review. Mira sends only that approved text to Owen through the agreed business email thread. Owen acknowledges receipt. The detailed worry, protective commitment and personal evening-work reflection are not included.
The two-session coaching engagement closes. Owen owns the later operational review; Lina has not purchased additional coaching or agreed to report private reflections indefinitely. Her personal notes remain her choice. A future coaching conversation would require a new agreement.
Keep a useful map and learning record in Coachful
Coachful is our #1 recommendation for organizing client-chosen reflection and the actions around a learning test. Use it to preserve the distinction between a tentative map, an agreed action and a reported event. It does not diagnose a hidden social contract or validate an assumption from a completed task.
- Prepare an original optional worksheet for the chosen goal, observable behaviour, worry, possible protective commitment and prediction. Assign it through Clients > client > Worksheets & resources with the appropriate access and delivery choices. Copying a private link alone does not grant access.
- Explain that submitted worksheet answers can be reviewed by the authorized coach team. If the client wants detailed wording to remain personal, use unshared journal or takeaway pages instead. Where an enabled Share with coach control is used, the client intentionally shares that individual page.
- Add the chosen preparation or conversation as an ordinary client-plan action, including its boundary and agreed review. A task marked done is not proof of a valid test, another person's acceptance or a changed belief.
- At review, distinguish the action actually taken, the other person's observed response, the client's interpretation and what remains unknown. Coach review is a private coach-team record, excluded from the response PDF; saving it does not deliver a reply to the client.
- Check actual workspace and session-type recap settings before generating sensitive material. Do not assume every recap waits for approval. Use the specifically approved audience and summary rather than converting a private map into a sponsor report.
In Lina's case the detailed map is not submitted as a shared worksheet. She and Mira discuss the learning in the two booked sessions. The separate approved work summary travels through the named email route, while the employer's actual work agreement stays in its authorized system. Explore Coachful's features for the supporting preparation and review workflow.

Troubleshoot before adding another column
If the map seems circular, separate the fear from the strategy used to prevent it. If no plausible protective commitment emerges, do not invent one. Clarify skills, authority, resources or the goal instead.
If the test produces reassurance but the relevant behaviour stayed unchanged, retain that limitation. Lina's first attempt did not examine evening work. If a test reveals a genuine consequence, revise the plan rather than insisting that change must feel comfortable.
If a sponsor requests individual maps, return to the actual agreement and the person's choice. If someone raises a legal, safety or clinical issue, use the appropriate process or professional expertise. The ICF Code of Ethics is a relevant reference for roles, information-sharing agreements, accurate representations and competence; it is not an endorsement of this fictional test.
Harvard Graduate School of Education's developer account describes the distinction between technical and adaptive work. That helps explain the framework's purpose, while neither that account nor the book example establishes a controlled outcome for Lina or every organization.
Frequently asked questions
Is an unconscious social contract an actual contract?
The phrase here describes a perceived social bargain. Actual contractual terms, employment rights and formal duties require appropriate interpretation. The map cannot cancel those obligations or determine whether a legal promise exists.
Must every expectation come from family history?
No. Work with the client's chosen current issue. The coach should not infer a family cause, hidden trauma or developmental stage from an evening reply. Historical exploration is optional and must remain within the agreed professional scope.
Does the framework assume the big assumption is false?
No. It can be accurate or partly accurate in the setting. Choose an appropriate learning test and examine the observations, including inconvenient results. Lina's test challenged a specific exclusion prediction while revealing an actual deadline-coordination problem.
Can a team use one shared map?
A voluntary collective inquiry can concern a shared goal and behaviour, but the account remains tentative. People can disagree or decline personal disclosure. A shared workflow agreement does not establish that every colleague has the same protective motive.
What counts as progress if the behaviour returns?
A clearer prediction, a valid limited observation, a corrected interpretation or an accepted work agreement can be useful. Retain the recurrence and avoid claiming permanent change. Lina's later evening reply and the unobserved future trial remain part of the final account.







