Leadership Under Pressure

How leaders are tested and destabilized by crisis, transition, unfair blame, and conflict — resilience-governance mandates created to manage disruption, the instability of interim/transitional leadership, the systemic tendency to blame effective leaders for problems the organization itself produced, and classical-strategy principles (Clausewitz) for handling conflict without losing the objective. Distinct from the corpus's engineering-leadership cluster (informal-leadership, dual-leadership, hands-on-leadership, etc.).

Also known as: chief resilience officer, resilience officer, interim CEO, interim leadership, evaluation trap, leaders branded as problems, organizational drift, governance gap, horizontal mandate, cascading disruption, center of gravity, the enemy gets a vote, conflict taking command

How authors use it

Oldest first (extraction date when no publication date is known).

Documents (5)

• We've Stopped Arguing About Whether AI Changes Software Greg Herlein · 2026-07-07 source ↗ Reader 🖥️
  The debate over whether agentic AI transforms software engineering is settled; the transformation is a shift in the center of gravity of the work — from writing code to specifying, verifying, and curating knowledge.
• How To Handle Conflict: 7 Secrets From History's Master Strategist Eric Barker · 2026-05-25 source ↗ Reader 🖥️
  To stop conflict from running your life, treat every interpersonal fight the way Clausewitz told generals to treat war — by subordinating it to a concrete purpose, accepting incomplete information, hitting the real center of gravity, preferring patient defense, planning for the other side's agency, prizing morale over material, and stopping the moment the cost of pressing on exceeds the gain.
• Why Effective Leaders Get Branded as Problems Luis Velasquez · 2026-05-07 source ↗ Reader 🖥️
  Organizations systematically misdiagnose leadership friction by defaulting to behavioral explanations — the 'evaluation trap' — when the actual source is more often historical reputation, strength overextension, or systemic constraints, and this misdiagnosis causes them to neutralize their most effective leaders.
• The Case for Hiring a Chief Resilience Officer Igor Linkov · 2026-05 source ↗ Reader 🖥️
  Modern enterprises face a structural governance gap because resilience-as-an-enterprise-wide capability has no single accountable executive, and the remedy is a Chief Resilience Officer with horizontal authority to coordinate recovery across functions that risk, security, operations, and continuity leaders each only see in part.
• The Pitfalls of an Interim CEO Adi Ignatius · 2026-03-26 source ↗ Reader 🖥️
  Appointing an interim CEO as a 'safe' response to unexpected leadership transitions is a trap — research shows it systematically triggers negative stakeholder reactions and long-term value destruction, making it a less safe option than it appears.

Propositions touching this concept (9)

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

2026-03

• explicitAppointing an interim CEO appears to be a safe response to sudden leadership gaps
  The Pitfalls of an Interim CEO · p1
• explicitResearch shows that interim CEO appointments typically trigger negative reactions from stakeholders
  The Pitfalls of an Interim CEO · p2
• explicitInterim CEO appointments lead to long-term value loss
  The Pitfalls of an Interim CEO · p3
• implicitThe perceived safety of interim CEO appointments is illusory — the apparent risk reduction conceals downstream costs
  The Pitfalls of an Interim CEO · p4
• implicit[INFERRED] Markets interpret interim CEO announcements as signals of board indecision or governance failure, not organizational stability
  The Pitfalls of an Interim CEO · p6

2026-07

• explicitcorroboratedThe Conflicted (~35%) are the ambivalent emotional center of gravity — not soured on AI, but exhausted by the work of keeping up while holding positive and negative feelings at once.
  Lenny Rachitsky's Post · p4
• explicitThe center of gravity of software work is moving from writing code to specifying, verifying, and curating knowledge.
  We've Stopped Arguing About Whether AI Changes Software · p2
• implicitWithout this substrate, organizations discover the same underlying governance gap repeatedly and in escalating form -- first as a surprising invoice, later as an audit finding, eventually as an incident -- because no signal closes the loop early enough to act before the failure compounds.
  The Meter Was Always Running · p14

2026-09

• implicitThe author assumes responsibility for closing MCP's governance gap sits with the integrating enterprise (via allowlisting, universal auth, audit logging, dynamic secrets) rather than with protocol maintainers or the registry closing it upstream.
  MCP Is Not Just Another API Standard · p15

Tensions

Open gaps (18)

• incompleteThe piece never delimits the analogy. Clausewitz wrote about conflict between coherent state actors with continuous policy interests, capable of mobilizing collective will, and existing in a Westphalian system; everyday disputes are dyadic, intimate, often involve unequal power, and frequently lack a coherent 'policy' on either side. The transfer is asserted in the intro and then never re-examined. This is the central category-jump risk: the seven principles inherit their authority from a domain whose structural features mostly do not apply.
  How To Handle Conflict: 7 Secrets From History's Master Strategist — read next: Compare against Annie Duke (decisions under uncertainty for individuals — 'Thinking in Bets'), Roger Fisher & William Ury ('Getting to Yes' — interest-based negotiation, an explicit alternative to the adversarial frame), Deborah Tannen on argument culture, and Donald Kagan's 'On the Origins of War' for a check on how state-level conflict actually scales.
• incompleteWhat is genuinely from Clausewitz here vs. Barker's own framing is unclear. 'Subordinate to purpose,' 'fog and friction,' 'center of gravity,' 'defense as the stronger form,' 'the enemy gets a vote' (this last is more US military doctrine than Clausewitz), and 'culminating point' (Section 7) all have textual warrant in 'On War.' But the operationalizations ('ask: do you want an apology?') are Barker's; readers are left unable to separate Clausewitz from self-help.
  How To Handle Conflict: 7 Secrets From History's Master Strategist — read next: Read Book I of 'On War' directly, especially chapters on the nature of war, friction, and the political object; cross-reference with Beatrice Heuser's 'Reading Clausewitz' or Hew Strachan's 'Clausewitz's On War: A Biography.'
• incompleteThe 'seven secrets' don't form a tightly coupled theory; they are seven valuable but largely independent prescriptions sharing a tone. Several overlap (Section 1 ≈ Section 7 on goal drift; Section 5 ≈ Section 3 on the counterparty), while no principle covers ethics, power asymmetry, conflict termination by repair, or pre-conflict prevention. Treating the list as a complete strategy would leave several common conflict types (chronic, structural, power-asymmetric, identity-based) outside the frame.
  How To Handle Conflict: 7 Secrets From History's Master Strategist — read next: John Paul Lederach 'The Little Book of Conflict Transformation' for a non-strategic frame; Marshall Rosenberg 'Nonviolent Communication' for a frame where 'objective' is replaced by 'shared need'; Carol Tavris & Elliot Aronson 'Mistakes Were Made (but Not by Me)' on the cognitive dynamics of overreach.
• incompleteSections 2 and 5 invoke ideas (decide under uncertainty; model the other side's agency) that have a much more rigorous treatment in decision theory and game theory. Barker's framing stays at the level of aphorism. For a reader already inside the decisions-under-uncertainty literature (Annie Duke, Kahneman), this is the thinnest layer.
  How To Handle Conflict: 7 Secrets From History's Master Strategist — read next: Annie Duke 'Thinking in Bets' and 'How to Decide'; Schelling 'The Strategy of Conflict'; Axelrod 'The Evolution of Cooperation' for what 'the enemy gets a vote' actually looks like once formalized.
• illogicalThe 'defense > offense' principle is stated as a near-universal rule, but the supporting reasons (terrain, supply lines, ability to wait) are domain-specific to military conflict and at least partly contested even there. In interpersonal life, the defender often has the time-on-side advantage precisely when they hold the structural power; recommending defense without specifying that condition can read as 'powerful parties should sit tight and wait the other side out.' Barker doesn't flag this.
  How To Handle Conflict: 7 Secrets From History's Master Strategist — read next: Cf. Stephen Biddle 'Military Power' on the empirical fragility of the defense-dominance claim; Ury 'Getting Past No' on how to engage when you are the disadvantaged party.
• incompleteThe article never canvasses structural alternatives to adding a C-suite role: explicit resilience portfolio for COO; resilience standing committee with rotating chair; embedding resilience accountability in existing role mandates; redesigning the boundaries between CISO/CRO/COO so the gap disappears. The choice between 'new role' vs. 'redesigned roles' is never made an argument — it is assumed.
  The Case for Hiring a Chief Resilience Officer — read next: Donella Meadows on leverage points (a new actor is a relatively low-leverage intervention compared to changing rules, feedback loops, or paradigms); Cutler on accountability culture and DRIs (whether accountability needs a title or a clearer commitment); Yourdon & Constantine on coupling and cohesion applied to org structures — when do you add a module vs. refactor existing modules?
• incompleteNo theory of how horizontal authority operates in practice. The CResO is said to have 'real authority' to set standards, make operational decisions during crisis, and report to CEO/board — but during a cascading event the CISO is restoring infrastructure, the COO is running operations, the CRO is managing exposure. The article does not explain by what mechanism the CResO's decisions override or align theirs.
  The Case for Hiring a Chief Resilience Officer — read next: Incident command system literature (NIMS/ICS); how military and emergency services handle cross-functional command; product organizations on dual-track authority (functional vs. mission); papers on matrix organizations that survive vs. collapse.
• uninformedNo engagement with the Resilience Engineering academic tradition (Hollnagel, Woods, Dekker), which has spent 20+ years arguing resilience is the adaptive capacity of a sociotechnical system — not something that can be 'owned' by a single accountable executive. The article reads as if this body of thought does not exist.
  The Case for Hiring a Chief Resilience Officer — read next: Hollnagel, Woods & Leveson, 'Resilience Engineering: Concepts and Precepts'; David Woods' lectures on graceful extensibility.
• illogicalThe 'companies that adopted the role' evidence chain has a selection-effect problem: companies that publicly appoint CResOs are companies that have had high-visibility cascading failures (CrowdStrike) or operate in high-cascade-risk industries (finance, pharma). The adoption rate does not establish that the role causes better outcomes — it establishes that organizations with the problem buy the solution. The article treats adoption as evidence of efficacy.
  The Case for Hiring a Chief Resilience Officer — read next: Pfeffer & Sutton, 'Evidence-Based Management'; any introductory text on selection bias in management research.
• incompleteAuthor conflict-of-interest signal in the closing note: the authors thank executives at Syngenta, Novo Nordisk, Nestlé, and 'Group Resilience' — all members of the UNDRR network the article cites approvingly. The article is partly the UNDRR network's case for itself, but this framing is not surfaced.
  The Case for Hiring a Chief Resilience Officer — read next: Look up Igor Linkov's affiliations and the UNDRR Network's funding and membership economics.
• incompleteNo discussion of failure modes for the CResO function itself: accountability laundering (other executives off-load problems to CResO), resilience theater (dashboards proliferate, actual capability does not improve), single-point-of-failure (a strong CResO leaves and capability collapses), incentive misalignment (CResO scored on time-to-recover incentivizes minimizing reported incidents).
  The Case for Hiring a Chief Resilience Officer — read next: Goodhart's Law literature; Cutler on metrics that displace work; security industry's experience with CISO accountability since SOX/Sarbanes-Oxley.
• incompleteThe entire article is paywalled. All propositions beyond the teaser's two sentences are inferred from the title and HBR's typical article structure. This extraction is a structured placeholder — not an analytical reading of the actual text.
  The Pitfalls of an Interim CEO — read next: Access the full HBR article; search for the underlying research (likely event studies on interim CEO announcements; Quigley & Hambrick 2012 on interim leadership; Ballinger & Marcel 2010 on CEO succession and interim appointments)
• incompleteThe available teaser doesn't distinguish between types of interim appointments: external interim (a professional turnaround/transition specialist), internal interim (an existing executive temporarily elevated), or board member as interim. Each likely has different risk profiles. The 'pitfalls' may not apply uniformly.
  The Pitfalls of an Interim CEO — read next: Succession research distinguishing interim types; Spencer Stuart data on interim CEO outcomes by appointment type
• incompleteThe 'long-term value loss' claim requires a counterfactual: compared to what? A rushed permanent appointment? A failed external search? The article presumably addresses this, but without the text, the comparison baseline is unknown.
  The Pitfalls of an Interim CEO — read next: The academic literature on CEO succession planning quality as a predictor of transition success
• incompleteThe four-source taxonomy is presented as exhaustive but no argument is made for completeness. Interpersonal dynamics (e.g., genuine personality clashes, political conflicts, or power struggles) are not addressed as a distinct category and do not fit neatly into the four sources.
  Why Effective Leaders Get Branded as Problems
• incompleteThe article provides no guidance for the common case where multiple friction sources are simultaneously primary. The diagnostic protocol treats them as distinguishable, but the simple heuristic at the end (consistent/recent = skill gap, outdated = drift, strong performance + friction = overextension, environment blocks change = system) does not address compound cases.
  Why Effective Leaders Get Branded as Problems
• uninformedThe claim that true skill deficits are the 'minority of situations at the senior level' rests entirely on the author's coaching experience. No data, frequency estimates, or external research is cited to support this base-rate claim, which is load-bearing for the entire argument.
  Why Effective Leaders Get Branded as Problems
• illogicalThere is a circularity risk in the diagnostic protocol: the article argues that organizations default to blaming the individual, then provides a framework where three of four sources exonerate the individual. The framework may encode the author's coaching bias (clients are usually right, systems are usually wrong) as a structural feature rather than testing it.
  Why Effective Leaders Get Branded as Problems