Worries in Immunity to Change: Explore a Work Goal
Nour
Founder, Coachful
Exploring worries in Immunity to Change can help a client understand what a familiar behavior protects. They may want to hand over work while fearing the loss of a useful role. Begin with their chosen work goal, then distinguish a worry, a protective commitment and an assumption worth investigating.
This guide develops a succession example, an accurate-reporting rehearsal, a six-field review and a team adaptation. The cases are original nonclinical illustrations. Do not use the language of "core anxiety" to diagnose a hidden condition, require intimate disclosure or promise that a work experiment will eliminate worry.
We build Coachful. Coachful is our #1 recommendation for organizing the selected preparation and follow-up in this workflow. That is our maker's editorial preference, not an independent ranking or evidence that software changes a developmental stage or treats anxiety. A private paper map can be sufficient.
Name what feels at risk without supplying the answer
Kegan and Lahey connect an improvement goal with behavior working against it, protective commitments and assumptions. Their 2015 Harvard Graduate School of Education interview distinguishes the worries that arise when imagining a different behavior from an active commitment to prevent the feared result. A worry is not itself the whole competing commitment.
Ask about a specific situation: "What concerns you about this handover?" That gives the client a manageable choice. Asking for the deepest possible fear can pull the conversation beyond what they want or need to explore. Childhood experiences, family loyalties and an entire professional identity are not admission requirements.
Offer more than one possible explanation. A leader answering routine requests might be protecting visibility, responding to an unclear handover or exercising authority they are still required to retain. Investigate the work arrangement before treating a protective motive as established.
The client can reject a coach's interpretation. "You fear becoming irrelevant" should not become a map entry because it sounds insightful. Ask whether the wording fits, what it misses and whether the person wants to use a less personal description.
Keep the four map components distinct
| Component | Clarifying question | Check |
|---|---|---|
| Improvement goal | What change do you want, and why does it matter? | A client-owned goal, not a maturity ranking |
| Doing and not doing | What specific behavior works against that goal? | An observable example, not a character judgment |
| Worry and competing commitment | What feels at risk, and what are you trying to protect? | Record the concern separately from the active protection |
| Big assumption | What do you believe would follow if you acted differently? | A proposition to investigate, not a conclusion already disproved |
A usable goal might be "Let the successor make routine decisions within the agreed handover." "Become a fully mature leader" gives little guidance about what to observe and can turn the exercise into an assessment the coach is not conducting.
A protective commitment should explain how the current behavior makes sense to the person. It is not simply a second worthy goal such as "support the team." The question is what the person is committed to preventing or maintaining when their behavior undercuts the improvement goal. Keep the client's wording provisional if the connection is uncertain.
The worry-box process develops this part of mapping. A map can remain incomplete; discovering the right phrase is less important than understanding the actual choice and constraint.
Build Nadia's succession map with her
In this fictional case, Nadia is moving from project lead to adviser. A written handover accepted on 2 November 2026 gives successor Sam the routine project-review agenda decisions. A separate spending approval remains Nadia's responsibility until 30 November. That retained authority is not part of the proposed experiment.
Nadia keeps answering requests addressed to Sam, adding herself to routine reviews and privately revising replies. With coach Mina, she chooses the following map. It describes this situation, not a diagnosis of retiring leaders or proof that every repeated intervention has the same motive.
| Entry | Nadia's chosen wording |
|---|---|
| Goal | Let Sam lead routine decisions within our handover |
| Behavior | I answer first, copy myself into reviews and revise responses without being asked |
| Worry | Colleagues may stop asking me anything and decide my previous work did not matter |
| Competing commitment | I am trying to maintain visible evidence that I still contribute |
| Assumption | If I redirect a routine request, that colleague will see no useful role for me |
Nadia declines to circulate the worry and assumption. She chooses to discuss only the work boundary with colleagues: Sam owns routine decisions; her advisory remit still needs a usable route. Mina does not contact the project team or disclose the coaching relationship on her behalf.
They read the relevant handover boundary before designing the action. A request involving Nadia's retained approval must still follow that approval process. Withholding it to make a test more dramatic would change the work risk and fail to examine the narrower assumption they selected.
Design a safe test rather than a bravery exercise
In the authorized book excerpts, printed page 261, the authors' SMART criteria mean Safe and Modest, Actionable in the near term, and a Research stance toward a Test of the assumption. These are criteria for learning, not the familiar goal-setting acronym or a requirement to feel confident before acting.
Nadia chooses one ordinary agenda request already within Sam's authority. Her prediction is explicit: the colleague will reject the redirect and say she has nothing useful to contribute. They will note the actual response and any subsequent advisory request. They will not infer everyone's private opinion from silence.
Mina: What can you say that respects both the handover and your remaining role?
Nadia: "Sam owns that decision now. Please send the request to Sam. I can help with historical context if you both need it."
Mina: What would count as information about your prediction?
Nadia: An explicit objection would matter. "Thanks" would not prove I am unwanted. A later context question could show the roles can coexist.
Mina: What if this needs your retained spending approval?
Nadia: I will use that procedure, not withhold approval to protect the experiment.
Agree what the action cannot establish. One colleague and one routine request cannot settle how the whole team values Nadia, whether every handover is sound or whether the worry is permanently resolved. If no relevant request arrives, there is no completed test to debrief yet.
Follow the first redirect and its limited evidence
On 4 November Ravi sends Nadia a routine agenda request. Nadia uses the agreed redirect. Ravi replies "thanks," forwards it to Sam and receives Sam's confirmation that Sam will handle it. No further advisory question reaches Nadia during the following seven days, 5–11 November.
Nadia feels overlooked. At the 12 November coaching review, Mina initially says the worry has been disproved. Nadia challenges that conclusion: the redirect was accepted, but they do not know why nobody sought advice. Mina withdraws the overstatement and changes the working record to separate the accepted redirect, the absence of a later question and Nadia's experience.
The correction matters. The authors' interpretation guidance distinguishes observed words and actions from inferences about another person's reactions, and asks whether the actual test was valid. Here, the accepted redirect qualifies Nadia's predicted explicit rejection. The quiet week does not establish either rejection or universal approval.
Nadia chooses a practical next step: use the scheduled handover review to clarify her advisory route. She does not need to argue herself out of feeling less visible before asking for a workable arrangement.
Clarify the route, repeat narrowly and retain a recurrence
At the 13 November handover review, Nadia, Sam and Ravi agree that historical-context questions can come through Sam when useful. Sam says being copied into every routine exchange undermines the new decision boundary and asks Nadia to stop doing that. Nadia accepts the criticism. The agreement clarifies roles; it does not give Sam a duty to produce reassuring questions.
On 16 November another routine request arrives from Ravi. Nadia redirects it to Sam. On 18 November Sam asks Nadia for a specific piece of project history, and she supplies that context that afternoon. On 19 November Sam acknowledges that it is useful and confirms that the current agenda decision remains Sam's.
This is evidence of one actual advisory contribution alongside the routine handover. It is not a new veto for Nadia or proof that every colleague values her. She still reports discomfort about a reduced day-to-day role.
On 20 November she slips back into sending Sam an unsolicited rewrite through their work email. Sam reads it and objects that this is the same boundary problem. Nadia withdraws the unsolicited revision that day and acknowledges the mistake. The later context request did not prevent recurrence or remove the need for accountability.
At the 23 November review, Nadia chooses to keep the redirect and bounded context route, and to check whether she is being asked to contribute before revising. Mina sends a selected learning summary through their agreed coaching email at 14:00. Nadia approves it at 15:00, retaining both the useful contribution and the unrequested-revision repair; Mina acknowledges the agreed close at 16:00.
This closes the agreed coaching review, not the whole organizational transition. The 27 November handover check and Nadia's retained spending approval through 30 November remain future work. No sponsor receives the private map, and the record makes no claim of a developmental-stage transition or elimination of worry.
Use a six-field review that permits mixed findings
- Prediction: What did the client expect, in words specific enough to examine?
- Action: What actually happened, including departures from the plan?
- Observation: What did people say or do? What remains unknown?
- Experience: How did the client experience the event, without making that an account of everyone else's thoughts?
- Alternative interpretation: What else could explain the observation?
- Next decision: What will the client keep, clarify, adapt or stop?
For the first test, Ravi's accepted redirect and the quiet week sit in Observation. Feeling overlooked sits in Experience. A successful handover, a quiet workload or an unclear advisory route are possible explanations to investigate, not facts to select according to the desired conclusion.
After the second test, include Sam's actual context request, acknowledgment and decision boundary. Add the later unrequested revision and objection. Do not describe the sequence as a simple march from fear to confidence while dropping the inconvenient event.
If a colleague objects, examine the objection. The issue may be poor communication, unclear authority, unavailable resources or a genuine reporting duty. An accurate warning is not resistance to dismiss. Change the plan or seek the person who can resolve the condition.
Rehearse accuracy when information is missing
A separate fictional example concerns Ellis, a finance leader who sometimes gives an estimate without clearly labeling it. Ellis worries that admitting an unanswered detail will look incompetent. The immediate responsibility is accurate reporting, whether or not that worry changes.
Ellis chooses a low-risk internal rehearsal on Monday 16 November with review chair Toby, after checking the actual verification route. This is not an experiment with a public disclosure or permission to omit required data. Ellis practices: "I can confirm the approved total. I have not verified that breakdown. I will check with Noor, the report owner, and give a verification-status update through our reporting email by Tuesday 17 November at 16:00 London time."
Toby asks which part is unresolved and who owns verification. Ellis answers accurately rather than interpreting the question as proof of incompetence. Ellis requests the check from Noor, who acknowledges receipt that afternoon and confirms that verification is still needed. At 16:00 on 17 November, Ellis sends Toby the promised status: the total is confirmed, but the breakdown is still unverified. No guessed figure is inserted.
Noor supplies the verified breakdown at 14:00 on 18 November. Ellis sends it through the reporting route at 15:00, and Toby acknowledges it at 16:00. The first deadline was a status update, not a promise that verification would necessarily finish by then. The later completed check is separately recorded.
Make the follow-up accountable without confusing it with reassurance. Ellis keeps the approved total, unresolved breakdown, responsible report owner, promised status time and actual return in the work record. Toby can challenge an omission or a missed commitment. The coach does not explain away such criticism as merely the assumption talking, nor use a calm rehearsal as evidence that the underlying figures are correct.
If the uncertainty concerns an earlier inaccurate report, address that through the actual reporting procedure. Keeping a private reflection does not correct a business record already circulated. Likewise, sending an on-time status update does not turn the still-unverified breakdown into verified information. These distinctions let Ellis practice a more accurate response while preserving the obligations that make the concern consequential.
At debrief, distinguish the actual follow-through from the rehearsal reaction. Toby asked a legitimate question and received accurate status and later figures. That does not guarantee a board's response or establish that Ellis's wider worry has resolved. It does provide a usable response and an accountable verification sequence.
Choose disclosure and appropriate support
Explain the exercise and intended record before asking for personal material. Offer a practical version focused on action and authority if the client does not want to name a worry. They can stop, decline a question or leave the map unfinished.
In sponsored work, separately agree who receives which information and what authority permits identifying the coaching relationship. A work-goal update does not require the private worry, every observation or a clinical interpretation. Prepare the actual excerpt for client approval rather than assuming general participation permits disclosure.
The ICF referral overview emphasizes the coach's responsibility to recognize needs outside their expertise and discuss referral openly. NHS guidance distinguishes ordinary periods of anxiety from difficult-to-control worry affecting daily life. A coaching map is not a diagnostic tool. When concerns exceed competence or affect functioning, discuss qualified support; an immediate safety concern calls for the appropriate urgent response, not another work experiment.
The hidden-assumptions guide offers related nonclinical inquiry. Use qualified support alongside appropriate work arrangements rather than claiming the map replaces assessment or treatment.
Adapt the inquiry to a collective work pattern
A team can explore a pattern such as repeatedly reopening decisions after authority was agreed. Start with a shared work goal and invite competing explanations. One member may describe a protective habit while another identifies a valid quality, legal or resource constraint. Preserve those differences.
Agree a practical action within the team's authority: what information justifies reopening a routine decision, who may do so, where the request goes and how affected colleagues will be told. Required escalation and formal reporting stay in place. If the group cannot authorize the change, seek the relevant decision rather than describe an unapproved experiment as launched.
Do not require a boardroom or offsite group to disclose personal core fears. A senior leader volunteering private material does not obligate others to match it. Permit participants to pass and keep individual coaching records separate from the shared practical record.
At review, ask what changed in the work and who bore the consequences. If conflicting incentives or unclear governance remain, the next step belongs with those able to change them. A collective map cannot substitute for authority or resources.
Set a proportionate review rhythm and record
Use the next relevant work opportunity as a review anchor rather than defaulting to a quarterly audit. Specify how the result will reach the review and what the coach is actually providing. A person who has not encountered the situation has no test result yet.
Decide whether to repeat, adjust or stop. A manageable first action does not authorize increasing the risk next time. The people, stakes and retained responsibilities may differ. The purpose is a clearer choice, not maintaining a permanent map-making ritual.
In Coachful, use a form or worksheet only for details the client wants to share. For a standalone resource, deliberately grant access, send the private client-access link and ask the client to confirm it opens. Assignment alone does not guarantee a My Coaching next-action entry. Separate context, prediction, action, observation and review without scoring emotional health.
Keep personal notes with the client if preferred. Unshared Coachful journal and takeaway pages remain client-owned; an enabled Share with coach control intentionally exposes the selected page when the client chooses it. Do not place sensitive words there under an unconditional promise that the coach can never read them.
After discussing a next step, record the actual agreed task or goal. Coach review notes are private to the coach team, and saving them does not send feedback. Check effective recap sharing and session-type overrides, and deliver the agreed summary through a real route. A saved response or completed task does not prove that a belief was disproved or a colleague approved a decision. Explore Coachful features once the necessary record is clear.
Frequently asked questions
Is a worry the same as a competing commitment?
No. The worry names what feels at risk; the commitment names the protection the person is actively maintaining. Keep both in the client's language and allow either connection to remain uncertain.
What if the feared consequence is a real risk?
Retain that risk and address authority, resources or specialist advice. Nadia's spending approval stayed in place. A narrower assumption can be investigated without abandoning legitimate oversight or ignoring a colleague's factual objection.
Must a client feel less worried after testing?
No. Review what happened and whether the next choice is clearer. An accepted redirect did not tell Nadia everyone's opinion, and a later advisory request did not prevent her old behavior recurring. Emotional relief is neither required nor proof.
Should teams disclose their personal core fears?
No. A collective work inquiry can use agreed decision criteria and practical actions without public disclosure of private worries. Participation, reporting scope and permission to use personal material need their own agreement.
Sources: Kegan and Lahey, authorized HarvardX excerpts from Immunity to Change (2009), selected printed pages 261–265; HGSE, Be the Change (8 July 2015), developer interview; ICF client referral overview; and NHS adult anxiety guidance. Nadia, Ellis, their messages, the six-field review and team instructions are original nonclinical applications, not source-study results.
