In the spring of my eighth year in organizational development, I ran an initiative that failed in the most public way I had experienced to that point. We had spent eleven months building a new talent architecture across a business unit of roughly fourteen hundred people — new competency frameworks, a redesigned succession process, a cohort-based leadership development program that I believed in deeply. Senior leadership had championed it. My team had done exceptional work. Then a merger announcement came down that made the entire infrastructure obsolete within sixty days. The new parent company had its own systems, its own processes, and no appetite to integrate ours.
I remember sitting with my team the morning after the announcement. I had nothing useful to say about the work — it was, for all practical purposes, over. What I had to figure out, in real time, was how to be present enough to process it honestly while remaining sufficiently functional to help them figure out what came next. The space between those two requirements is where I first became genuinely curious about resilience — not as a concept but as a set of concrete practices I either had or didn't.
The standard framing of resilience treats it as a trait — something you either have or don't, distributed across people like height or musical aptitude, shaped early in life and not particularly amenable to development. The practical implication of this framing is that resilience selection, not resilience development, is what organizations should invest in: find the people built for adversity and put them in the hard roles. The people who aren't built for it shouldn't be there.
This framing is wrong in ways that matter enormously for how organizations develop leaders and how leaders develop themselves. Resilience is a set of practices, and the practices are learnable. The people who appear most resilient under pressure are not, for the most part, the ones who feel adversity least — they're the ones who have developed more reliable methods for processing it, understanding it, and returning to full function after it. That distinction changes everything about what's developable and how.
Where the trait myth comes from — and why it persists
The trait interpretation of resilience is not entirely baseless. Genetics and early developmental experience do influence baseline emotional regulation capacity — the research on temperament is real. Some people arrive at their first serious professional setback with more psychological resources than others. That's not a comfortable fact, but it's a fact.
The problem is the interpretive leap: from "baseline differences exist" to "resilience is therefore not developable." That leap doesn't follow, and the evidence doesn't support it. The research on resilience as a learnable set of skills goes back at least to Martin Seligman's learned optimism work in the 1990s and runs through more recent longitudinal studies on leadership development under adversity. What the research shows, consistently, is that resilience-relevant practices can be learned and that the learning compounds. People who survive one serious setback — who process it rather than bypassing it — are more resilient in the next one, not primarily because they're tougher but because they have better methods.
The trait myth persists partly because high-resilience leaders often can't articulate what they're doing. When you ask a senior leader how they got through a difficult period, the answer is often something like "I just kept going" or "I have a lot of support at home" — neither of which is a useful developmental prescription. The practices are real, but they're often invisible to the people who've internalized them. That invisibility gets interpreted as evidence of a trait rather than evidence of a skill that hasn't been made explicit.
There's also a status dimension. For some leaders, the idea that resilience is a trait rather than a practice is self-serving — it explains their resilience as an innate quality rather than something they worked to develop, and it creates a convenient ceiling on what their less-resilient colleagues can achieve. I've seen this dynamic play out in talent conversations, where senior leaders describe a subordinate as "not having the constitution for this kind of work" when a more accurate description would be "hasn't yet developed the practices that would allow them to function under this kind of pressure."
What resilience actually comprises — broken down practically
The shift from treating resilience as a trait to treating it as a set of practices requires being specific about what those practices are. In my experience across forty-plus leadership development engagements and in my own practice over fourteen years, resilience in leadership contexts breaks down into four distinct components — each learnable, each requiring deliberate attention.
Processing speed and quality. This is the capacity to sit with what happened — to actually let it land — before moving to response. It sounds simple and it's genuinely difficult. The default response to professional setbacks among high-performing leaders is to skip the processing and move directly to problem-solving: what do we do now, what's the learning, how do we avoid this next time? The processing — the acknowledgment that this actually hurt, that the work mattered and its loss matters — gets treated as an indulgence, something for people with too much time on their hands.
What I've observed repeatedly is that bypassing the processing doesn't eliminate it. It defers it. Leaders who consistently skip the processing of setbacks accumulate a kind of unresolved residue that surfaces later: as disproportionate reactions to smaller frustrations, as a subtle brittleness under pressure that wasn't there before, as a progressive narrowing of risk tolerance that looks like wisdom but is actually defensive self-protection. The leaders who develop the practice of real processing — who build in the space, however brief, to genuinely acknowledge what happened — recover faster in the long run even if they appear to recover more slowly in the short run.
Meaning-making. The capacity to place adverse experience in a frame that makes it bearable and useful — not to minimize it, but to understand it in terms of what it might mean for who you're becoming and what you're trying to do. This is the component of resilience that most closely overlaps with what psychologists call post-traumatic growth, and it's probably the most misunderstood.
Meaning-making is not the same as toxic positivity. The question isn't "how was this actually good" — sometimes setbacks are just costly and there's nothing to be gained from pretending otherwise. The question is more precise: what is the most accurate interpretation of what happened, including what it reveals about my assumptions, my environment, and what I need to develop? That question requires honesty about what went wrong and why, and it produces a different kind of learning than the post-mortems that are primarily focused on systemic improvement rather than personal development.
Recovery practices — physical, relational, and psychological. This is the most concrete component and the one leaders are most likely to underinvest in. Recovery isn't rest in the passive sense — it's the active restoration of capacity that allows sustained leadership effort over time. The leaders who sustain high performance across long careers are almost invariably the ones who have developed some version of reliable recovery practice: something physical that creates a genuine boundary between work states, something relational that involves honest connection with people who aren't filtered through the power dynamics of their role, and something that gives them genuine absorption in something other than leadership problems.
The failure mode I see most often is leaders who treat recovery as optional — something to get to when the workload lightens, which it never does. The result is a progressive depletion that's invisible until it isn't: the leader who handles a major crisis and then, in the relative quiet that follows, suddenly can't get out of bed in the morning. Sustainable resilience requires treating recovery as a leadership practice, not a self-indulgence.
Community and social support utilization. The capacity to actually use the relationships available to you for recovery and perspective — to accept help, share difficulty with appropriate people, and draw on human connection rather than persisting in the performance of invulnerability. This is particularly difficult for senior leaders because the role creates powerful incentives against it: you're supposed to be the source of stability, the person other people draw on. Admitting that you're struggling can feel like a failure of the role itself.
What I've learned — partly through direct observation of leaders who navigate difficulty sustainably, and partly through getting it wrong myself — is that the performance of invulnerability is one of the primary vectors through which senior leaders become isolated and fragile. The leaders who maintain genuine communities of honest connection — people with whom real conversation about real difficulty is possible — are significantly more resilient than those who don't, independent of temperament and baseline capacity.
The organizational dimension: why team resilience matters more than individual resilience
Individual resilience is important, but I want to argue that team resilience is the more consequential organizational unit — and the one that gets dramatically less attention. The resilience of an organizational unit isn't simply the average of the resilience of its members. It's an emergent property of how the team has navigated adversity together, what they've learned from it, and what trust they've built through the navigation.
Teams that have been through serious difficulty together — that have navigated genuine uncertainty, made hard decisions under pressure, and come out with their relationships and mutual respect intact — are significantly more capable under subsequent difficulty. They have established communication patterns that work under stress. They've learned which members of the team stay clear-headed under pressure and which ones need more support. They have a shared narrative about having gotten through hard things before, which is one of the most powerful resources available when the next hard thing arrives.
This has a direct practical implication that runs against some conventional wisdom about protecting teams from difficulty. The teams that consistently receive adequate resources, clear mandates, and minimal friction develop a kind of hidden fragility that isn't apparent until a genuine crisis exposes it. They've never had to develop the muscles that difficulty builds. The leader who is always running interference, always absorbing the organizational turbulence before it reaches the team, is inadvertently producing a team that can only function in protected conditions.
I spent several years working with a function whose leader was exceptionally skilled at this kind of protection. Her team loved working for her — the conditions were excellent, the support was genuine, the work was well-resourced. When she left, the team's performance collapsed in ways that surprised almost everyone except me. They had never had to navigate hard things. They had never built the shared experience of difficulty that creates organizational resilience. What looked like excellent leadership had actually been producing a team with no resilience beneath the surface.
The developmental implication: building team resilience requires deliberately exposing teams to appropriately scaled difficulty — stretch goals that require genuine effort, assignments with real uncertainty, the kind of productive struggle that develops capability and, along the way, builds the relational trust that makes the team resilient to subsequent difficulty. This isn't about making work unnecessarily hard. It's about understanding that some difficulty is a resource, not a problem to be solved.
The counterargument worth taking seriously: what about hardwired differences?
I want to engage with the real objection here, not the straw man version. The serious case for treating resilience as significantly trait-based goes something like this: yes, practices matter, but baseline emotional regulation capacity varies significantly across individuals, and that variance is substantially heritable. The person with naturally lower baseline anxiety and stronger emotional regulation can develop resilience practices on top of a more favorable foundation. Telling the person who starts from a harder place that resilience is entirely learnable may be setting them up for a different kind of failure — the belief that if they just worked harder at the right practices, they'd be as resilient as the person next to them who started from an easier baseline.
This objection has genuine force, and I don't want to dismiss it. What I'd say in response is this: the question for leadership development purposes isn't whether baseline differences exist — they do. The question is whether the development of resilience practices produces meaningful change in actual resilience capacity, regardless of where you start. And on that question, the evidence is clear that it does. The comparison shouldn't be between a person with low baseline regulation and a person with high baseline regulation. It should be between that same person before and after having developed robust resilience practices. On that comparison, consistent gains are achievable.
What this means practically: leadership selection that values apparent resilience as evidence of fit for hard roles is not wrong. But it becomes harmful when it substitutes for resilience development — when organizations use the trait framing to sort rather than develop, and never invest in the practices that would actually make more leaders more capable under adversity.
How to actually build resilience — deliberately
The shift from treating resilience as a trait to developing it as a practice requires making it specific enough to act on. Here's what that looks like concretely.
Build a processing practice. When significant setbacks occur, create a deliberate space — even twenty to thirty minutes — to sit with what happened before moving to problem-solving. This doesn't need to be elaborate. What it requires is honest engagement with the question: what actually happened here, and what did it cost? Write it down if that helps. The discipline is resisting the pull to move directly to "what now" before you've genuinely sat with "what happened."
Develop a meaning-making habit. At the end of difficult periods, ask a specific set of questions: What did this reveal about my assumptions? What capability did this expose as underdeveloped? What does this change about how I'll approach similar situations? The goal isn't to extract silver linings — it's to understand what the experience is actually teaching you about yourself and your environment. The leaders I've seen sustain excellent performance over decades are almost uniformly good at this kind of learning extraction, even from failures.
Protect recovery practices like they matter. Identify what actually restores your capacity — physical activity, genuine time off, deep social connection, absorbing creative engagement — and treat those practices as non-negotiable rather than nice-to-have. The failure mode is treating recovery as what you do when the workload lightens. The workload never lightens. Recovery has to be built into the operating rhythm, not deferred to a future that doesn't arrive.
Cultivate genuine community. Deliberately develop relationships with people who can absorb honest conversation about what you're actually carrying — not the managed version, not the professional performance. This almost certainly requires investing in connections outside your immediate reporting structure, where the power dynamics make full honesty difficult. A peer network at your level, a coach, or close trusted advisors who know the work and aren't in it — these are the relationships that make sustained resilience possible.
What resilience looks like in the long run
The morning after the merger announcement, when I sat with my team with nothing useful to say about the work we'd built, I did a few things right and several things wrong. What I did right: I acknowledged the loss directly rather than immediately pivoting to opportunity framing. I told them honestly that I was disappointed and that I thought the work had been excellent and that it was genuinely painful to see it not reach the people it was designed for. I didn't perform equanimity I wasn't feeling.
What I did wrong: I moved to problem-solving too quickly. I spent that first conversation mostly mapping the new landscape and identifying where our skills might translate in the new structure. It was useful information, but it was premature. The team needed a bit more space to simply absorb what had happened before we moved to what came next.
I've thought about that morning often in the years since. Not because the mistakes were severe — they weren't — but because it crystallized something I've come to believe strongly: resilience is built in exactly those moments when the instinct to move on conflicts with the need to first genuinely engage with what happened. The leaders who develop real resilience are the ones who don't bypass the engagement, who have enough practice with difficulty that they trust their ability to come through it, and who build the habits and relationships that make the processing possible.
The work is specific, it is learnable, and it compounds. The leader who develops robust resilience practices at year five of their career is a genuinely different leader at year fifteen than one who relied on temperament alone. That's not an inspirational claim — it's a practical one, grounded in what I've seen work across more difficult leadership situations than I wish I'd had the opportunity to observe.
Related: How Leaders Actually Process Significant Failure, Managing Your Reactions Under Pressure