What Resilience Actually Feels Like

Most accounts of resilience describe a single turning point: the job loss that redirected a career, the setback that turned out to be the best thing that happened. My experience has been less like that. Over thirty-five years working across start-ups, scale-ups, turnarounds, and management consulting, change has been frequent enough that it stopped feeling like an exception a long time ago.

That is not a complaint. It is, I think, where the useful version of resilience actually comes from.

The consulting model as training

Working as a management consultant teaches something that employment often does not: every engagement ends. The consultant arrives, solves the problem, leaves. The relationship with any given organisation is bounded by definition. Most people experience that as instability. The ones who last in consulting experience it as the structure of the work.

What it builds is a different relationship to endings. The conclusion of one thing stops feeling like a failure state and starts feeling like the starting position for the next. That sounds like a mindset reframe, but it is more practical than that. It changes what gets held onto. When the engagement is known to end, a consultant does not build their identity inside it in a way that makes leaving devastating.

I carried that thinking into every start-up and scale-up I joined afterwards. The companies that thrive do not always survive. The ones that scale do not always stay scaled. Having been through several of both, what one accumulates is not just experience of the cycle but a different tolerance for where one stands in it at any given moment.

The value of breadth when one domain fails

There is a systems-engineering concept called redundancy: if a critical function is supported by multiple independent paths, the failure of one path does not bring down the system. Careers work similarly, though most people do not think about them that way until the failure happens.

Working across hardware, firmware, software, manufacturing, defence consulting, hospitality, and cloud infrastructure means that no single domain collapse has ever defined my situation. When one area contracted, there was always another where the skills transferred and the credibility was real. The breadth that looks like a restless CV is actually a form of anti-fragility. Each domain change is difficult at the time. Collectively they are what makes a person difficult to put out of work.

The corollary is that people who spend their entire career deepening a single specialisation are building capability on a narrower foundation than it appears. When the specialisation becomes unfashionable, or the sector contracts, there is no adjacent domain to step into. Resilience, in a career that spans decades, is partly a function of how wide it has been built.

The part that transfers is rarely the obvious one. It is usually a way of seeing rather than a technical skill: how cash really moves through a business, how customers behave when something goes wrong, how a team behaves under pressure. Each move feels like starting again at the time. With hindsight, very little is lost. It is simply waiting for the right context.

What resilience actually feels like

It does not feel like strength at the time. The periods that, in hindsight, represent the most useful transitions were not comfortable while they were happening. The end of something one has invested in always has weight, regardless of what follows.

What resilience actually is, in my experience, is the capacity to remain functional enough during the difficult period to make use of where one has landed. Not to pretend the difficulty is not there, not to accelerate past it by sheer will, but to keep making decisions and building things even when the ground is uncertain. The career on the other side of those transitions has almost always been richer than the one that preceded them. That is not visible in advance. It becomes visible only by having been through enough of them to see the pattern.

Building resilience into the organisation

Personal resilience is necessary. It is not sufficient. A leader who is personally resilient but has built an organisation that depends entirely on their own capacity to absorb difficulty has not built a resilient organisation. They have built a fragile one with a resilient person at the centre.

The work of building organisational resilience is different from the work of building personal resilience, and it requires deliberate attention. It means creating redundancy in critical capabilities so that the departure of one person does not take institutional knowledge with them. In a connected-product company, that includes knowledge that sits awkwardly between functions: why a particular calibration routine exists, which production tolerances matter in the field, what a service partner has learned that never made it back into the formal documentation. It means building a culture where difficulty is acknowledged rather than performed away, because teams that cannot name what is hard cannot address it. It means making sure the team has enough context about the organisation’s direction and constraints that they can continue to function when the leader is not available to make every decision.

The test of whether an organisation is genuinely resilient is not how it performs when things are going well. It is how it functions when the leader is absent, when a key person leaves unexpectedly, or when the external environment changes faster than the plan assumed. Leaders who have built genuine resilience into their organisations are not indispensable. That is the point. The goal is not to be the person the organisation cannot function without. It is to build the organisation that functions because of what the leader has built into it, not because of the leader’s continued presence.