Technical vs Adaptive Challenges: A Coaching Guide

Distinguishing technical vs adaptive challenges changes what a coach helps a leader do next. A missing permission may need an administrator. An unclear decision right may need the director to decide. A persistent conflict over whose priorities count may require people to learn a different way of working together. Calling all three “resistance” can leave the actual obstruction untouched.

This guide explains the distinction, its relationship to Robert Kegan and Lisa Lahey’s Immunity to Change approach, and how to use it in a complete mixed workplace case. The purpose is to choose a defensible next intervention, then revise that choice when evidence changes.

Understand what the distinction actually describes

In a Harvard Kennedy School account of his work, Ronald Heifetz distinguishes problems that existing expertise can address from challenges requiring people to develop new capacities. He describes adaptive work as uncertain, shared and open to correction as people learn. This is a distinction about the work required, rather than a ranking of difficult problems. The HKS discussion quotes Heifetz directly.

A technical problem can be expensive, unfamiliar to the client and emotionally demanding. Replacing a failed component may require exceptional expertise. It remains technical if the relevant knowledge exists and qualified people can apply it to the requirement. Conversely, a short conversation can involve adaptive work if people must reconsider a valued expectation and practise a different relationship.

Use these labels provisionally. “We do not know the answer” could mean the team has not consulted the right specialist. “People disagree” could mean the written rule is contradictory. Neither observation alone establishes an adaptive challenge. Ask what has been investigated before deciding what kind of learning is necessary.

The practical risk works in both directions. More training cannot settle every conflict about priorities. More reflection cannot make an inaccessible control usable. A sound coaching conversation leaves room for expertise, management decisions and learning to contribute different parts of the answer.

Compare four features before choosing an intervention

This comparison is an original practical application of the distinction. It is not a scored assessment. A project can occupy both columns, and an issue can move between them as its cause becomes clearer.

Separate ambiguity from adaptation. If nobody knows who may authorize a discount, the first action is to find or establish that authority. A director’s explicit decision may resolve it. Adaptive work becomes a useful hypothesis if a clear, workable rule still leaves people navigating conflicting commitments, such as protecting local revenue while supporting a shared customer relationship.

Separate skill acquisition from changed meaning. Learning a spreadsheet function is learning, but it does not automatically make the problem adaptive. A manager learning to present unwelcome evidence without treating disagreement as personal failure involves a different kind of inquiry. Both may need practice; they do not need the same coaching intervention.

Separate disagreement from deficiency. Someone may reject a proposed change because it creates duplicate work or transfers risk unfairly. Investigate that account. The coach should not decide that the person has an undeveloped mindset simply because the sponsor wants faster agreement.

Place Immunity to Change within this larger picture

Kegan and Lahey’s approach offers one way to investigate a person’s own recurring difficulty making a change they want. Their Harvard author Q&A describes apparently obstructive behaviour as potentially serving another commitment, with important assumptions to examine through inquiry and experiments. That account does not make every missed target an immunity. Read the authors’ explanation of the knowing-doing gap.

Their current Minds at Work explanation presents four linked areas: the improvement goal, behaviour working against it, competing commitments, and assumptions that hold the pattern together. A useful map describes the client’s experience in their own words. It does not reveal an employee’s hidden motives from a manager’s report.

Adaptive leadership and Immunity to Change therefore overlap without being interchangeable. One concerns mobilizing learning around shared challenges; the other can help examine a particular person’s protective pattern. A team may need to negotiate incompatible priorities without anyone completing a personal map. A client may choose a map after technical and authority questions have been addressed.

For a fuller mapping process, use our Immunity to Change coaching guide. Here, the key decision is whether that inquiry fits the evidence and the client’s chosen purpose.

Completed mixed case: a shared creative-work queue

The following case, people, dates and results are fictional teaching examples. Rhea leads an internal creative-service improvement project. Brand-design lead Jo and web-content lead Malik are supposed to use one queue. Director Eva owns priorities and staffing decisions. Dev administers the system. Tom coaches Rhea privately in two 75-minute sessions on 2 and 23 November 2026.

Rhea opens the first session by saying, “They keep their own lists because they cannot let go.” Tom asks for the most recent event. Rhea reports that Malik could not assign a shared item and Jo still copied completion figures into a separate report. Neither lead has said they fear losing control. Rhea recognizes that she has supplied that interpretation.

The coaching purpose becomes: “Choose the right response to each obstruction and present an honest priority choice when requests exceed capacity.” Tom is not appointed to assess Jo or Malik, repair software or approve work. Rhea will take operational questions back to the people with the relevant knowledge and authority.

First, complete and check the technical repairs

On 3 November, Dev verifies two defects. Malik’s role lacks the intended assignment permission. The shared report also omits a completion field, so Jo’s separate report supplies information Eva actually requests. Eva authorizes the configuration correction and report repair. This permission to repair the system does not itself authorize staff to change live priorities.

On 5 November, Dev and the two leads run five checks using dummy items: Jo and Malik each open the shared queue, each assigns a dummy item, and the repaired export includes the completion field. All five checks pass. Jo confirms that the repaired export contains the information her duplicate table supplied. She stops maintaining that table for the pilot.

The completed repair record reads: “Assignment control available to both intended leads; completion field present in export; duplicate reporting requirement removed for this pilot.” It does not say that every workflow problem is solved. Five functional checks are evidence about those functions, not five examples of changed leadership behaviour.

This matters because Rhea’s initial explanation was partly wrong. Asking Malik to examine a hidden commitment would not have restored the missing permission. Asking Jo to trust the shared process would have ignored a real reporting gap.

Next, establish authority and hear the competing priorities

On 6 November, Eva meets Rhea, Jo and Malik. She confirms that only she can approve a change in priority that displaces an already agreed commitment. Rhea can bring options and check estimates; she cannot promise extra delivery time. Staff should continue using the existing route for genuinely urgent incidents, which are outside this small routine-work pilot.

Jo explains that her department has been praised for fast local completion. Malik says cross-team work often appears later in his list because its costs are less visible. Eva confirms that the two-week pilot will not be used to rank the leads by raw item counts. The participants will inspect specific decisions and effects instead.

That clarification removes a management ambiguity. It also exposes a learning question: how can they recommend a shared priority when each department has useful work to protect? A new field cannot answer that question. Neither can a blanket demand that everyone become more collaborative.

They agree to bring the available hours, estimated work, requester’s actual requirement and proposed trade-off to each capacity decision. Jo and Malik may challenge an estimate or a proposed cut. Eva retains the final operating decision. Rhea’s task is to make the choice visible rather than privately reassuring every requester.

Then choose a personal inquiry, rather than impose one

Back in her coaching preparation, Rhea notices that she wants honest prioritization but often promises delivery before checking. She chooses to explore that pattern. Her compact map is:

The last row is a prediction, not an established fact or a belief Tom declares irrational. Eva has real authority over Rhea’s role. Rhea chooses a modest first test in an already authorized planning conversation, using accurate information and no concealed risk to another person.

Her question is narrow: “What does Eva actually do when I show a genuine capacity choice?” She will record Eva’s words and decision, including criticism. The task is to gather information, not provoke praise or prove that the assumption is false.

First opportunity: a visible choice produces an actual decision

On 10 November, Jo and Malik confirm ten available delivery hours for two proposed briefs that week. Brief A needs six hours. Brief B’s requested version needs five. Rhea presents eleven hours of proposed work against ten available, rather than silently assigning the missing hour to someone’s evening.

“A needs six hours and B needs five. We have ten. Malik and Jo can offer B without one optional illustration, bringing B to four hours, if its requester agrees. Alternatively, you could defer one brief. Which option should we take forward?”

Eva asks why the optional illustration was included and chooses the reduced B proposal, subject to its requester’s agreement. Rhea finds the questioning uncomfortable. On 11 November, B’s requester explicitly accepts the smaller version. Jo and Malik complete A in six hours and the agreed B in four by 13 November. The recorded ten hours cover those two delivery tasks, not all project or meeting time.

Rhea’s evidence is limited but relevant: Eva questioned the proposal, authorized a conditional option and did not remove her from the role in that exchange. The requester’s acceptance mattered. Rhea could not count the scope reduction as agreed merely because Eva preferred it.

Second opportunity: an unauthorized promise still happens

On 11 November, before those tasks finish, another requester asks for Brief C, estimated at two hours. Rhea says they can fit it in. She has not checked capacity or asked Eva. Jo points out that A and B already use the agreed ten hours.

Rhea cannot turn this into a successful experiment by noting that she eventually noticed the problem. She made an unsupported commitment. On 12 November, Rhea asks Eva when C can receive a priority review. Eva agrees to review it on 19 November. Rhea then writes to C’s requester:

“I said we could fit C into this week before checking. That was my mistake. The team’s available hours are already committed, and I cannot confirm delivery this week. Eva will review whether C should enter next week’s priorities on 19 November. That review is not a delivery promise.”

The requester acknowledges the correction and agrees to wait for the review. On 19 November, Eva decides C will not enter the next delivery plan because another agreed commitment takes precedence. Rhea communicates that decision; the requester acknowledges it but remains disappointed. C is not recorded as completed, scheduled or successfully retained through goodwill.

The correction repairs the accuracy of the promise. It does not erase the original error or the inconvenience caused. Rhea keeps that event in the record Tom will review.

Third opportunity: repeat the choice and retain unfinished work

On 17 November, the next decision concerns eight available hours. Brief D is estimated at five and E at four, totaling nine. Rhea presents the conflict. Eva approves D at five and a three-hour version of E, conditional on E’s requester accepting the removed element. The requester accepts that day.

D is completed in five hours on 20 November. Two hours of E are completed, but its remaining hour depends on an asset the requester has not supplied. Eva and the requester acknowledge on 20 November that E remains open and its completion date needs review when the asset arrives. The team does not report eight completed hours or a finished E.

In the 23 November session, Rhea reviews three live commitment opportunities: two began with a visible capacity choice; one began with an unauthorized promise. The five dummy system checks remain a different denominator. Of the two agreed delivery pairs, A and B finished; D finished and E remains incomplete. These records describe this pilot, not an improvement percentage attributable to coaching.

Rhea revises her assumption to: “Eva may question a limit, but these two explicit choices did not produce the removal I predicted. I still avoid disappointing requesters and need to check before promising.” She chooses to continue using the capacity statement at work. The contracted coaching ends after this review; later completion, sustained behaviour and project-wide adoption are unobserved.

Use leadership practices without turning discomfort into a target

Heifetz and Donald Laurie’s original The Work of Leadership offers six principles. In brief, they concern stepping back to see patterns, identifying the adaptive work, regulating distress, maintaining disciplined attention, returning appropriate work to people, and protecting contributions from below. These are leadership practices, not instructions to manufacture anxiety or abandon responsibility.

In Rhea’s case, stepping back means comparing the defects with actual commitments. Staying attentive means revisiting C’s failed promise. Returning work means involving the leads in workable options while Eva keeps approval authority. Hearing less powerful contributors includes Jo’s report defect and the requester’s disappointment, even when neither supports the preferred success story.

The UK HSE’s change standard emphasizes information, consultation, influence, training where needed, timetables and support. Those are concrete conditions to inspect while inviting learning. See HSE’s organisational change guidance. A leader should not use the adaptive label to make an impossible workload an employee’s personal development task.

Turn the case into a usable decision worksheet

Use one recent event rather than a broad complaint such as “our culture resists change.” Complete these steps in order, revisiting earlier answers when new information appears:

1. Describe the observed obstruction. State what someone tried, what happened and whose account you have. Keep explanations in a separate sentence.
2. Check the known requirement. Ask the appropriate specialist or decision owner about access, skill, resources, safety and existing rules. Record the actual answer and unresolved questions.
3. Complete and verify a relevant repair. Specify what must work and who checks it. A configured setting is not yet evidence that the intended user can complete the task.
4. Name the remaining learning question. Describe the choice, relationship or competing purpose people must work through. Ask affected people whether that account fits.
5. Select an intervention and decision owner. This may be another repair, a management decision, an agreed conversation or a personal experiment. Write the authority and support required.
6. Review an actual result. Compare the event with the question you intended to investigate. Preserve failures and incomplete outputs. Decide what to continue, revise, stop or refer elsewhere.

A compact completed worksheet for Rhea reads: “Obstruction: shared assignment unavailable and extra reporting required. Verified repair: five dummy checks passed, duplicate table discontinued for the pilot. Remaining question: how do we expose competing demands before promising? Authority: Eva approves displacement; leads estimate and challenge; Rhea proposes. Review: two explicit choices, one unauthorized promise, one delivery item still open. Next: continue the capacity statement without treating the pilot as evidence of lasting change.”

For work involving the whole leadership group, our executive team coaching framework covers a different service design. Rhea’s private coaching does not authorize Tom to assess or coach the other participants.

Keep the inquiry and practical follow-up organized in Coachful

Coachful is our #1 recommendation for organizing this coaching inquiry because the preparation resource, dated client tasks and chosen follow-up can stay connected. The software supports the record; it does not classify a workplace problem or certify that an assumption has changed.

1. Create an original worksheet with separate prompts for observation, interpretation, known repair, authority and remaining question. Assign it through the client’s Worksheets & resources. Do not copy a licensed assessment or present the demo form as an official Kegan-Lahey instrument.
2. Agree dated tasks for Rhea’s checks and chosen practice. Record the technical verification separately from the three live commitment opportunities. A task tick means the stated action was marked complete, not that the rollout or client’s development succeeded.
3. Name the private support route and its limit. In this case Tom is the sole coaching provider. Rhea may send one brief clarification in their one-to-one Messages conversation by 6 November at 12:00 Europe/London; Tom’s reply is due by 17:00 that day.
4. Keep workplace correspondence in its authorized work system. Rhea shares a short de-identified decision summary, without requester documents or colleagues’ personal information. Her unshared journal pages remain private. Where enabled, Share with coach lets her deliberately share an individual page with the coach. She can keep sensitive personal words unshared.
5. Check recap delivery before both sessions. Automatic sending is the default; select Approve before sending, check the session-type override and review the held recap before sending chosen client-facing content. Eva receives no private coaching reflection automatically.

Rhea actually sends her narrow question at 10:00 on 6 November: does a passed permission check also authorize live priority changes? Tom replies at 14:00 in the same conversation: the record shows a technical check, while Eva’s operating rule governs priority changes. No continuing asynchronous coaching is implied. The substantive review occurs in the second session.

The illustrated builder shows a demo wellness question. For this topic, create the original decision worksheet described above.

The goal view illustrates linked actions and reflections. Keep the case’s different evidence categories visible in the task wording and review notes. Explore the broader Coachful coaching features when designing the service.

Troubleshoot the classification before adding another intervention

The same problem returns after repair. First check whether the repair reached the actual user and situation. A successful dummy assignment cannot prove that every live category has the correct permission. Investigate new evidence rather than assuming recurrence proves a competing commitment.

The client wants a map for an absent employee. Return to what the employee has actually said and what the leader can verify. The leader can examine their own promises and interpretations. A personal map is not a covert performance assessment of someone who has not agreed to participate.

The experiment is designed to secure agreement. Rewrite it as a question with more than one informative outcome. Criticism, a refused proposal or an accurate prediction can all supply evidence. Do not make the other person’s compliance the sole definition of learning.

The issue exceeds coaching authority. Route technical, employment, legal or health questions to suitable expertise and the proper decision owner. Agree roles and information sharing explicitly. The current ICF Code of Ethics addresses agreements, confidentiality, boundaries and competence; it does not give a coach authority over the client’s employer.

Frequently asked questions

Are technical challenges always easy or quick?

No. They can require substantial expertise, money and time. Technical describes the availability of applicable knowledge and a specifiable requirement, rather than the effort or emotional intensity involved.

Can a challenge be both technical and adaptive?

Yes. A shared workflow may need repaired controls and new ways of resolving competing priorities. Record the components separately, verify repairs and investigate the remaining learning question. Do not force the whole project into one category.

Does knowing the answer but not acting prove immunity to change?

No. Missing authority, inconsistent incentives, inaccessible tools, workload or a reasonable objection may explain the pattern. A client can choose an Immunity to Change inquiry when it fits their own wanted change and the available evidence.

Should every adaptive challenge use a four-column map?

No. Some require collective negotiation, experimentation or changes to operating conditions. The map is one approach to investigating personal competing commitments and assumptions. It cannot substitute for another person’s participation or a director’s decision.

What is a useful first coaching question?

Ask for a recent event: “What did you try, what happened, and what do you know directly?” That creates a starting point for checking requirements and authority before deciding whether a deeper learning inquiry is appropriate.