THE CHANGE ARCHITECTURE
A Strategic Framework for Decoding Resistance and Recalibrating Transformation Integrating Insights from Behavioral Strategy, Organizational Politics, and Adult Development
Executive Summary
Organizations chronically misdiagnose change failure as a problem of willpower, skill, or commitment. The conventional prescription—more training, more incentives, more pressure—treats rational actors as defective machines. This framework introduces The Change Architecture—a diagnostic and intervention model built on a fundamentally different premise: resistance is not a defect to be fixed but a strategy to be decoded.
The framework rests on three foundational insights:
Every resistant behavior is a Protection Strategy. People and systems are not broken; they are executing strategies that have successfully delivered payoffs—safety, status, quality, certainty—for years. The problem is not the intent; it is the accumulating cost.
Individual protection operates by different mechanisms than organizational protection. Effective intervention requires distinguishing between psychological strategies (residing within individuals) and political-structural strategies (embedded in systems).
The goal is recalibration, not elimination. Resistance protects something the person or system values. Attempting to eliminate that protection triggers defensive escalation. Strategic recalibration preserves the protected value while reducing its cost.
Before reading further, you can run a live initiative through the diagnostic this framework is built on: the Change Architecture Diagnostic. About five minutes. Or read on — the tool will make more sense once you have the model.
This document provides a complete diagnostic and intervention methodology—including the Protection Equation (applicable at both individual and organizational scales), the Dual-Track Model, and the Strategic Recalibration Protocol—enabling leaders to decode the logic of resistance and design interventions that work with human nature rather than against it.
This framework sits at the intersection of adaptive leadership, adult development, behavioral strategy, and organizational politics. It draws from a simple observation: most failed change efforts are not blocked by lack of information, skill, or willpower. They are blocked by hidden commitments, identity threats, incentives, and power structures that make the current behavior rational—even optimal—from the actor’s perspective.
Part I: The Trap
Why Smart People and Successful Organizations Fail at Change
Every executive knows the pattern. The team agrees to the new initiative. The strategy is sound. The training is delivered. And then—nothing changes. Performance reviews carry the same feedback year after year. Post-merger culture integration stalls despite executive sponsorship. Digital transformation programs generate activity without impact.
The conventional diagnosis is seductive in its simplicity: people lack commitment, discipline, or capability. The prescription follows logically—more incentives, more training, more pressure. Yet this diagnosis is catastrophically wrong, and the prescription often makes things worse.
The Rational Actor Assumption
Here is the uncomfortable truth: the people “resisting” your change initiative are not irrational. They are executing a strategy that has worked for them—often for years or decades. That strategy delivers a payoff: safety, status, quality, certainty, control. The fact that this strategy now creates costs for the organization does not make it irrational from the individual’s perspective.
What appears to be a “broken” system is almost never broken. It is working precisely as designed—just not for the outcomes you want. The system is optimized to serve someone’s interests, protect someone’s position, or preserve someone’s identity. To change it, you must first understand what it is protecting.
The Legacy Code Problem
Consider a useful metaphor from software engineering: the behavior isn’t a bug; it’s legacy code.
When the employee “wrote” this behavioral code years ago, it was the perfect solution to protect their system from a crash—failure, embarrassment, loss of status. The code delivered a payoff. It worked. But the environment has scaled up, the organization has changed, and now that old code is causing latency—inefficiency, bottlenecks, friction.
The instinct of most change leaders is to “delete the code”—demand that the person simply stop the behavior. But deleting legacy code without understanding its function crashes the system. The person experiences the demand as an attack on something they value, and they defend accordingly.
The fix is not deletion; it is refactoring. We write a new script that protects the same value (stability, quality, reputation) but uses less processing power (time, energy, organizational friction).
The Core Insight
Resistance is not a character flaw. It is a protection strategy. Every “dysfunctional” behavior protects a hidden value, prevents a feared outcome, and operates on a governing belief that links the two. The path forward is not to attack the strategy but to decode it—then recalibrate.
Part II: The Diagnostic Foundation
Classifying the Challenge Before Designing the Solution
Effective intervention requires accurate diagnosis. The Change Architecture provides three critical diagnostic frameworks that must be applied before any intervention is designed.
Diagnostic 1: Technical Problem vs. Adaptive Challenge
The most consequential diagnostic question is: Is this a Technical Problem or an Adaptive Challenge?
Technical Problems, regardless of complexity, have known solutions that can be implemented by deploying existing expertise. (The distinction between technical problems and adaptive challenges was first articulated by Ronald Heifetz.) A surgeon removing an appendix is solving a technical problem. Installing new software is a technical problem. Technical problems yield to training, best practices, and expert intervention.
Adaptive Challenges are fundamentally different. They require the people with the problem to change their assumptions, beliefs, habits, and loyalties. No expert can solve an adaptive challenge for someone else because the change must happen inside the person or system.
The diagnostic test: Has this problem persisted despite multiple well-executed technical solutions? If yes, you are facing an adaptive challenge, and every additional technical solution will produce another cycle of failure.
The two diagnoses split cleanly across five dimensions:
Problem definition. Technical: clearly defined. Adaptive: contested.
Solution. Technical: known. Adaptive: requires discovery.
Who fixes it. Technical: expert can implement. Adaptive: the people with the problem must change.
Nature of change. Technical: additive—a new skill or tool. Adaptive: requires loss—beliefs, habits, identity.
Timeline. Technical: predictable. Adaptive: uncertain.
Diagnostic 2: Individual Strategy vs. Organizational Strategy
Once you have confirmed an adaptive challenge exists, the second diagnostic determines where the protection strategy resides. This distinction is critical because individual psychological change operates by fundamentally different mechanisms than organizational systemic change.
The two strategies differ across six dimensions:
Location. Individual: inside individuals. Organizational: embedded in systems.
Mechanism. Individual: personal beliefs, fears, identity. Organizational: structures, incentives, power, norms.
Timeline. Individual: hours to weeks. Organizational: months to years.
Facilitator. Individual: coach or trusted colleague. Organizational: leader with authority plus political skill.
Risk. Individual: emotional discomfort. Organizational: political backlash, career risk.
Primary tool. Both: the Protection Equation—applied at the appropriate scale.
The Dual-Track Test: If one person genuinely changed their behavior tomorrow, would the system support or punish that change? If support—this is primarily an Individual Strategy. If punish—this is primarily an Organizational Strategy. Most challenges involve both, requiring parallel interventions.
Diagnostic 3: Preemptive Decoding (The Sabotage Strategy)
While Diagnostics 1 and 2 are often applied to stalling initiatives, the most powerful application of this framework is preventative. Assume the protection strategy is already active before the kickoff meeting.
The Sabotage Strategy Protocol
Move the discovery of protection strategies from the middle of the project (troubleshooting) to Day One (strategy design).
The Inversion Question. Instead of asking “How do we succeed?” ask the leadership team: “If we were secretly committed to ensuring this project fails—while still appearing to support it—what specifically would we do?”
Typical Answers: “We would schedule the training during quarter-end close.” “We would nod in meetings but never allocate budget.” “We would critique the first prototype for not being perfect.”
Map to the Hidden Value. What is each sabotage behavior protecting?
Example: “We say we want innovation, but these behaviors reveal we are also protecting quarterly targets that affect our compensation.”
Design the Inoculation. Adjust the strategy to honor the protected value. If the hidden value is “protecting quarterly targets,” the strategy must include a “Safe Harbor” clause where the pilot team’s metrics are decoupled from short-term P&L.
Part III: The Protection Equation
The Core Diagnostic Tool
At the heart of this framework is a single diagnostic instrument: the Protection Equation. This tool decodes any resistant behavior by surfacing its hidden logic.
The Protection Equation
“This behavior is a Strategy that protects [Hidden Value] by preventing [Feared Outcome], based on the [Governing Belief] that these two are permanently linked.”
The Four Components
1. The Strategy (The Behavior)
What is the person doing—or not doing? This is the visible “symptom” that change leaders typically try to eliminate directly.
Example: “I am micromanaging my team” or “I am avoiding the new AI platform.”
2. The Hidden Value (The Asset)
What noble value is this behavior preserving? Resistant behaviors are never only dysfunctional. They always reflect something positive about the person holding them.
Example: “I am preserving High Quality Standards” or “I am protecting my Reputation as an Expert.”
3. The Feared Outcome (The Loss)
What specific loss is the strategy preventing? People resist loss, not change. Identifying the feared loss is the key to understanding the strategy’s logic.
Example: “I am preventing Reputational Damage from errors” or “I am preventing Irrelevance in my role.”
4. The Governing Belief (The Logic)
What is the assumption that connects the strategy to the value? This belief makes the strategy feel necessary—even when the costs are high.
Example: “I assume that only I possess the context required to ensure zero defects” or “I assume that admitting uncertainty will destroy my credibility.”
The Protection Equation in Action
Consider a manager who micromanages. The standard diagnosis labels this as “controlling behavior” or “lack of trust.” The standard prescription is coaching on delegation skills—a technical fix.
The Protection Equation reveals a different picture:
“Micromanaging is a Strategy that protects Quality Standards by preventing Reputational Damage, based on the Governing Belief that only I can ensure zero defects.”
Now the intervention changes entirely. We are not asking the manager to “stop caring about quality” (which attacks the Hidden Value). We are asking: “Is your Governing Belief accurate? Is there another strategy that could protect Quality Standards without the cost of bottlenecking your team?”
The Protection Equation at Organizational Scale
The Protection Equation is also the core diagnostic at organizational scale. The first three components stay the same. The key adaptation comes in the fourth component: when the pattern is systemic, Governing Belief becomes Governing Logic—a shared assumption plus the coalition and structural mechanisms that enforce it.
“This pattern is a Strategy that protects [Institutional Value] by preventing [Institutional Risk], based on the Governing Logic that [shared assumption], enforced by [stakeholders + structures].”
Compare the two scales using a recurring example—Sarah, an HR operations manager (individual), and Marcus, a Regional Sales VP (organizational):
Strategy. Sarah: delaying AI deployment. Marcus’s sales org: rejecting data-driven selling.
Hidden Value. Sarah: being needed as rescuer. Marcus’s org: customer relationships and personalized service.
Feared Outcome. Sarah: irrelevance. Marcus’s org: loss of the sales-artisan identity that built the company.
Governing Belief / Logic. Sarah: “If I’m not manually solving problems, I’m not valued.” Marcus’s org: “Relationships beat algorithms”—enforced by commission structures that reward whale-hunting, promotion criteria that privilege executive presence over data fluency, and cultural rituals built around war stories.
At the individual level, the Governing Belief is a single testable assumption. At the organizational level, the Governing Logic is a shared assumption plus the enforcement apparatus and beneficiaries that keep it in place. You cannot recalibrate the organizational strategy without identifying both the assumption and the structures that sustain it.
The Virtue-in-Overdrive Reframe
At the organizational level, leaders often fill in the Hidden Value by naming a dysfunction: information hoarding, risk aversion, bureaucratic delay. The better move is to ask which institutional virtue has been dialed too high:
Information hoarding becomes data-integrity commitment in overdrive.
Risk aversion becomes quality standards in overdrive.
Bureaucratic slowness becomes thoroughness in overdrive.
This reframe is what makes organizational recalibration politically viable. When the Hidden Value is named as a virtue, the people enforcing it can become allies in redesign rather than enemies to defeat.
Interlocking Equations: Decomposing Complex Organizational Strategies
Some organizational strategies are maintained by multiple stakeholders with different motivations. In those cases, a single system-level equation is not enough. Use Interlocking Equations as an advanced diagnostic.
Method: identify the 3–5 key stakeholders who benefit from the current strategy. Run a Protection Equation on each. Then map how their individual equations interlock to produce the systemic pattern.
In Marcus’s sales org, three stakeholders sustain the same systemic pattern through different protection strategies:
Marcus (Sales VP).
Strategy: undermine AI adoption.
Hidden Value: artisan identity.
Feared Outcome: irrelevance.
Governing Belief: relationships beat algorithms.
CFO.
Strategy: maintain current comp structure.
Hidden Value: predictable forecasting.
Feared Outcome: compensation chaos mid-transition.
Governing Belief: don’t change comp during a sales cycle.
Sales Culture Carriers.
Strategy: celebrate intuitive wins.
Hidden Value: tribal belonging.
Feared Outcome: cultural erasure.
Governing Belief: our way is what makes us us.
The diagnostic payoff is practical:
Which equation to crack first—identify the highest-leverage belief to test, usually the one with the weakest empirical foundation.
Who to recruit as allies—find stakeholders whose Hidden Values are compatible with the change.
What structural mechanisms to redesign first—target the enforcement apparatus that is easiest to modify and most visible to the organization.
Facilitation note: running nested equations requires more skill than a single equation. This is leadership-team-level diagnostic work, not individual coaching. The facilitator needs authority and political skill, and the session has to feel like strategic analysis rather than personal accusation.
Part IV: The Individual Track
Strategic Recalibration for Personal Protection Strategies
When diagnosis confirms an Individual Strategy—the protection resides within a person rather than the system—the intervention is Strategic Recalibration. The goal is not to eliminate the protective behavior but to adjust its setting.
The Recalibration Dial (adapted from David Burns’ magic dial technique): the current protection strategy is dialed to 100 percent—maximum protection, maximum cost. The question is: what setting would preserve the benefit while reducing the cost?
A manager who would never agree to “stop caring about quality” might readily agree to “reduce my quality-anxiety dial from 90 to 25, which would allow me to delegate routine work while maintaining oversight on critical deliverables.”
This reframe transforms the goal from “stop being controlling” (which attacks identity) to “recalibrate from 90 to 25” (which preserves values while expanding capacity).
Part V: The Organizational Track
Applying the Protection Equation to Systems
When diagnosis indicates an Organizational Strategy—protection embedded in structures, incentives, power dynamics, and cultural norms—individual recalibration is insufficient. The manager may genuinely want to delegate, but the system punishes delegation.
The same Protection Equation applies, but the fourth component shifts: from Governing Belief (personal) to Governing Logic (an institutional assumption plus the enforcement apparatus that keeps it in place).
The Guardian Metaphor
Consider a useful way to think about organizational resistance: the dysfunctional behavior is a Guardian protecting a Treasure.
The Guardian is the organizational Protection Equation made visible. The Guardian (Strategy) protects the Treasure (Hidden Value) by blocking entry (preventing the Feared Outcome), following standing orders (the Governing Logic). The organization has placed that Guardian at the door to protect quality, data integrity, reputation, or customer trust.
But the Guardian has become so aggressive they are not letting allies in either. Innovation cannot enter. New processes cannot enter. Change cannot enter.
Recalibration means rewriting the Guardian’s instructions, not firing the Guardian. Instead of “Block Everyone,” the new instruction is “Verify and Trust.”
Where to Look for the Governing Logic
These five structural barriers are the enforcement apparatus. When you fill in the Governing Logic at the organizational level, scan each mechanism to see where the shared assumption lives and how it is enforced.
Incentive Misalignment. The reward system punishes the desired behavior or rewards the unwanted behavior. Example: espousing innovation while promoting only those with zero failures.
Power Concentration. Key stakeholders benefit from the status quo and have the authority to block change. Example: senior leaders whose identity is tied to the current strategy.
Information Control. Relevant information is hoarded, filtered, or distorted as it moves through the organization. Example: bad news is softened at each level until leadership receives an inaccurate picture.
Cultural Norms. Unwritten rules about acceptable behavior prevent the needed actions. Example: “We don’t disagree with leadership in meetings.”
Historical Precedent. Past consequences create learned helplessness. Example: “The last person who raised that issue was marginalized.”
Running the Protection Equation at the Organizational Level
This is the facilitation sequence for filling in the equation at system scale:
Step 1: Name the Pattern (Strategy). What is the organization doing or not doing? Use neutral language: “The sales organization consistently deprioritizes AI-assisted pipeline management.”
Step 2: Decode the Institutional Value (Hidden Value). Apply the Virtue-in-Overdrive reframe. What noble institutional value is this pattern protecting? “A fierce commitment to customer relationships and personalized service that built the company’s reputation.”
Step 3: Surface the Institutional Risk (Feared Outcome). What loss would the organization experience if the pattern stopped overnight? “Loss of the relationship-driven culture that differentiates us from competitors.”
Step 4: Map the Governing Logic. What shared assumption links the strategy to the value? And who enforces that assumption through incentives, metrics, promotion criteria, information flows, and cultural norms?
Step 5: Design the Recalibration. Preserve the value, reduce the cost, and test the assumption. At the organizational level, recalibration requires changes to structures—incentives, metrics, promotion criteria, and decision rights—not just beliefs. The Sabotage Strategy Protocol is the preemptive version of this step.
This keeps the organizational track inside the same diagnostic architecture: one Protection Equation, applied at the scale of the system. The Virtue-in-Overdrive reframe helps name the institutional value. The structural barriers reveal the enforcement apparatus. Together they make redesign politically workable.
Part VI: In Practice
Two Case Studies in AI Business Transformation
The following cases illustrate both tracks of the Change Architecture in action. Marcus demonstrates an Organizational Strategy requiring the Protection Equation at organizational scale. Sarah demonstrates an Individual Strategy requiring Strategic Recalibration. Both involve the same adaptive challenge: AI adoption threatening professional identity.
Case Study 1: The Sales “Artisan” (Organizational Track)
The Situation
Marcus is a Regional Sales VP at a global B2B firm. The company is shifting from “gut-feel” selling to an AI-driven Revenue Intelligence platform that scores leads and prescribes next-best actions.
Marcus is a “rainmaker.” He built his career on intuition, deep relationships, and closing massive deals over steak dinners. In town halls, Marcus praises the AI investment as “the future.” But in practice, his region’s adoption metrics are near zero. He privately tells his account executives, “Don’t let the algorithm distract you from the relationship. Trust your gut; the bot doesn’t know this client like we do.”
The Standard Diagnosis: Marcus is a “luddite” stubbornly refusing to modernize. The standard prescription is more training sessions on the dashboard—a technical fix.
Diagnostic Phase
Technical vs. Adaptive: Training has been delivered repeatedly. Nothing changed. This is an Adaptive Challenge.
Individual vs. Organizational: Apply the Dual-Track Test. If one sales rep genuinely adopted the AI platform, would the system support or punish that behavior?
Analysis reveals the system would punish it:
Commission structures reward relationship-based “whale hunting,” not AI-optimized pipeline management.
Promotion criteria emphasize “executive presence,” not data fluency.
Sales culture celebrates “war stories” of intuitive wins, not algorithmic efficiency.
This is primarily an Organizational Strategy. Marcus is not merely an individual resistor—he is the visible embodiment of a system optimized to protect the “sales artisan” identity.
Applying the Protection Equation at Organizational Scale
Decoding the Institutional Value (Virtue-in-Overdrive): Leadership’s instinct is to label the sales culture as “broken.” But the Protection Equation reveals:
The Strategy: rejection of data-driven selling.
The Institutional Value: a fierce commitment to customer relationships and personalized service that built the company’s reputation.
The Pivot: Instead of framing AI as “replacing intuition,” reframe it as “protecting relationships at scale.” The message: “Your instincts built this business. The AI ensures no relationship falls through the cracks while you focus on the deals only you can close.”
Applying the Sabotage Strategy: Leadership asked: “If we were secretly committed to ensuring AI adoption fails, what would we do?”
Answers: “Keep the current commission structure. Let Marcus quietly signal resistance. Measure adoption by logins, not outcomes.”
Inoculation Design:
Create a “hybrid comp” model that rewards both relationship wins and AI-assisted pipeline growth.
Engage Marcus as a “co-designer” of how AI insights are presented.
Measure success by deal velocity and forecast accuracy, not dashboard logins.
Create visible wins where AI helped a rainmaker close faster.
Case Study 2: The “Benevolent Rescuer” (Individual Track)
The Situation
Sarah is an HR Operations Manager at a logistics firm. The company is introducing AI to automate complex tasks like shift scheduling and payroll error detection—tasks Sarah used to handle manually.
Sarah is known as the “team mom.” She stays late to fix problems personally and is beloved for saving employees from administrative crises. Unlike Marcus, Sarah is deeply involved in the AI pilot. However, she constantly finds small reasons why it isn’t ready. “It flagged a false positive on holiday pay,” she reports, demanding another month of manual double-checking.
The Standard Diagnosis: Sarah is conscientious and risk-aware. Leadership views her stalling as valuable due diligence.
Diagnostic Phase
Technical vs. Adaptive: Sarah understands the technology. Yet implementation remains perpetually “almost ready.” This is an Adaptive Challenge.
Individual vs. Organizational: Apply the Dual-Track Test. If Sarah fully adopted the AI platform tomorrow, would the system support or punish that behavior?
Analysis reveals the system would support it. Leadership wants automation. There are no structural barriers.
This is primarily an Individual Strategy. The protection resides inside Sarah.
Applying Strategic Recalibration
Phase 1: DECODE. Sarah’s manager facilitates a conversation using the Protection Equation:
The Strategy: finding reasons to delay AI deployment.
The Hidden Value: being needed—being the “rescuer” who saves employees from crises.
The Feared Outcome: irrelevance. “If I’m not personally saving the day, what am I?”
The Governing Belief: “If I am not manually solving problems, I am no longer valued here.”
Phase 2: HONOR. The manager validates: “Your instinct to protect people is exactly why you’re valuable. The question isn’t whether to stop caring—it’s whether caring requires you to personally process every payroll exception.”
Phase 3: RECALIBRATE. Using the dial metaphor:
Manager: “On a scale of 0–100, where is your anxiety about the AI making errors?”
Sarah: “Probably 85.”
Manager: “If you could turn that dial down to 25—still vigilant, but not requiring your personal intervention on every transaction—would that feel acceptable?”
Sarah: “Yes… at 25 I could let the system handle routine cases while I focus on the complex ones.”
Phase 4: TEST. Sarah designs experiments:
Experiment 1: Let AI process one week of routine scheduling. Prediction: “Employees will blame me.” Observe actual results.
Experiment 2: When thanked for solving a problem, disclose: “The system caught that one.” Prediction: “They’ll be disappointed.” Observe actual reaction.
Experiment 3: Spend saved time redesigning onboarding. Prediction: “Leadership won’t notice.” Observe actual feedback.
The Lesson from Both Cases
Marcus and Sarah faced the same adaptive challenge: AI threatening professional identity. But Marcus required organizational intervention (changing the system’s instructions to the Guardian), while Sarah required individual intervention (recalibrating her personal protection dial). Misdiagnosing the track guarantees failure. Accurate diagnosis enables transformation.
Part VII: The Diagnostic Toolkit
Five Questions for Monday Morning
Before designing your next change initiative, work through these diagnostic questions.
Question 1: Have we tried this before?
If the problem has persisted through multiple well-intentioned interventions, you are facing an Adaptive Challenge, not a Technical Problem. Stop adding new training programs. Start decoding the protection strategy.
Question 2: Where does the protection strategy reside?
If one person genuinely changed their behavior, would the system support or punish that change? If support—focus on Individual Strategy using Strategic Recalibration. If punish—focus on Organizational Strategy using the Protection Equation at organizational scale. If both—run parallel interventions.
Question 3: How would we sabotage this if we wanted to?
Before the kickoff meeting, ask the leadership team: “If we were secretly committed to ensuring this project fails—while still appearing to support it—what specifically would we do?” The answers reveal the protection strategies already active in the system. Design your initiative to honor those hidden values while reducing their costs.
Question 4: What is this resistance protecting?
Apply the Protection Equation. For individuals, resistance reflects positive core values in overdrive—quality, reliability, expertise. For organizations, dysfunction often masks institutional virtue—data hoarding protects integrity, risk aversion protects quality. Name the hidden value. Honor it. Then explore whether it requires this particular protective behavior.
Question 5: What experiment would we never run?
The test that feels too risky to attempt is usually the one that would most directly challenge the Governing Belief holding the protection strategy in place. Design a smaller, safer version. Run it. Observe what actually happens rather than what you assumed would happen.
If you want a structured version of these questions applied to a specific initiative — with the Protection Equation surfaced for you — Altipoint’s Change Architecture Diagnostic runs the full sequence interactively.
Conclusion: From Protection to Capacity
The Change Architecture does not promise that transformation will become easy. Adaptive challenges remain genuinely difficult because they require people to tolerate loss—loss of certainty, loss of competence, loss of identity. What the framework offers is accuracy: a precise diagnosis of why change fails and a structured methodology for addressing the real obstacles rather than the imagined ones.
The deepest insight is this: resistance is not a defect to be fixed but a strategy to be decoded. Every protection strategy—individual or organizational—guards something the person or system values. The path forward is not to attack that protection but to recalibrate it: preserve the benefit while reducing the cost.
Leaders who master this framework do not eliminate resistance. They decode it, honor it, and redirect it. In doing so, they transform protection into capacity—not just for this change, but for the continuous adaptation that the future demands.
Decode. Honor. Recalibrate.
Sources and Intellectual Lineage
This framework synthesizes and applies several bodies of work: adaptive leadership, adult development, behavioral strategy, cognitive-behavioral approaches to resistance, premortem thinking, and organizational politics.
I am especially indebted to Ronald Heifetz, Alexander Grashow, and Marty Linsky for the distinction between technical problems and adaptive challenges (The Practice of Adaptive Leadership), and to Robert Kegan and Lisa Laskow Lahey for the immunity-to-change dynamic, competing commitments, and big assumptions (Immunity to Change; The Real Reason People Won’t Change, HBR 2001). I also draw on David D. Burns for positive reframing and the magic dial technique (Feeling Great), Gary Klein for the premortem method, and Michael Bungay Stanier for the distinction between easy change and hard change (The Advice Trap).
The Change Architecture is my attempt to integrate these ideas into a practical diagnostic model for leaders, strategists, and change agents navigating AI transformation and other adaptive challenges.