Change Management & Adoption

The discipline of institutionalizing organizational change so it becomes durable — urgency, coalition, vision, communication, quick wins, and structural anchoring (Kotter, Fearless Change, ADKAR, Lewin) — the org-wide arc distinct from the tactical upward influence of managing-up.

Also known as: change management, change adoption, Kotter's 8 steps, Kotter, Fearless Change, ADKAR, Lewin, make it stick, organizational change adoption, institutionalizing change

Documents (10)

• Welcome to AI Autumn Gretchen Gavett · 2026-09-08 source ↗ Reader 🖥️
  Two distinct claims coexist under one masthead: leaders can find profitable new market space not by outcompeting rivals but by removing industry-imposed pain points for excluded noncustomers (illustrated via Midea's air-conditioner redesign), and HBR's own newsletter readership currently ranks 'leading through change and uncertainty' as its top self-reported leadership challenge, ahead of workload, career advancement, influence, and organizational politics.
• The person your firm needs and cannot name Ernie Svenson · 2026-09-04 Reader 🖥️
  Most small firms silently need, and almost never deliberately hire for, an operational-integrator role (a 'fractional integrator') that translates the owner's vision into execution and fixes broken processes before automating them — a need AI is making more acute, not less, because the hard part has shifted from building tools to deciding what they should do and training people through the change.
• Is Your Organizational Culture Too Nice? Ron Ashkenas, Gali Cooks · 2026-08-19 source ↗ Reader 🖥️
  Organizational cultures of "niceness" — which prioritize harmony, comfort and consensus over candor, accountability and results — measurably compromise performance, and leaders can reverse this by modeling peer candor at the senior-team level (starting with the CEO), demonstrating the results of rigor through data-backed pilots, and redesigning operational review and governance meetings so they require substantive debate rather than ratify decisions as a fait accompli.
• Strategi som regi i møte med teknologi: En samtale med Walter Qvam Verdistrategipodden (Tale Skjølsvik interviewing Walter Qvam) · 2026-08-01 Reader 🖥️
  Strategy is best understood not as a detailed analytical plan but as an ambition or aspiration compressed into a believed, narratable direction that a leader — acting as a director/orchestra-conductor rather than a soloist — uses to make an organization's culture willing and able to execute; and because plans now have a shorter shelf life than ever, strategic success increasingly depends on combining proactive bet-making with the honesty and speed to detect weak signals and respond to the unforeseen (robustness), rather than treating proactive and reactive strategy as opposites.
• Model the Transformation You Expect Employees to Deliver Antonio Nieto-Rodriguez · 2026-07-22 source ↗ Reader 🖥️
  Organizational transformations succeed or fail not because employees resist change but because senior leaders either do or do not visibly perform, in their own calendars and decisions, the same risk-taking, uncertainty-tolerance, and willingness-to-reverse-course they are asking employees to adopt.
• Frontline Workers Know How to Solve Your Organization's Biggest Problems Constance Noonan Hadley and Deborah Lovich · 2026-07-20 source ↗ Reader 🖥️
  Organizations can surface frontline employees' accurate, granular knowledge of what's broken in their work — and rebuild the trust that generic engagement surveys erode — by replacing periodic top-down surveys with a disciplined, iterative cycle of confidential listening, quantified diagnosis, employee-cocreated and ranked solutions, and piloted, repeated experimentation.
• How Leaders Can Use AI to Solve Real Business Problems Harvard Business Review · 2026-07-07 source ↗ Reader 🖥️
  Successful AI adoption is determined less by which model or vendor an organization chooses than by whether it first identifies a specific, well-understood business problem, hands ownership to domain experts who genuinely care about that problem, builds trust through explainability and honest communication, and resists the frontier labs' self-interested narrative that missing the AI 'wave' is existential.
• DORA Community Discussion - Operationalizing DORA within a large organization DORA (speaker: Julia Jakubiec, ABN AMRO; host: Nathan Harvey) · 2026-06-26 source ↗ Reader 🖥️
  Operationalizing DORA at enterprise scale is fundamentally a change-management problem — solved by running Kotter's 8 steps to institutionalize a durable continuous-improvement culture — not by the metrics themselves, which serve only as a recognizable survey instrument, authority brand, and benchmarking catalyst.
• Your AI agent just blamed the network team. Now what? Nik Kale · 2026-06-15 source ↗ Reader 🖥️
  Deploying autonomous, cross-domain AI diagnostic agents in production incident response introduces a new organizational-political risk -- a confidently-asserted, team-implicating finding that may be contested -- and that risk is best managed not by better AI reasoning but by a deliberately staged trust-building process (investigation-scoped credentials, a read-only start, an auditable reasoning trail, and treating rollout as organizational change with pre-secured cross-team buy-in) that earns autonomy incrementally rather than being engineered away as a purely technical problem.
• Gene Kim on Vibe Coding - Part III | Episode 412 | Troubleshooting Agile Douglas Squirrel · 2025-12-24 source ↗ Reader 🖥️
  Agentic coding tools work by letting the AI observe and check the effects of its own actions rather than just chatting, which shifts the developer's job from writing code to decomposing problems into task graphs and delegating pieces to AI — a scarce, teachable combination of specification and delegation skill (not raw coding ability) that now determines who benefits, while the same power that makes the tools valuable (a 'sawzall') makes them dangerous if used past their original disposable-prototyping purpose without guardrails and supervision.

Propositions touching this concept (3)

By publication month, oldest first (extraction month when no publication date is known).

2026-05

• explicitdevelopedA single control plane managing a million chips creates significant blast radius and change management risk
  Google Announces GKE Agent Sandbox and Hypercluster at Next '26 · p4
• explicitTraditional change management is actually a form of control, not change, because it assumes one group directs others rather than deciding together.
  New Skills to Navigate Continuous Change · p1

2026-08

• explicitVisible token/API costs understate the true cost of AI deployment; substantial 'shadow costs' — infrastructure, power, in-house tech teams, training, and change management — sit on top of them.
  How to Respond to the Coming AI Cost Shock · p5

Open gaps (19)

• illogicalThe piece claims AI evidence is 'harder to dispute' and removes political deflection, yet also insists cross-team buy-in must be secured up front and treated as organizational change -- i.e., the very political dynamics the system is supposed to bypass are simultaneously treated as a prerequisite gate on the system's legitimacy. It never reconciles whether evidence overrides politics, or politics still governs whether evidence gets heard at all.
  Your AI agent just blamed the network team. Now what? — read next: Change-management and blameless-postmortem literature on whether objective/dashboard data changes minds independent of prior trust, or whether distrust causes inconvenient data to be rejected regardless of rigor.
• incompleteTeam adoption is treated as an exercise for the reader. Pocock's answer to 'how does this work in a team?' is essentially: 'the upstream becomes team-shared, the downstream is one or two devs managing the pipeline.' He gives no story for: review queue scaling, distribution of PRD-authoring authority, who owns skills/coding-standards as a shared asset, code-review burden as a team-wide labour question, or how juniors learn craft in a workflow where most code is agent-written.
  [FULL WORKSHOP] AI Coding For Real Engineers - Matt Pocock, AI Hero — read next: Cutler on overload and accountability culture; Beck on socio-technical change; Fearless Change for the adoption-of-practices angle in the user's hidden-layer interests.
• illogicalThere is a tension between 'don't mandate AI' and 'the fastest learners will win.' If organizational learning speed is the competitive differentiator, laissez-faire adoption may be too slow. The panelists don't reconcile this.
  Designing the AI-native engineering organization — read next: Change management literature on balancing autonomy with urgency in technology adoption
• incompleteNo treatment of the social-and-organisational fate of the artefacts themselves. Dependency-cruiser configs, custom coupling-analyser CLIs, and imported Modularity Skill packs are all new load-bearing artefacts. Who owns them? Who updates them when the architecture should change? In the absence of an owner, the rules outlive the intent behind them and become either silently violated or silently obsolete — the classic linter-suppression-debt pathology, scaled to architecture.
  Three more static code analysis sensors — read next: Cutler on institutionalised overload and waste; Fearless Change (Manns & Rising) on what it takes for organisational invariants to survive; Tornhill's Software Design X-Rays on attaching social/ownership data to code-quality signals; Vlad Khononov's modularity work directly (since his Skills are now part of the harness).
• incompleteThe inverted generational-adoption pattern (oldest and youngest adopt fastest, mid-career senior staff resist most) is offered with a speculative explanation ('maybe they feel like they have the most to lose') but no structural account of why — e.g. compensation tied to code-authorship credit, identity investment, or performance-review design — is tested against alternatives.
  Gene Kim on Vibe Coding - Part III | Episode 412 | Troubleshooting Agile — read next: extract-hbr-hidden-realities-ai-adoption-roundtable#p13 documents a related but distinct reverse-generational-bias finding (younger workers trusting AI less than senior ones) — worth reading against this episode's claim to see whether they describe the same phenomenon or two different ones (trust vs. active resistance; junior vs. mid-career).
• incompleteThe article assumes the seller possesses time, network, political cover, and emotional regulation as preconditions. It does not address how to do issue selling when one or more of those is unavailable — i.e., the typical condition of overloaded mid-level managers.
  Getting Buy-In for Your Next Big Idea — read next: Time to Think (Kline) on the conditions ideas need; Stolen Focus on attention as precondition; Fearless Change patterns for resource-poor change agents.
• incompleteAdler's mode of incompleteness: the article reduces idea transmission to tactics and scripts ('three questions,' 'map the stakeholders,' 'aim for worth exploring'). The structural conditions under which those tactics actually work — slack in the executive agenda, trust between layers, a culture that distinguishes loyalty to leaders from loyalty to ideas — are presupposed and never named. The advice is therefore most useful exactly where it is least needed (healthy organizations) and least useful where it is most needed (organizations whose pathology is what makes upward selling necessary in the first place).
  Getting Buy-In for Your Next Big Idea — read next: Fearless Change (Manns & Rising) — patterns for getting ideas through resistant organizations; Time to Think (Nancy Kline); Cutler's 'institutionalized overload' essays; Donella Meadows on leverage points (rule-changes, paradigms) vs. parameter-changes.
• incompleteNo comparison group, pre-existing trend baseline, or control for the concurrent organizational/leadership change the article itself mentions mid-case is offered, so the reported improvements (pulse scores, stable adherence, on-schedule coaching rollout) cannot be separated from simple attention effects (Hawthorne-type), regression to the mean from a poor starting baseline, or the coincident leadership transition.
  Frontline Workers Know How to Solve Your Organization's Biggest Problems — read next: Methodologically rigorous employee-intervention studies with control groups; critiques of single-case consulting case studies as an evidence class.
• uninformedThe article discloses no cost figures — consultant fees, roughly 100 hours of confidential frontline interviews plus survey time plus three 90-minute focus groups plus multiple town halls, and five months of engagement by two outside institutions — needed to weigh the return of this 'disciplined process' against its resource intensity before an organization adopts it as a portable method.
  Frontline Workers Know How to Solve Your Organization's Biggest Problems — read next: Cost-benefit or ROI studies of large-scale employee-listening / engagement interventions.
• incompleteThe authors are the intervention's own designers evaluating their own consulting engagement's success: Lovich is a BCG senior partner co-authoring a forthcoming book built on this exact framework, and the survey used is a named, proprietary BCG instrument. No independent verification, peer replication, or disconfirming case is offered — read against the stated skepticism of consulting-firm frameworks, the piece is more evidenced and quantified than a typical McKinsey/BCG listicle (real response rates, real before/after timing data, a named survey instrument with specific dimensions), but it is still, structurally, a case study written by the vendor about the vendor's own product, doubling as pre-publication marketing for Lovich's book.
  Frontline Workers Know How to Solve Your Organization's Biggest Problems — read next: Independent (non-consultant-authored) accounts of similar frontline-listening interventions; critiques of practitioner-authored HBR case studies as an evidence genre.
• incompleteTyrangiel notes the US federal job-retraining program 'died in 2022' with 'no effort... to bring it back up,' but never explains why it ended, what (if anything) replaced it at the state or private-sector level, or what a leader relying on external retraining infrastructure should actually expect today. This is left as an assertion of absence rather than a mapped current landscape.
  How Leaders Can Use AI to Solve Real Business Problems — read next: Read current US labor-policy reporting on workforce retraining funding post-2022 to establish what infrastructure (if any) leaders can actually draw on for broad (non-'training up') retraining.
• incompleteThe central causal claim — that niceness culture measurably compromises financial performance and rigor culture measurably improves it — rests entirely on the authors' own consulting anecdotes plus a single Bain survey about behavior prevalence (not about performance outcomes). No controlled comparison, industry benchmark, or correlational study directly connects "niceness" to performance metrics.
  Is Your Organizational Culture Too Nice? — read next: Organizational-culture research with actual performance correlations (e.g., Kotter & Heskett's culture-and-performance work, or Denison culture-survey studies) to test whether the niceness/performance link holds outside these authors' own client base.
• illogicalThe Bain statistic ("only one in five of the highest-performing teams consistently exhibit these behaviors") is used to argue candor is rare and valuable, but on its face it also shows four in five top-performing teams do NOT consistently exhibit these behaviors — i.e., high performance is evidently possible without them most of the time. The article doesn't reconcile this tension.
  Is Your Organizational Culture Too Nice? — read next: The original Bain "At the Top, It's All About Teamwork" study, to see whether Bain's own analysis treats these behaviors as necessary, sufficient, or merely correlated with top-quintile performance.
• incompleteThe article never specifies how a leadership team gets from failing the three tests to passing them, beyond one anecdote (a new CEO personally taking ownership of two hard initiatives). It gives no account of what happens when a team recognizes it is failing but the CEO who would need to change their calendar is the same person unwilling or unable to do so — the article's own logic (leaders cannot delegate this) implies there is no remediation path that does not run through the top person's own willingness, but this implication is never stated or examined.
  Model the Transformation You Expect Employees to Deliver — read next: Read against literature on board-level accountability and CEO succession/removal for cultural failure (relevant given the Credit Suisse case itself ended in the chairman's own removal), and against change-management frameworks (e.g., Kotter, ADKAR) that specify sequencing and remediation steps rather than only diagnostics.
• incompleteEvery case in the article — Gupta, Horta-Osório, the unnamed industrial-company CEO, the energy-company CEO, the pharma CFO, the retail-bank CEO — sits at CEO, chairman, or C-suite level. The article's own opening claim ('the bottleneck is at the top') is never tested against a case where the bottleneck is one level below the top: a business-unit leader or VP whose own boss is not modeling the transformation. It is left unaddressed whether visible modeling by a sub-CEO leader can still move their own team's behavior, or whether the effect requires the very top of the hierarchy to model it.
  Model the Transformation You Expect Employees to Deliver — read next: Read alongside middle-management- or informal-leadership-focused accounts of change agency operating without top-level air cover, to test whether 'modeling' works bottom-up/mid-up or only top-down.
• incompleteThe McKinsey and Prosci statistics (5.3x more likely to succeed; 79% vs 27%) are presented as if the causal arrow runs cleanly from leader modeling to transformation success. The article does not consider or rule out reverse causation (transformations that are already succeeding for other structural reasons — better resourcing, less internal politics, a healthier starting culture — may simply free leaders to model behavior visibly, rather than the modeling causing the success) or confounding (leaders confident and secure enough to visibly take personal risk may be systematically different, and more effective for unrelated reasons, from leaders who are not).
  Model the Transformation You Expect Employees to Deliver — read next: Read alongside the original McKinsey and Prosci methodology write-ups to check whether either study attempts to control for confounds or establish direction of causality, or is purely correlational self-reported benchmarking.
• uninformedThe article treats the Credit Suisse collapse as if the modeling failure were the decisive cause ('at its heart is Horta-Osório's failure to embody and model the transformation'), while its own text names the Greensill and Archegos losses (the latter alone costing about $5.5 billion) as having already 'laid bare' the cultural problem before Horta-Osório's appointment. It does not engage with the possibility that Credit Suisse's fate was already largely sealed by those prior losses and the resulting collapse in market and counterparty confidence, independent of whether the chairman personally modeled accountability afterward.
  Model the Transformation You Expect Employees to Deliver — read next: Read banking-sector post-mortems on Credit Suisse's collapse (regulatory reports, the Swiss FINMA assessment) that weigh governance/risk-control failures against leadership/cultural factors, to establish whether the modeling-failure framing is proportionate to its actual causal weight.
• incompleteCutler's prescription ('surf the tension', 'find pockets') leaves the change agent without a diagnostic for distinguishing a real pocket of opportunity from a temporary opening that will close, or from a trap that consumes effort without producing change. The post advises a posture but not a method.
  TBM 423: Why Defining Teams Is So Hard — read next: Donella Meadows' 'Places to Intervene in a System' (leverage points hierarchy) supplies the missing taxonomy of where intervention has high leverage. Fearless Change (Manns & Rising) — which Kjetil's persona shows he highlights heavily — supplies pattern-level guidance for what to do once a pocket is identified.
• incompleteThe piece gives no account of the mechanics of engaging a fractional integrator — hours, cost, exclusivity across client firms, or confidentiality/conflicts when working across competing law firms — despite this being exactly the practical detail a reader would need to act on the advice.
  The person your firm needs and cannot name — read next: Fractional-executive (fractional COO/CFO) literature on engagement structuring and conflict management across multiple client firms.